Re: [whatwg] Inconsistent behavior for empty-string URLs
On Mon, 21 Dec 2009 20:03:01 +0100, Nicholas Zakas nza...@yahoo-inc.com wrote: Here are the results of testing various tags with empty URLs across different browsers. The table below indicates how many requests are sent when the given tag is encountered on the page (curiously, Firefox 3 sometimes sends two extra requests). Even though the link tags don't show it in the table, they all had href=. IE7 IE8 FF3 FF3.5 SF4 Ch3 Op10 img src=1 1 1 0 1 1 0 link rel=stylesheet 0 0 1 1 1 1 0 link rel=icon 0 0 2 1 1 1 0 link rel=shortcut icon 0 0 2 1 1 1 0 link rel=prefetch 0 0 2 0 0 0 0 script src= 0 0 1 1 1 1 0 iframe src= 0 0 0 0 0 0 0 input type=image src= 1 1 1 0 1 1 0 object data=0 0 1 1 0 0 0 embed src= 0 0 0 0 0 0 0 html manifest= 0 0 0 0 1 0 0 For the most part, no two browsers act the same. Safari and Chrome are the closest (not surprising). Apply a base URL via base in all cases didn't change the results, except in IE, where it prevented the extra image request from being made. Thanks. IIRC, IE doesn't make a request when using minimized attribute syntax, i.e. img src (because it drops the attribute during parsing). -- Simon Pieters Opera Software
[whatwg] How to select which websocket protocol to use
Hi, In the case someone wants to use BWTP, how is this signaled to the Websocket (javascript) API? Is this controlled by the protocol constructor argument? Cheers! -- Francis Brosnan Blazquez fran...@aspl.es ASPL
Re: [whatwg] api for fullscreen()
On Dec 17, 2009, at 1:52 AM, Simon Pieters wrote: On Thu, 17 Dec 2009 10:30:26 +0100, Maciej Stachowiak m...@apple.com wrote: Some of us at Apple have discussed fullscreen APIs, and we think a user gesture requirement plus clear indication of what has happened is likely sufficient. As to the API itself: we tentatively think a good API would be to make a specific *element* go full screen, rather than the whole Web page. Some use cases for fullscreen will indeed want to transition the whole page, for example, let's say a Web-based editor wants to provide a distraction-free fullscreen mode like WriteRoom. However, it seems like many common use cases will benefit most from taking only part of the page full-screen, for example video or games, where it's common for the original content to only be a small box in the page. Now, content could just manually hide the parts of the page in response to an event. Or you could provide a special media type or pseudo-class to use CSS to hide the unwanted content. In Opera, @media projection targets full-screen mode. It's possible though that a page would want different styles when the whole page is in full screen and when an element is in full screen. A page may also have multiple elements that could potentially be the focus when going full screen (for instance if it has multiple embedded videos) so it can't just use a single @media rule to hide all other content. - Maciej
