It all started about two years ago. I had recently joined Mozilla, and about one or two months in, a wiki page surfaced. It was called B2G.
Posts in the "HTML5/HTML/XHTML" Category
Being able to easily specify what to post with XMLHttpRequest is quite a powerful way of sending things to the server, using key/value pairs and
FormData. However, many seem to have missed this gem, so I thought I’d outline it here.
All seats have been taken. Please write a comment to be put on a waiting list, there are always a number of cancellations, so there’s still a chance.
Finally, time for another Geek Meet here in Stockholm!
It’s been a while since I last shared some good reading, but hey, it’s 2012 now, so I thought I’d share my first batch this year!
Last chance to share some good reading with you before the end of 2011. Some good ones in here!
Time again for a number of interesting, entertaining or otherwise all-round good links I recommend taking a look at!
I took a little hiatus last week from posting Robert’s read, but now it’s back with lots of good links!
Last week I introduced Robert’s read and now it’s time again for my reading list for the latest week.
I’ve always been interested in reading all kinds of inspirational articles, blog posts and just fun things on the Internet, and most of the time I just tweet about it. But now, both for my sake and yours, I will write a weekly blog post listing the links for the latest week.
When the AJAX wave came in 2005 when Jesse James Garrett coined the term and then everyone wanted it, one of the major shortcomings was that dynamic updates of only portions of a web page lead to inconsistent history handling and back/forward navigation button problems in web browsers and poor end user experiences. Enter the HTML5 History API.
People are creating amazing things with HTML5
canvas, especially combined with other HTML5 features. I thought I’d touch on a handy method that some people don’t seem to know about: canvas clip.
Yesterday I had the pleasure of speaking at the London Ajax Mobile Event in, surprisingly, London.
Today I was just about to write a blog post about images and serving different sizes depending on the device accessing it. Then the Adaptive images post came up on the email@example.com mailing list. So let’s look at that and add my thoughts.
HTML5 is here to save us all: it has the cool functions, eye-dazzling features and APIs to go around. I get to see a lot of great things developed with HTML5, but I’d like to issue a word of caution as well.
Looking at HTML5 and the placeholder functionality, it’s there to offer a hint to the user before they have started filling out something. But what if that’s not the best way?
With the first release of IE10, and officially stating it won’t support Windows Vista, it gets me thinking.
I’m currently in Las Vegas for Microsoft’s MIX conference where they just showed the first version of Internet Explorer 10. Given what they announced, I have some thoughts.
A common discussion about HTML5 and whether to use it, and touched on in the HTML5 Hurdles article, is usually about fallback support and making it work in every web browser. But do we really need that?
This morning I was notified of an article about the download rate of IE9 by Ryan Gavin, Senior Director, Internet Explorer Business and Marketing. I had to check the date to see that it wasn’t an April Fool’s joke; alas, it wasn’t, so here’s my reply.
Yesterday I attended the Stockholm Web Monkeys’ spring 2011 meetup in Stockholm, and I gave a short presentation and led a discussion about HTML5 – What’s good, what’s missing, web browser implementation takes.
I wrote about it on Twitter last week (follow me on Twitter!), but naturally I should mention it here too, my dear readers. With new input from testing Internet Explorer 9 and from the Opera team, I have updated my HTML5 tests and compatibility tables and CSS3 tests and compatibility tables.
Microsoft recently launched their Dev:unplugged HTML5 competition, to create outstanding showcases.
By using a combination of the
<canvas> element and the File API we could put together a little service that offers “The Cure” for many people.
As always, there is so much discussion going on about HTML5 and video on the web, and I thought I’d suggest a solution to it all.
Last night there was an interesting announcement from the WHATWG group, who effectively develops various HTML5 and related specifications. That is, HTML5 is no more.
Yesterday Google announced they’re dropping H.264 video codec support in Google Chrome. Whatever you think about this, it’s an interesting move and I thought I’d express my thoughts on it.
With HTML5 video and the current support in web browsers, we need to cater to different codecs, and fallbacks for web browsers with no native
video support. This is where Video JS steps in.
To me, something about HTML5 that makes it quite interesting is all the new support for file interaction. I’ve written about the File API and reading file information before, and I thought I’d expand on that and add uploads and progress bars.
I just encountered the weirdest bug with the HTML5
autofocus attribute in Google Chrome and Safari.
For a long long time we have tried to be able to push information from the server out to the end users without having to poll the server all the time.
Time for the first Geek Meet this fall! Can you believe it’s been four months since the last one? This time around, it’s time to bring in a guest from the UK.
Seasons come and seasons go; life turns in a constantly changing manner. But, as after every summer, I’m back and I long to write for you!
I continually talk about HTML5 and how progressive enhancement is a simple approach to make any new behavior possible in web browsers that haven’t implemented it yet. I thought I’d show you a simple example how to do this with the new
placeholder attribute for
A couple of days ago, Apple announced support for developing extensions, so I felt obliged to implement my HTML Validator extension for Safari too.
I don’t think I’m exaggerating when I’m saying something really really important has happened for the future of the Open Web. Finally, it looks like there might be a solution to the video codecs and patent encumbered alternatives we have been dealing with.
It is soon summer (Yay!) and about time for a last Geek Meet before a summer break!
A constant drag when developing web sites have been when the end user wants to upload files to it. Luckily, though, those problems are to come to an end due to the File API.
In a world where we carry our computers/Internet-connected devices with us all around, we’re bound to lose connection now and then but still want to be able to continue our work. That is where Offline Web Applications steps in.
June 2-3 third this year a number of high-profile speakers are coming to Stockholm, Sweden, to talk at the SWDC 2010 conference, organized by Peter Svensson (who also organizes the GTUG events in Stockholm).
There’s an inner beauty of HTML code that I can never seem to get away from. The wonderful world of semantics – choosing the right element for the right task, something that conveys meaning, makes it more accessible and strikes the perfect balance of different parts of a web page. Which moves us on to Content Management Systems.
When performing advanced load-heavy operations in a web browser, both the web page it is run in as well as the web browser UI becomes unresponsive till it’s finished. However, there’s a way to address that with HTML5 Web Workers.
With more and more people getting faster Internet connections, and video being one of the ultimate online multimedia experience (so far), it was due to get native
video elements in web browsers. However, open video is threatened by codecs and patents, and I thought I’d discuss the situation and possible outcomes here.
Ever had the need to communicate between windows or the current window and an inner iframe? Across domains as well? I bet you have, but now we have a nice option for doing that!
At MIX10 yesterday, Microsoft announced IE9 and spoke about its upcoming features. And, lo and behold, they released a Internet Explorer Platform Preview for anyone to download and play around with!
Time for another Geek Meet, and this time, we’l be trying something new.
I think we can all agree that performance of web sites matters a lot, and slow web sites are very annoying both for developers and, more importantly, end users. Therefore, we need to talk about a newly discovered problem: Internet Explorer, protocols and inclusion of stylesheets.
Last weekend I had the pleasure of going to FOSDEM to give a presentation about HTML5 and to experience a very big open-source conference.