Pony99CA wrote:If somebody does not have a "modern browser" (whatever that means ), does it gracefully degrade to the previous experience?
Steve
The term 'modern browser' here refers to one that supports HTML5, particularly the file API.Pony99CA wrote:If somebody does not have a "modern browser" (whatever that means ), does it gracefully degrade to the previous experience?
Steve
OK, thanks. As a suggestion (and not just for you), people should say "HTML 5-capable browser" if that's what they mean. "Modern" could mean HTML 5 support, CSS 3 support or even anything newer than IE 6.Fyorl wrote:The term 'modern browser' here refers to one that supports HTML5, particularly the file API.Pony99CA wrote:If somebody does not have a "modern browser" (whatever that means ), does it gracefully degrade to the previous experience?
I presumed that it would, but just wanted to be sure.Fyorl wrote:To answer your question, if the browser doesn't support the new uploader, the user will simply see the old one which will still function just as it always has.
Since the people in charge of html5 decided to not ever stop changing html5, there will never be a browser implementing all of html5, and as such "HTML 5-capable browser" is fairly meaningless.Pony99CA wrote: OK, thanks. As a suggestion (and not just for you), people should say "HTML 5-capable browser" if that's what they mean.
I think the same is true of CSS 2 and CSS 3; many browsers support parts of them but not the whole thing. Nonetheless, saying "HTML 5-capable" or "CSS 3-capable" is still more useful IMHO than saying "modern". The only truly precise option would be to specify browser versions, which would become unwieldy; my suggestion provides more precision than "modern" without being so verbose.Oleg wrote:Since the people in charge of html5 decided to not ever stop changing html5, there will never be a browser implementing all of html5, and as such "HTML 5-capable browser" is fairly meaningless.Pony99CA wrote: OK, thanks. As a suggestion (and not just for you), people should say "HTML 5-capable browser" if that's what they mean.
The HTML5 specification has not been finished yet; however many browsers support [some/most] of the current HTML5 features. If I recall correctly the W3C's timeline was to have a full specification and to give it a W3C Recommendation in 2014 but I'm not sure if that is still the case.Oleg wrote:Since the people in charge of html5 decided to not ever stop changing html5, there will never be a browser implementing all of html5, and as such "HTML 5-capable browser" is fairly meaningless.Pony99CA wrote: OK, thanks. As a suggestion (and not just for you), people should say "HTML 5-capable browser" if that's what they mean.
Thanks for clarifying that. I guess that means that there won't be an HTML 6.naderman wrote:HTML5 is a "living standard". There is no versioning anymore HTML5 is just HTML. There won't be any later versions either, since HTML now just evolves. As such there simply is no HTML standard that can be fully implemented, but only ever the HTML standard at the time. And there won't be any final version either.
See http://blog.whatwg.org/html-is-the-new-html5