It's valid in XHTML 1.1 and WCAG 2.0 guidelines don't have any info about its usage?
I know it's not valid in XHTML 1.0 strict, but if many people are using other things like JavaScript, jQuery, rel attribute, PHP etc.
Does it make sense? It means people don't want to follow validation rules, they just want to skip the validation.
It's mainly to do with separating content from behaviour. The basic premise is that we should use HTML/XHTML to denote content, CSS for presentation and layout, and JavaScript for interactivity.
The target attribute doesn't fit in with this paradigm (it's a bit of HTML content that affects browser behaviour), which is why its use is frowned upon.
Why are you trying to force the link to open in a new window in the first place? If the user want to view it in a new window or tab, they should be the one to decide. It's harmful for usability; for example, it stops the back button from functioning correctly, and takes some control out of the users hands. Check out this article for more.
Designers open new browser windows on the theory that it keeps users on their site. But even disregarding the user-hostile message implied in taking over the user's machine, the strategy is self-defeating since it disables the Back button which is the normal way users return to previous sites. Users often don't notice that a new window has opened, especially if they are using a small monitor where the windows are maximized to fill up the screen. So a user who tries to return to the origin will be confused by a grayed out Back button.
Except for 4 special target names, the target attribute is used primarily for frames. Since XHTML 1.0 has no support for frames, it makes sense that it doesn't include an attribute designed to operate on them.
Its sad that this also means losing the "open in a new window" effect, but that's how it is
© 2022 - 2024 — McMap. All rights reserved.
