- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 06 Feb 2008 04:02:07 -0600
- To: "j.j." <moz@jeka.info>, "public-html@w3.org" <public-html@w3.org>
j.j. wrote: >> Firefox handles target="_new" specially like target="_blank". > > Indeed, I see now and ask me why. Some CVS archeology leads me to think that https://bugzilla.mozilla.org/show_bug.cgi?id=17468#c28 is the only justification. Prior to that, there was no "_new" in the relevant part of Gecko. Of course about 6 weeks before that there was no "_blank" either; window targeting was just being implemented at the time. If that is indeed the only reason "_new" is supported, perhaps it should be removed. Technically the change is quite easy, if it doesn't break content (sounds like it shouldn't, that much). Note that there are older appearances of "_new" in the plug-in code, so apparently some plug-ins like to pass that through the plug-in API and expect to get a new window. But that shouldn't affect HTML, of course. I can't tell you the source of those offhand, because they got imported into the public CVS repository with the original Netscape code as far as I can tell. -Boris
Received on Wednesday, 6 February 2008 10:01:59 UTC