4 ms·
And the versions of IE in use didn’t support application/xhtml+xml anyway so you would have to switch to text/html based on the user agent string. It was never
by xtian 9y ago
And the versions of IE in use didn’t support application/xhtml+xml anyway so you would have to switch to text/html based on the user agent string.
It was never clear what the technical benefit of this was supposed to be. I only ever saw one site whose pages served double duty as an API and UI by serving styled XML. It seemed like a challenging approach to pull off well.
- chias 9y agoThe Gentoo website / handbook does this. Or rather, did this a few years ago when I was last messing around with Gentoo. It seems to be HTML now.
- Hello71 9y agoThe Handbook was interesting in that it was one of the few sites that actually went with the XML + XSLT = XHTML route. Of course, nobody knows XSLT, and everyone hates XML, so it was dumped in favor of MediaWiki, which everyone still hates, but at least now mostly understands how to use. (although the same people that insisted we use XML+XSLT also insisted we use SMW, which is even worse... I gave up then, but I hear they're trying to undo SMW now.)
- duskwuff 9y agoThe shoe web site skechers.com used to do this. With the removal of XSL support from browsers, though, it looks like it's now using some form of JS templating.
- spiralx 9y agoI wrote an XSL stylesheet that turned an HTML page into a pretty-printed and syntax highlighted display of its source code.