Android’s stock browser supports the range input type, but in versions 3.x4.x and below (not sure about Android 4.x), it doesn’t actually display the UI. It does, however, support parts of the Shadow DOM. That means we can style this element, and give our users a visible control. The image below shows a rather garish [...]
[7 Feb 2012]
Recently a friend messaged me about the url input type, and how to prevent Opera from automatically prepending http:// to the value of a URL input field if it is missing. I think I’ve found a workaround, but first, I want to discuss the url input type, and how different browsers handle it. HTML5 introduces [...]
[3 Jan 2012]
My super-short post that attempts to answer this question as completely and accurately as possible in three presentation-friendly bullet points. HTML5 … re-imagines HTML as an API with objects, events, interfaces, and methods or a collection of interfaces. defines an algorithm for generating a consistent, cross-browser friendly DOM tree, regardless of the quality of the [...]
[26 Oct 2011]
To date, Firefox does not yet support the loop attribute of the <video> element. This snippet is a simple work-around. Once the video’s ended event is fired, it calls the play method. For more, consult the media events section of the HTML5 specification.
[4 Oct 2011]
Debugging is part of my day job at Opera. Today, I stumbled across an issue related to white spaces and values for the HTML type attribute that affects Opera. Take a look at the following code: var d = ‘test.js’; var s = document.createElement(‘script’); s.setAttribute(“type”, ” text/javascript”); // note the leading space s.src = d; [...]
[12 Apr 2011]
One of the neat things about HTML5 is that it allows for multiple file uploads in one file upload field. Of course, you have to have a browser that supports such a feature. Currently Opera 11.10 does. So do Firefox 4, the latest version of Chrome, and Safari 5.0.4. (Internet Explorer 9 does not.) Now [...]
[29 Mar 2011]
… on non-void elements, at least. One of the big misconceptions about HTML5 is that any tag can be self-closed. That’s not true, though it appears that way. What HTML5 does is provide parsing rules for handling mismatched tags and markup. While it seems like self-closing tags are acceptable, that’s not the case. This post [...]
[23 Mar 2011]
Click to embiggen. View the page causing the error. The problem above was caused by three things working in concert. An HTML page was served with a Content-Type: application/xhtml+xml; response header. Here’s what the server response headers look like: HTTP/1.1 200 OK Cache-Control: no-cache Pragma: no-cache Content-Length: 4001 Content-Type: application/xhtml+xml; charset=utf-8 Expires: -1 Server: Microsoft-IIS/7.0 [...]
[10 Mar 2011]
Cross-posted to my Opera blog A little over a week ago, I gave a talk to the Los Angeles HTML5 User Group about forms in HTML. I said something that was incorrect in the talk, and had a faulty example in the slides (that’s what happens when you pull it together in a day!). First [...]
[7 Mar 2011]