- From: Borek Bernard <borekbe@yahoo.co.uk>
- Date: Wed, 11 Jun 2008 08:15:54 +0000 (GMT)
Hi Adrian, That is actually a very good point, I missed that. In fact, it means that _tab should not be part of HTML spec because it would possibly make things even worse than they currently are (opening GReader links in new "_tab"s in old browsers would lead to losing the opened articles) . I still believe that there should be a way to instruct the browser to open a new tab and the before mentioned CSS3 target-new is probably the best way (if not only one) to go. Thanks, Borek ----- Original Message ---- From: Adrian Sutton <adrian.sutton@ephox.com> To: whatwg at lists.whatwg.org Sent: Tuesday, 10 June, 2008 10:29:54 PM Subject: Re: [whatwg] Proposal: target="_tab" >> From my brief testing, _tab opens a new window so it should be backwards >> compatible. It's deceptively close but not quite backwards compatible. _tab will cause the link to open in the frame called "_tab" and if it doesn't exist it creates it, as a new window. So the first link works perfectly and opens a new window but the second link you click will replace the first one since there is now a frame called "_tab". Regards, Adrian Sutton. ______________________ Adrian Sutton, CTO US: +1 (650) 292 9659 x717 UK: +44 (20) 8123 0617 x717 Ephox <http://www.ephox.com/> Ephox Blogs <http://planet.ephox.com/>, Personal Blog <http://www.symphonious.net/> __________________________________________________________ Sent from Yahoo! Mail. A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html
Received on Wednesday, 11 June 2008 01:15:54 UTC