Intent to Deprecate: CSS font loading's ready as a function in favor of ready as an attributehttps://groups.google.com/a/chromium.org/d/msg/blink-dev/XqKrqbMEsZA/N4yQ_supV4sJ
So a dev notified blink-dev that the removal of the old CSS Font Loading API caused a compat problem.
> This caught me out today. We had production code using document.fonts.ready() which started throwing errors in Chrome 41 before we'd had time to notice the console warnings and apply a fix. Perhaps my code should have been more defensive but I had no idea the spec was likely to change. The transition period was too short, in my view.
Perhaps yes the transition/deprecation period was too short. Perhaps Blink's launch process has became a bit flawed from a compat standpoint. Perhaps console warning has never caught attention (I'm sick and tired of DevTools saying to use CSS dppx unit). Perhaps, perhaps...
But, I've been wondering, why don't devs test the site/app with Canary (or Developer Edition)? Going further, why don't devs use Beta instead of Stable/Release channel builds? By doing so such "transition period" could be extended by a month and a half or three. Using Beta or Dev channel builds is not just playing with cutting-edge Web platform features, but also avoiding such future breakage.
Are there any particular reasons to avoid developing with Beta/Dev/Canary builds?