PHP/Flash/AS/JS/XML webdev, game design and similar stuff.
Well, maybe I’m the last to notice, but hixie works for google now, he has published web authoring stats, he has been slashdotted, he’s currently working on HTML 5 specification, even when we’re expecting XHTML 2 specification to be finished, but some XHTML 2.0 pages alredy exist for quite some time. Also IBM has nice article on HTML 5 vs XHTML 2.0 and all this doesn’t make me feel like world wide web is going to unite in anything.
Cool. Now FXweb parses inner XML to XHTML 1.1 or HTML 4.01 depending on your browser’s coolness factor. Of course, Micro$oft Internet Explorer has coolness factor -200% and doesn’t even recognise MIME type application/xhtml+xml, which should be sent with every XHTML file. Which IS SENT with every XHTML file by FXweb. Standard compliance is a good thing.
That said, I will soon release FXweb 0.0.2 on sourceforge.net – the motto is “useless, but working!” – we’ve still got a long way to go.
Tags: FXweb, Firefox, Content Management System (CMS) and open source.
Wow. I’m just one tiny year late. And I would have saved myself at least a day-long headache if I’d read article explaining what you get and what you lose by serving XHTML as text/html MIME type.
You don’t want to read it? Here’s summary: XHTML sent as text/html instead of application/xhtml+xml is rendered in HTML mode (see previous post). When you write you code in XHTML and serve as text/html, it may appear perfectly valid, but after upgrading to proper application/xhtml+xml, it will probably be broken – e.g. if you’re using SGML comments to hide their CSS and JavaScript or uppercase element types etc. Also – this is the problem I’ve had – be sure to rename your CSS element body to html.
Well, after googling for some AJAX tutorials, I’ve found great resources that every web developer should read (or be able to write such articles).
“Mac IE 5, Windows IE 6, Opera prior to 7.5 and Konqueror do not need an Almost Standards mode, because they don’t implement the vertical sizing of table cells rigorously according to the CSS2 specification in their respective Standards modes anyway.” This one made me laugh. And it also almost made me cry few moments later – when I saw the table describing how DOCTYPE declaration relates to rendering mode – that crap IE 6.0 renders even XHTML 1.0 with XML declaration in quirks mode. Oh my.
But then I realised that even serving XHTML 1.0/1.1 isn’t so great – because almost every hosting I’ve seen so far serves everything as MIME type text/html – which shouldn’t be used for XHTML. Serving XHTML could cause these problems (but that document is a bit outdated). And another problem is that I have no chance of convincing my webserver admin to set up webserver so that it will identify all *.php pages as application/xhtml+xml. Anyway, when I’ve changed FXweb to always send data as application/xhtml+xml, Firefox just spit out XML tree, even when I have properly defined doctype, it is valid XHTML 1.1 and I have CSS styles associated. Strange. I have to look deeper into this.
