the target attribute for the a tag is deprecated. Some alternatives are out there, including assigning a class or using rel=”external”, then iterating through the page to spawn a new window using JS. Is that cheating? Not to mention.. is iterating through an entire page a drain on client resources?
There is always the old fallback, the ‘official’ way.
The modularisation of XHTML 1.1 breaks down XHTML 1.0 Strict into a collection of abstract modules, grouped by related elements and attributes. The idea behind modularisation is instead of having one huge DTD that defines everything; modules are used as and when required.
– From http://accessify.com/features/tutorials/new-windows/
Yes, George, that’s xhtml1.1. So what’re the differences between 1.1 and 1.0? According to the w3c,
This Appendix describes the differences between XHTML 1.1 and XHTML 1.0 Strict. XHTML 1.1 represents a departure from both HTML 4 and XHTML 1.0. Most significant is the removal of features that were deprecated. In general, the strategy is to define a markup language that is rich in structural functionality, but that relies upon style sheets for presentation.
The differences can be summarized as follows:
- On every element, the lang attribute has been removed in favor of the xml:lang attribute (as defined in [XHTMLMOD]).
- On the a and map elements, the name attribute has been removed in favor of the id attribute (as defined in [XHTMLMOD]).
- The “ruby” collection of elements has been added (as defined in [RUBY]).
Well I can handle those.
I’m debating if this is the best way to handle this. Is a custom DTD a good direction?
The whole modularization seems a bit ‘off’ to me. So if I use this DTD, it is okay for me to target a different window, whereas others should not? Is that because if you’ve taken the trouble to research the various modules, they figure you won’t abuse the poor target?