Tag: html
HTML.next perspectives
muses on how standards should be made: match reality? reverse engineering? precision? extensibility? timely? open source? patents? forking? accessibility?
Empty src reload behavior
This markup means that there is an image at the same address as the HTML document. IE silently drops the image. Other browsers do not; which results in a “duplicate” request for the page.
Refactoring HTML
the biggest refactoring job in the world
Microsoft subterfuge
Unless you’re suggesting that the WG would shoulder the financial burden when we (Microsoft) are sued because we broke compatibility and caused some company’s multi-million-dollar intranet app to break.
what a bunch of crap. they deserve to go under.
XHTML over Jabber
maybe the first useful application of xhtml
iPhone and Open Standards
I was a little nervous to look at iPhone for Web Developers from the Apple Developer Connection; with a splash as big as the iPhone, it seemed inevitable that they’d cut corners when it came to support for open standards. Surely the Use Standards and Tried-and-True Design Practices heading was a tease. But then… wow… The first surprise was support for the tel: URI scheme
then again, apple does NOT hate the web on the iphone. these are incredibly well done
HTML art
a new crashing test for browser implementers. others would call it html art.
Future of the Web
While XHTML2 is a semantic improvement over XHTML 1.0, it does not seem likely that it will matter for web developers for a long time, especially when one considers that Internet Explorer still doesn’t offer XHTML 1.0 support. It will take many years for a new version that might support XHTML2—and we have been given no indication that the next one will. On the other hand, many parts of HTML5 are already creeping into browsers, and, if Microsoft takes an active part in the development of HTML5 in the future, it looks likely that many features that are already very polished will be supported cross-browser in a much shorter timeframe. The fact that HTML5 contains several areas that are already ready for implementation while still being developed in other areas makes it a technology that is easy to partially adapt until browser support is fully evolved for the features you wish to use.
good explanation of xhtml5 vs xhtml2 , etc
Apple canvas patent
so much for canvas making it into w3c now.