PUBLIC MARKS with search browsers

Current versions of Microsoft Internet Explorer also have native support for ruby, and you can also get ruby support in Firefox by installing Piro’s XHTML Ruby add-on (and for more details, see his XHTML ruby add-on info page) — so we are well on the way to seeing the HTML5 ruby feature supported across a range of browsers.

Maintenant que Ruby a gagné son petit autocollant "HTML 5", les développeurs de navigateurs s'y intéressent. Comme quoi, le web tient à peu de chose.

Until now, Sidewiki was available only through Google Toolbar for Firefox and Internet Explorer. Today, we're excited to release the official bookmarklet for Sidewiki, which lets you easily read and write Sidewiki entries in Google Chrome, Safari and others browsers.

If you use the Internet Explorer, Google Chrome or Apple Safari browsers to conduct PayPal transactions, now would be a good time to switch over to the decidedly more secure Firefox alternative.

Founded in 1999, the Rhizome ArtBase is an online archive of new media art containing some 2503 art works, and growing. The ArtBase encompasses a vast range of projects by artists all over the world that employ materials such as software, code, websites, moving images, games and browsers to aesthetic and critical ends. We welcome submissions to the ArtBase; they are reviewed by our curatorial staff on a monthly basis.

This project is about running test cases automatically on several versions of the main Web browsers available today. See the StartPage for more information. Tests and results are visible on http://www.browsertests.org.

The short version of this is pretty easy to see, all of the browsers except for Firefox will use at least 2 packets for an XHR done over HTTP POST. When I saw that Safari sent 2 packets I figured that Chrome would as well, but I tested it anyway just to make sure.

This is (EF BB BF) C3 B6 3D 22 21 22 loaded into browsers under various labels. That happens to be properly formed ECMAScript code for all the encodings used. The bogus results for Opera9 can easily be reproduced in context of the testing script, but probably not individually from a clean cache; what's going on there is unknown. I also noted in running these tests that Opera claims "Opera supports the entire ECMA-262 2nd and 3rd standards with no exceptions" while in fact their implementation does not, the parser rejects code that follows the IdentifierStart :: UnicodeEscapeSequence production of ECMA-262 section 7.6. Instead it implements Opera-only extensions, like comma-free arrays ala [ 1 2 3 ]. Other fun facts include: IE does not implement onload for iframes and cannot modify the innerHTML or tr elements; Firefox ignores "tags" when setting the innerHTML of dynamically created tr elements with no ownerElement... Oh and Opera again needs /th "tags" so it won't nest adjacent th elements when setting innerHTML.

SVG Web is a JavaScript library which provides SVG support on many browsers, including Internet Explorer, Firefox, and Safari. Using the library plus native SVG support you can instantly target ~95% of the existing installed web base.

Well, the author can say it is anything they want, but that doesn't change what it actually is. It is literally not possible to send XHTML5 as text/html, because as soon as you label it as text/html, you are stating "it is HTML".

I used to think that too, but then I realised that in the real world it is different. Browsers sniff, and media types are hard-wired into software, rather than being an extension point. You have to row with the oars you have got. As I said, I send documents with media type text/html, not because they are necessarily HTML, but because I want them in the browser. I agree that the document gets *processed* as HTML, but the document doesn't magically change type just because it gets sent with a certain media type.