News for hackers. Stuff that matters.
Re:Two.js by gondo on Thursday July 16, 2015 @03:50PM (#9899494)
what is meant by "modern web browsers"?
Re:Two.js by m3Lith on Thursday July 16, 2015 @03:55PM (#9899523)
I guess it would be something along the lines of this quote from http://farukat.es/journal/2011/02/528-modern-browser: "A modern browser is any browser that: successfully renders a site that you just built using web standards, testing only in your browser of choice along the way, with all the essentials functioning well; without you having written any browser-specific hacks, forks or workarounds; and shows great performance as you navigate it."
Re:Two.js by yellowapple on Thursday July 16, 2015 @07:52PM (#9900592)
In other words, "modern browsers" might as well be mythical creatures :)
Re:Two.js by jonobr1 on Thursday July 16, 2015 @03:59PM (#9899546)
Roughly, self updating html5 compliant browser.
Re:Two.js by yellowapple on Thursday July 16, 2015 @07:53PM (#9900596)
Why self-updating? Is my version of Firefox non-"modern" simply because I install and update it through my operating system's package management system?
Re:Two.js by yoklov on Friday July 17, 2015 @01:24AM (#9901379)
It is if you updated it recently.
Re:Two.js by RobertKerans on Friday July 17, 2015 @12:38AM (#9901291)
In general as regards SVG [and canvas in this case], not IE <=8 or Android <= 2.4, and some caveats (eg will need careful testing, as some JS/DOM APIs or rendering optimisations may not be present) with earlier versions of FF/Chrome/Safari & IE9/10
Re:Two.js by gondo on Saturday July 18, 2015 @04:48PM (#9908854)
what about in a year? i bet you would list different browsers and versions. my point is, "modern browser" doesn't mean anything and it change as time passes
Re:Two.js by RobertKerans on Thursday July 23, 2015 @08:36AM (#9935268)
True, it should specify where support drops off really, it's not as if there aren't tools to automate the JS testing part of it if the time isn't there to thoroughly manually check. I've think maybe spent too much time assessing JS libraries & frontend stuff; after a while when you see 'modern browser' you mentally tick off where it's likely to be functional and accept/discount the guessed tradeoffs (maybe a bad habit)