4 ms·
As soon as browser support the standard, the message will be shown less and less. Chrome was an early adopter, but Audio Worklets are part of a W3C working draf
by janesconference 8y ago
As soon as browser support the standard, the message will be shown less and less. Chrome was an early adopter, but Audio Worklets are part of a W3C working draft, which is the de facto standard for web audio:
https://www.w3.org/TR/webaudio/ https://www.w3.org/TR/webaudio/
- lloeki 8y agoQualifying browsers that don't follow an early adopter in implementing a working draft of being "old" is kind of odd and disparaging. A simple message like "Sadly your browser does not seem to support spec foo yet, but you can try one of those: browser X v>42, Y, Z".
- dkersten 8y agoThere’s an “or” in that sentence: “old or unsupported browser”
- giancarlostoro 8y agoThe term unsupported browser sounds like it's intentionally only for Chrome.
- janesconference 8y agoThat's true, that's inaccurate. I'll change the message with the next deploy.
- dkersten 8y agoI’m not saying that the message sounded good, I’m just saying that it’s technically accurate. Other browsers don’t support the bleeding edge features the site needs and therefore they’re unsupported.
- te_chris 8y agoNitpicking cool projects is also pretty disparaging.
- janesconference 8y agoSorry if I hurt any browser's sensibility. Hope no browser was offended by my app :) However, I didn't refer to "browsers that don't follow an early adopter in implementing a working draft" as "old", though; if you read the compatibility message carefully, you'll find I referred to them as "unsupported" (which might be a bit inexact but not disparaging). Non-evergreen browsers, instead, are correctly referred to as "old", because they are.
- gcb0 8y agoCalling it a standard might be jumping the gun. from your very link > Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
- janesconference 8y agoI guess so. But then again, there's a bunch of people who are taking care of the draft and browser vendors will probably implement it soon. In the ever changing world of web development, that's as close to a standard as you get, if you don't want to wait years. But yep, technically it's a W3C draft, which might change and which I'm actively monitoring.