[citation][nom]Pherule[/nom]Maybe you should jump off your pedestal and take a seat. In the corner.1. HTML5 is notoriously difficult to block.2. Some browsers don't play nicely with HTML5.Do I really need any more reasons? Nope, I didn't think so. Being unable to automatically block a video in a webpage is a huge no in my book."XHTML? HTML 4.1? HTML 3"We weren't discussing these. I don't give a flying **** about them as long as they don't break webpages.[/citation]1. Considering the number of sites using HTML5 is still miniscule compared to those using Flash, can anything about HTML5 really be called "notorious"? :-D
In reality it doesn't really make sense to "block" HTML5 as a whole, as it introduces a whole plethora of new web standards improvements. But there's no real difficulty involved in preventing 'active' (Flash-esque) content from displaying. All a browser or add-on developer would need to do is simply remove < video >, < canvas > and/or < audio > elements, depending on the user's preference. Blacklists and whitelists could be formulated, just as is done with Flash blockers. I have no doubt we'll see numerous blockers in browsers and their add-ons as HTML5 becomes more prominent.
2. Considering that HTML5 standards are still being worked on, is it any wonder that browser developers are still working on supporting it? Did browsers play perfectly with HTML4 back in 1997? Because they didn't, should we have hated HTML4?
In reality it doesn't really make sense to "block" HTML5 as a whole, as it introduces a whole plethora of new web standards improvements. But there's no real difficulty involved in preventing 'active' (Flash-esque) content from displaying. All a browser or add-on developer would need to do is simply remove < video >, < canvas > and/or < audio > elements, depending on the user's preference. Blacklists and whitelists could be formulated, just as is done with Flash blockers. I have no doubt we'll see numerous blockers in browsers and their add-ons as HTML5 becomes more prominent.
2. Considering that HTML5 standards are still being worked on, is it any wonder that browser developers are still working on supporting it? Did browsers play perfectly with HTML4 back in 1997? Because they didn't, should we have hated HTML4?
Facebook
Twitter
Instagram