Last Updated on 22 Agustus 2010 by dani
MathML and SVG inside! It may not suitable for your favorite Web browsers. If you were new to both of markup standards, please read my previous post at Dani Iswara .com titled (in bahasa Indonesia) Menulis Matematika di Weblog WordPress dengan MathML and Mencoba SVG di Peramban Web Firefox. Or googling it.
After reading Henri Sivonen post in hacks.mozilla.org site about the parser of inline SVG on HTML5 by Firefox 4, I think HTML5 is really promising. Delivering SVG on XHTML doctype is more difficult. Since we have to send the header page as pure XML,
application/xhtml+xml. Read this Mozilla Web Developer FAQ written by Henri Sivonen.
application/xhtml+xmlwas added to the Accept header in order to enable the serving of MathML to both Mozilla and IE with Apache without scripting back when the MathPlayer plug-in for IE did not handle
Now the real purpose of (X)HTML in the next quote.
If your document mixes MathML or SVG with XHTML, you should use
application/xhtml+xml(until HTML5 parsing is supported).
However, if you are using the usual HTML features (no MathML or SVG) and are serving your content as
text/htmlto other browsers, there is no need to serve
application/xhtml+xmlto Mozilla. Serving valid HTML as
text/htmlensures the widest browser and search engine support.
Both of these samples below works fine on my Mozilla Firefox 3.6.6+ running Arch Linux machine. Except this unicode character,
⁢ (fileformat.info). Similar to
⁢ in decimal and
⁢ in hex.
Below are samples of MathML markups from Henri Sivonen post on that hacks.mozilla.org–adapted using decimal entity:
Below is SVG sample. The right padding looks bad on Presto (Opera). Sample of SVG (text-based image in left float) from the same Henri’s post above:
The markups slightly modified for this blog doctype.
Promising. But HTML5 brings the euforia for the Apple’s team also. Read this Christopher Blizzard–Firefox evangelist–post titled Intellectual Honesty and HTML5 on his weblog (0xdeadbeef.com):
That’s right. If you’re not on Safari, then F*ck You.
Aside from the incendiary language I’ve used to help you understand how it feels the real underlying message here is that if you don’t have access to Safari then you must not have access to HTML5. Wait, only Safari supports HTML5??
Some vendor specific features are still in draft for the open Web standards.
HTML5 is in a dangerous place since everyone wants to own it, but everyone is in a different place in terms of support or even what it means. I can’t promise what other organizations will do, but I can at least say what I will do in the future. At Mozilla, intellectual honesty matters and it matters to me personally. So I don’t think you’ll see us do things like this in the future. To us, the web and its users matter more than any particular standard or browser. And you’ll see that reflected in messaging that comes from me and shows up as marketing.
This page is not valid (X)HTML, accessible, and so on.