Happy Hardware Accelerated Holidays
Here are two new HTML5 experiences you can run in your browser, designed in the spirit of the holiday season and with hardware accelerated HTML5 in mind.
Check out Santa’s Workshop, where the speed of your browser on your PC determines how many elves help pack Santa’s bag for the big night, and how fast they work. We built this experience using HTML5 technologies like integrated SVG graphics and HTML5 audio.
See how big of a storm your browser and your PC can kick up with HTML5 Blizzard. Your snowflake score shows you how many falling snowflakes can be animated in real time (60FPS). The more snowflakes you see, the faster your browser and PC. This experience combines HTML5 canvas, SVG, audio, CSS3 and WOFF fonts together to create a winter wonderland.
Just over a year ago we presented the earliest look at IE9 and how browsing experiences are better through the power of underlying hardware and operating system. Starting in March at MIX 2010, and throughout the year, we demonstrated our approach to bringing full hardware acceleration to the web in IE9. We showed continuing progress with the release of seven platform previews, the IE9 beta, and through samples on the IE test drive site.
We showed how web applications built on the next generation of hardware accelerated HTML5 approach the level of interactivity and performance found in native apps, and we had some fun along the way (as did many partners) – we hope you did as well.
Thank you!
Your participation and feedback is an important part of how we build IE9. Today we want to say thank you to everyone who has downloaded IE9 beta and previews, run the test drives, reported issues on Connect, or submitted feedback through the Send Feedback (alt+X, K) in IE9 beta. We also want to thank the people and groups who make the standards process work, the broad community of web developers, and enthusiastic consumers who work to move the web forward.
From the entire IE team, we wish you a happy hardware accelerated Holiday season, and we look forward to another exciting year on the web in 2011.
Rob Mauceri
Group Program Manager, IE
Comments
Anonymous
December 22, 2010
And a Merry Christmas to you, too. ( Happy Holidays, tssssch....) <insert appropriate smiley here>Anonymous
December 22, 2010
The comment has been removedAnonymous
December 22, 2010
"This demo requires ECMAScript 5 properties API support. We recomend you upgrade before proceeding. If you would like, you can try the demo anyway with your current browser by clicking here." It's "recoMmend".Anonymous
December 22, 2010
Not sure who programmed this demo, but it is doing anything special, you don't need to have hardware acceleration for this. I tried the demo's in different browsers and the first demo didn't work in IE9 at all. In other browsers atleast one demo didn't load, but the browser didn't have anything to do either. So it seems to have crashed, maybe someone needs to learn how to do things x-browser. Maybe the person that created the demo should do more testing. Especially on different machines with different graphics drivers. The inline SVG worked best in Firefox 4 Beta, the Javascript performance was best in Google Chrome and IE9 was just confused.Anonymous
December 22, 2010
The comment has been removedAnonymous
December 22, 2010
@Jace: cool story bro.Anonymous
December 22, 2010
3 snowflakes in opera, 3 in firefox, IE preview works like a storm (pardon the pun) But somehow I don't believe this has anything to do with hardware acceleration. Are these demonstrations contrived to make other browsers look bad, (it crashed in chrome completely!)Anonymous
December 22, 2010
@blepore: Sorry to hear about the audio issue, are you running IE9 Beta? This is a known issue that we saw on a small number of machines with the beta release.Anonymous
December 22, 2010
Great performance with IE9-P7. I get 11 Elf's and 85 packages/minute and I get 2400 snowflakes. Processor Intel(R) Core(TM)2 Duo CPU E7400 @ 2800 Mhz, 2 Core(s), 4GB RAM, Nvidia GT8600Anonymous
December 22, 2010
Great Work By IE Team.IE surely rocks. http://thetechbytes.comAnonymous
December 22, 2010
Yup. Version 9.0.7930.16406 if that matters. I didn't try it in the latest platform preview. Is there a reason why the betas aren't kept up to the rendering of the previews?Anonymous
December 22, 2010
works fine here (also 9.0.7930.16406). ~500 Snowflakes on my old and underpowered Latitude D820 (Intel T7200 2GHz, 4GB RAM) Compare to: FF and Safari on my buddy's Mac Pro (Dual Quad Xeon 2.8GHz, 8GB RAM) - 3 (in words, "three")Anonymous
December 22, 2010
I'm using IE9 beta, yet both these demos insisted i was using IE7. Just in case you're wondering, version 9.0.7930.16406. Other that that, I really do like IE9.Anonymous
December 22, 2010
@John Perhaps you had compatibility mode turned on?Anonymous
December 22, 2010
I hate to repeat this here but once a post on the IE blog is not the latest post it gets ignored. Can someone from Microsoft please make a statement about shutting down the IE6/IE7/IE8/IE9 images at http://www.spoon.net/ ====================================================================================================== This was THE most useful resource for testing multiple versions of IE and the shutdown really ticked developers off! As a long time web developer of Enterprise Web Applications I've tried all the options out there to try and simplify testing IE and the lack of realistic options is a royal PITA. 1.) Multiple IEs - IE8 breaks the functionality of IE6's textboxes - thus its a NO-GO 2.) IETester - works great until you need to test popup interaction and then it fails - thus a NO-GO 3.) Virtual PC with timebombed images of IE6, IE7, IE8 - works ok, but the 12Gigs of HD space needed is frustrating when each full image of Windows dies 4 times a year, running a full Windows image is slow and you have to beg for updates because the releases are not co-ordinated and announced well at all - thus its a NO-GO 4.) IE Super Preview - Last I checked this did not allow full testing of IE user interaction, JavaScript DOM changes, popups etc. - thus its a NO-GO 5.) Multiple PC's to run multiple versions of windows and IE. With all the hardware, software, and physical space needed - its a NO-GO 6.) Spoon.net IEs - They work, they work just like local native apps once running, and there's no hacking of my real local IE install. - the ONLY problem with these IE's is that Microsoft shut them down Please understand that we (developers) just want something that works. Testing in multiple versions of IE is a pain to begin with and with IE9 on the horizon it is only getting worse. I'm not sure where the issue stands with Spoon, but I would really like a solution worked out fast. SteveAnonymous
December 22, 2010
The comment has been removedAnonymous
December 22, 2010
the blizzard demo doesnt work on chrome 10 unless you resize the window to ~350x350. Then I get ~700 on my processor. I got ~420 on latest minefield and ~1989 on IE9pp7.Anonymous
December 22, 2010
CvP even doing that, I only get sound and background image but nothing else.Anonymous
December 22, 2010
<strong><a href="blogs.msdn.com/.../happy-hardware-accelerated-holidays.aspx You can disable the GPU acceleration in Internet Options. Go to the Advanced tab and it's the first option.Anonymous
December 22, 2010
<b><a href="blogs.msdn.com/.../happy-hardware-accelerated-holidays.aspx You can disable the GPU acceleration in Internet Options. Go to the Advanced tab and it's the first option.Anonymous
December 22, 2010
Merry Christmas and gud job guys !!Anonymous
December 22, 2010
@Harold: JavaScript is JIT-compiled in IE9, this brings speed improvements that are independent from GPU acceleration. Else it wouldn't do so well on JS benchmarks, many of which do not test graphics-related stuff. In other words, if you turned off GPU acceleration (if possible in IE9, dunno about that), JavaScript would still be much faster than in IE8.Anonymous
December 22, 2010
Merry Christmas from finland! ;) Good job!Anonymous
December 23, 2010
Merry Christmas IE9 team =]. and thanks for all the hard work!Anonymous
December 23, 2010
I only got 3 snowflakes on my corporate Vista computer from Dell.Anonymous
December 23, 2010
@Bill Gates II - I'm using the latest platform preview which does not contain a tools > internet options menu item - thus no luck :-( I'm glad to hear that it is an option in the browser though - the only question is will it be disabled by default considering that there isn't any good throttling available for the usage? Or will throttling be added to the final release to ensure that IE9 does not cause hardware damage?Anonymous
December 23, 2010
IE Beta Snoflakes: ~950 IE PP: ~2500 HP ElitebookAnonymous
December 23, 2010
The audio doesn't work in Firefox 4. The Santa's Workshop page has the audio block as: <audio loop="true" autoplay="true"> <source src="media/song.mp4"/> <source src="media/song.ogg"/> </audio> It is very encouraging to see Microsoft constructively embrace the web and make use of an open audio format (something that should also be done with all video on this blog). Sadly, however, media/song.ogg does not exist on the site and returns a 404.Anonymous
December 23, 2010
And similarly for HTML5 Blizzard. Its audio block tries to use Audio/HolidayJazz.ogg but HolidayJazz.ogg is missing from the Audio directory. So an upload of song.ogg and HolidayJazz.ogg will fix both issues.Anonymous
December 23, 2010
Happy non customizable holidays!!Anonymous
December 23, 2010
Thanks for developing IE9, but when it done, can you destroy all of the version before on the world??? (which means IE6, 7, 8) You should have some strategy to let IE users to use the latest version, not stay in version 6, 7, 8 IE6 ,7 8 waste a lot of web developers life. thanks again.Anonymous
December 23, 2010
Hello again! :) My results: HTML5 Blizzard: Internet Explorer 9 Beta: ~0340 Internet Explorer Platform Preview 7: ~2040 Santa's Workshop: Internet Explorer 9 Beta: 09 presents per minute Internet Explorer Platform Preview 7: 25 present per minute HP Pavilion (2008 series) Amazingly, I have never followed this development closely, this is interesting to watch. I love my favorite browser ever more and more ... ;)Anonymous
December 23, 2010
The comment has been removedAnonymous
December 23, 2010
Er that should be... "...In making IE a standards based browser..."Anonymous
December 24, 2010
@William - In IE9, an exception is thrown when using document.createElement with HTML markup.Anonymous
December 25, 2010
When the IE9 is official releases, it's the time that css4 & html6 release.Anonymous
December 26, 2010
Why do the elves go on strike after a minute or so? The number then gradually drops from 10 to only one. This is both in the beta and the PP7, hardware accel. is enabled.Anonymous
December 26, 2010
The comment has been removedAnonymous
December 26, 2010
Nick,how easy it is to turn it against browsers not supporting mp3 and H264 it makes one wonder why are you posting such illogical comment.Anonymous
December 26, 2010
Santa Workshop IE 9 Beta 64bit 21 elves working 240 presents per minute Snowflakes 2004 Machine Core i7 920 @ 3.6 Ghz + Radeon 4890 + Intel 160GB G2 SSDAnonymous
December 26, 2010
Santa Workshop IE 9 Beta 64bit 21 elves working 240 presents per minute Snowflakes 2004 Machine Core i7 920 @ 3.6 Ghz + Radeon 4890 + Intel 160GB G2 SSDAnonymous
December 27, 2010
The comment has been removedAnonymous
December 27, 2010
Oh one other really annoying thing. The IE9 preview application has done something funky with scrollable regions (including the main application window) such that they don't work with many trackpad scrollers. E.g. on any Lenovo trackpad, I can't scroll the main window, or any scrollable area inside the window using the trackpad scroller. This works fine in any other application in windows - just not the IE preview which is REALLY annoying! I also had issues on an ACER laptop and I believe a Toshiba? (can't recall the brand) Please fix this in the next preview so that we can properly test IE9.Anonymous
December 27, 2010
The comment has been removedAnonymous
December 27, 2010
Supersparky when I run this in chrome I get 14 elfs working! IE9 beta gives me 21 elfs Doesn't work in Firefox 3.6 for me cause there is no API support.Anonymous
December 27, 2010
The comment has been removedAnonymous
December 27, 2010
Dear MS, you have forever lost at least one loyal IE1-8 user because of the dumbed down non customizable UI and your craze for "reduced concepts" as you put it.Anonymous
December 27, 2010
I reported that most blogger's blogs IE9 work too slowly to Beta, I wish you could provide some support for these sites. Thanks.Anonymous
December 28, 2010
Ha. I see the audio issue has been "fixed" by removing references to the Vorbis version from the source of Santa's Workshop and HTML5 Blizzard. What a delightful farce. You stay classy, Microsoft.Anonymous
December 29, 2010
Any chance IE9 will support the new "async=false" script property standard that is being proposed by Kyle Simpson, creator of the LABjs script loader? Firefox and Webkit browsers already have it implemented in their beta versions, and it looks like it could help significantly improve script loading performance in a clean, standards-friendly way.Anonymous
December 29, 2010
When using an accelerator (like the default Google Maps), the adress bar is in edit mode after the Google Maps page has been loaded. This prevents zooming the map directly. This is also a problem for IE8, could you fix this please?Anonymous
December 30, 2010
The comment has been removedAnonymous
December 30, 2010
@Phil: "...implementing half of the standards..." You may be under the impression that OGG Vorbis is part of HTML5. That is not the case.Anonymous
December 31, 2010
The comment has been removedAnonymous
December 31, 2010
Shame? None at all. They might have planned and then decided "not worth it". As for support in other browsers, there are open soure libraries. There are ways in majority of common OSes how to load them if they are installed without them being linked in thus no trouble with licences. (AFAIK:VfW,DirectShow,gstream,...) But then those vendors would have to want. And they don't want for ideological reasons... Standard doesn't specify,so MS takes safest route for it (already licensed with patents being cleared or part of lic.) Last time I checked there was awfull lot of sw patent lawsuits. MS didn't break anything. (there was nothing to break in the first place - so far) And if OGG (btw I like the format,but don't think its that important yet) or something becomes popular they can add support (unless submarine patents are in waiting...) as with WebM. Is there anything else you(all) wish to rant about?Anonymous
December 31, 2010
IE9 is still betaAnonymous
January 01, 2011
PLEASE IE9 MUST HAVE STANDALONE DOWNLOAD MANAGER ICON ON WINDOWS 7 TASKBAR. PLEASE DO NOT COMBINE DOWNLOADS WITH MAIN IE9 ICON. EVERY TIME WHEN I DOWNLOAD SOMETHING IN IE8 AND MY MOM WANNA GO ON THE INTERNET, SHE CLICKS ON IE ICON, UNMINIMIZE ACTIVE DOWNLOAD, BUT SHE DOES NOT UNDERSTAND WHAT IS GOING ON, SHE CLOSES THE DOWNLOAD WINDOW :( AND RE-LAUNCH IE8 AGAIN TO BROWSE THE WEB... PLEASE IE9 MUST HAVE ON TASKBAR STANDALONE ICON FOR TRIGGERED DOWNLOADS, THE SAME WAY LIKE CONTROL PANEL ICON IS STANDALONE, EVEN IF IT IS ONLY NEW EXPLORER WINDOW...Anonymous
January 02, 2011
Nice real-world test for performance is http://store.steampowered.com/ . Unfortunately it reverts back tomorrow at 19:00 CET (GMT+1) . Seems that so far only IE8 is slow unlike IE9. (page animation should be smooth)Anonymous
January 02, 2011
Internet Explorer 9 Release Candidate (RC) due on January 28 Read more here: www.neowin.net/.../965266-internet-explorer-9-release-candidate-rc-due-on-january-28Anonymous
January 02, 2011
Internet Explorer 9 Release Candidate (RC) due on January 28 Read more here: www.neowin.net/.../965266-internet-explorer-9-release-candidate-rc-due-on-january-28Anonymous
January 02, 2011
The RSS feed address on your blog is wrongAnonymous
January 03, 2011
Please, if you really want to have a lasting and positive effect, just leave the browser market and delete all copies of IE world wide. Thanks in advance.Anonymous
January 03, 2011
@"The Internet" : Things would be much better if you would stop interfering with Real Internet and trolling. Many thangz.Anonymous
January 03, 2011
@Klimax you seem to miss the point about the broken web with innerHTML. It is broken in IE and as long as it remains broken IE9 will absolutely NOT be HTML5 compliant in the slightest... never mind the missing form stuff and lack of geolocation just to name a few. Rumour above has IE9 RC due out at the end of January - if this is so that would be awesome I'd be very glad to see all the things fixed in the latest release to make it a decent browser. For now, the Platform Preview 6 is NOT adequate enough for the next release as there are too many missing standards and far too many that are still broken.Anonymous
January 03, 2011
@nicolas(10:18): geolocation? For what??? I think you get it on WP7 port of IE. Not to mention it is not part of HTML5. Don't know about innerHTML. I'll checkout svn repo to see how it changed and how often - can be further guide to what we might see in´mplemented beside annouced stuff. But what I heard original extending innerHTML is different from HTML5 which might be compatibility nightmare. (especially with sites still doing bad version check and declairing standard mode) BTW:What comment you responded? The one from 10:11 was more joking at troll then anything else...Anonymous
January 03, 2011
@klimax - GeoLocation is one of those HTML5 "related" technologies that just makes HTML5 an awesome leap forward from HTML4. The fact that IE8 didn't support it and IE9 STILL doesn't support it is just sad and makes Microsoft look incompetent. Its just like how IE is the only major browser in the market that doesn't come with a spell checker in 2011 - that's not just sad - that's a disgusting disgrace. I think what was being mentioned about the innerHTML is the fact that it has been broken in IE since it was first added and in HTML5 it is actually part of the specs thus now Microsoft's previous "omission" is now a serious infraction against the HTML5 specs. Bugs: webbugtrack.blogspot.com/.../bug-179-innerhtml-love-outside-body-is.html webbugtrack.blogspot.com/.../bug-210-no-innerhtml-support-on-tables.html webbugtrack.blogspot.com/.../bug-274-dom-methods-on-select-lists.html I don't know if internal builds of IE9 have got these issues fixed yet but quite simply IE9 can't legitimately go RTW and not undergo major criticism and dis-satisfaction from the developer community until these issues are resolved. donAnonymous
January 03, 2011
Geolocation last time I checked is mostly useless on regular HW like desktop or notebooks (generally lack GPS or GSM/... for position determining) so IE9 won't need that. IE9-WP7 edition is completely different matter as there is at least one method for use. As for innerHTML-compatibility with pre-HTML5 otherwise standard compliant webpages using other things like CSS3,SVG and some other parts of HTML5 or ECSMAScript- how do you solve it?Anonymous
January 03, 2011
The comment has been removedAnonymous
January 03, 2011
er... I meant "their failure" (tail between legs)Anonymous
January 04, 2011
@steve How was innerHTML broken in IE since "day 1"? Microsoft is the inventor of the feature. They designed and implemented it as they chose at the time. Others implemented it and then extended it. If Microsoft had done the same with a similar feature, the ABMer would be up in arms screaming "Microsoft is extending _______!! :-O; they're going to break teh interwebz!!" Don't be shy now, tell me, how was it "broken in IE since day 1"? :-DAnonymous
January 04, 2011
The comment has been removedAnonymous
January 04, 2011
www.informationweek.com/.../showArticle.jhtml any microsoft offical or any updates on microsofts view of thisAnonymous
January 04, 2011
Growl!!! the spam filter on this blog is very, very, very annoying! It looks like the spam detectors on this blog really don't like hyperlinks! even if they all point to an HTTPS site in Microsoft's own list of sites. For the record, here's a few of the bug reports in MS Connect regarding IE's broken innerHTML issues: http://pastebin.com/cs4d1A0F hopefully just 1 link will be okay (it wasn't 2 minutes ago, but...) anyway it links to a few (16) different innerHTML bugs filed in Microsoft's Connect DB. Most are long standing issues, some are brand new to IE9. If this doesn't work I'm going to try a different username and or computer to get around the aggressive filtering.Anonymous
January 04, 2011
I forgot: "Otherwise CSS3, SVG, Canvas, ECMAScript, etc. have nothing to do with MSFT fixing their innerHTML. (the exception being that setting and getting innerHTML is called from JavaScript)" Sites might use old behaviour of innerHTML (without proper checking - altough one might hope situation will improve) and CSS3ECSMAScript(5?) together. Try to maintain compatibility with such site and introduce new innerHTML behaviour. I hope this is just theoretical thing and nowhere to be seen in practice,but last time I checked too many programmers/webdesigners/webprogrammers are lazy or whatever and such combination exists. P.S.:I already wrote one comment on geolocation, but it is nowhere to be seen...Anonymous
January 04, 2011
Geolocation - currently of same acuracy as IP address. At earlest better adoption of Sandy Bridge(AFAIK has 3G) or other integrated 3G devices. But then Compatibility/Upgrade Libraries like PIE will provide similar or same API. Good enough on desktop/notebook. AFAIK WP7-IE doesn't support GeoAPI. I would want first HTML5 itself and CSS3 and maybe IndexDB first, less usefull APIs later. And those APIs might be used throughplugins from MS Lab anyway. (Like Websocket/IndexDB) Anyway I read that link to Eric Vasilik and seems that what was true back then still remained true today. Backward compatibility... (most probably reason why we didn't heard about HTML5-innerHTML ; still didn't find/finished-testing good way for support of old-broken and new) (second try)Anonymous
January 04, 2011
The comment has been removedAnonymous
January 04, 2011
The comment has been removedAnonymous
January 04, 2011
The comment has been removedAnonymous
January 04, 2011
@Steve, Built-in limitations don't equate to bugs. I don't disagree that Microsoft could improve the feature and update it to match what has now come to be a formal spec. Also, I actually read the article. You put some things in quotes in your reply that are not found in the article, in the same paragraph you start with "As you can digest from Eric's notes..." Are you quoting yourself? Aren't we in a position where other vendors improved upon and extended and Microsoft feature, and Microsoft has lagged behind and needs to address it to come to feature parity / full spec implementation? I don't see the need to paint things as something they are not/re-write history... :-)Anonymous
January 04, 2011
The comment has been removedAnonymous
January 04, 2011
@Steve, Logic fail: "Its a bug, has been declared a bug by everyone including Microsoft" then you say: "We would all be much happier if they actually stood up and accepted the issue. e.g. "We agree this is a bug in our implementation..." Which is it? Next: Classic snow-balling/kitchen-sinking arguments. "Lets not forget that IE was the only browser..." What does that have to do with the price of rice in China? I asked a very specific question, and watch you dance around the topic. Working as designed can be a cop-out, but you use it as a blanket straw-man where it doesn't fit. The article you linked to specifically explains how it is working as designed and that the design has limitations, period. Calling those limitations bugs does nothing other than gloss over facts.Anonymous
January 05, 2011
@Jace not a logic failure. Separate statements with different context. "Its a bug, has been declared a bug by everyone including Microsoft" (other than a few people like yourself, everyone agrees this is a bug, including the MSFT employees I've communicated with and the guy who wrote the code) New context: "We would all be much happier if they actually stood up and accepted the issue. e.g. "We agree this is a bug in our implementation..."" - even though we (the development community) all agree it is a bug, and MSFT developers agree, the MS Connect Feedback channel (the only public facing bug-tracking MSFT has) declares all issues it doesn't want to fix (for whatever reason) as "works as designed" which is not a confirmation that it is a bug. The "works as designed" is a bogus statement in itself because ALL code works as designed. If I build a Hello World app that doesn't quote the string "Hello World" then my app will fail... but it "works as designed". I guess I would appreciate it if Microsoft changed their bug tracking to properly address bugs. Each issue submitted first needs a flag indicating that the issue as described is "verified" as occurring (e.g. is reproducible). Then it needs a flag indicating if the issue is a "bug" or a "misunderstanding", etc. e.g. the browser does do something weird, but you passed it a negative integer when it was expecting a positive index... don't do that. Then finally it needs a flag indicating what Microsoft's intentions are. Are they "declining" the bug?, "prioritizing" it?, "accepting" it and targeting it for a given release?, or "postponing" it for a future release. Ok, now for what you call snow-balling. I was merely trying to hammer home a point that this is not the first time that Microsoft has failed to implement something properly then turned around and claimed that it "works as designed". document.getElementById(id) is a classic case of how for multiple releases IE's version of this method did not match the published specs and it was not because the implementation was somehow unclear, ambiguous or needed additional options. It wasn't until IE8 was released that IE fixed this properly to return the correct element every time (as long as you are in Standards Mode) You are correct though. You did ask me a specific (yes/no) question and I didn't answer it with a (yes/no) answer. Your question: Are you quoting yourself? My answer: No. My elaboration: I was using air quotes. To ensure that I correctly respond to your last note about how "limitations by design" (air quotes) are not bugs, here goes. Definition of "Software Bug" by Wikipedia: en.wikipedia.org/.../Software_bug "A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. " Does IE produce an incorrect or unexpected (error) or (fault)? YES Does IE behave in unintended ways? YES Are developers describing this as an (error), a (flaw), a (mistake), a (failure) or a (fault)? YES You can argue that you personally do not feel it is a bug all you want. The jury of the "Developer Community at Large" (your peers) were convinced this was a bug years ago. Failing to make a "global" property/method work on all the "things" it is supposed to is a bug. As for me I'm not going to play your Troll game anymore. If you think that the current implementation of innerHTML in IE is great - perfect. However if IE9 gets released and the (not-a-bug-according-to-you) isn't fixed, IT WILL BE A BUG IN HTML5 - without exception.