One of the biggest annoyances on the web, and something I really hate, is popup windows. It frustrates me, and many others, whenever a site attempts to forcibly open a new window for any reason whatsoever. So, it may be surprising to hear that the
target attribute has actually been made conforming in HTML5, even though it was non-conforming in HTML 4.01 Strict, and that this is a good thing. There are in fact several valid reasons for making it conforming, which I will attempt to explain.
When embedding documents within an
iframe, it’s important to be able to set the target of links and forms to be the
iframe. This is a useful technique for cases where it’s undesirable to refresh the entire page to update a small section. Although there are alternative techniques that could be used, such as the many AJAX solutions, the simplicity of using an
Similarly, it’s important to be able to cause links within a framed document to be able to set the target to the
_top in order to break out of frames. Without those values, links would default to opening within the frame itself, which is not always useful. When done well, using
target in this way can actually be quite beneficial for the usability of a site.
The purpose of
_blank value, however, is to cause a link to open within a new window or tab. Although there are many valid arguments against forcing a new window, mostly related to usability and accessibility, the reason for allowing this becomes clear when you consider the alternatives.
There are many authors who, for whatever reason, really want to have links opened in new windows, and nothing will convince them otherwise. But experience has shown over the years that because it is non-conforming in HTML 4.01 Strict, many authors will go to sometimes extreme lengths to get a popup window, while still writing technically valid markup.
Such techniques range from dynamically adding the
target attribute to the DOM with script, to using event handlers and calls to
window.open(). Such approaches actually ignore the reason for making it non-conforming in the first place, which was presumably to avoid the usability issues, and in fact have chosen to give validity a higher priority.
When a new window is desired, the benefit of using the
target attribute over many of the other techniques is that it is actually more beneficial to the user because it is easier to override. Many browsers offer options to cause such links to open in a new tab instead of a window, and some even allow it open in the same tab. While it is also possible to do that with
window.open(), doing so can actually interfere with sites that depend upon the new window to function correclty.
Allowing authors to get what they want using the least user-hostile method is significantly better than inadvertently forcing them to find more harmful workarounds. So this is why the
target attribute has been made conforming in HTML 5.
2 thoughts on “Conforming target Attribute”
As a hobby, I created a personal Web site that now has over 300 pages. I use the target attribute in very limited circumstances — only when I believe a visitor to my Web site might want to switch back and forth between two pages. An example is my [http://www.rossde.com/internet/int_tools.html], which uses target to launch a new page or tab for my glossary. This avoids repeated loading and rendering of pages.
Note that Gecko browsers have a user option to force a new page into the current window when the link to that page includes the target attribute. That is, an attempt to launch a new window or tab can be defeated by a user option.
I don’t know the issues too well. But I like to think of popups in the context of tabs. For example
1) open in new tab and switch to it
2) open in bg tab but do not switch to it
Maybe some API to open several tab and switch to a certain tab type use cases.
I hate windows. I hate how they overlap and they are a pain to manage from the keyboard. Tiled WM & tabs are the future for me. 🙂
Comments are closed.