Since sending this intent to ship, questions have been raised over the suitability of the frames() name.[1]
In order to allow the standards discussion to play out without being bound by shipping implementations, Chrome have decided to abort shipping their implementation to the release channel for the time being.[2][3] Since that discussion has still not reached a conclusion we should do that same. Our implementation is currently set to ride the 55 train (current beta) so I have filed bug 1379582 ( https://bugzilla.mozilla.org/show_bug.cgi?id=1379582) to put this feature behind a pref and turn it off for beta/release. Brian [1] https://github.com/w3c/csswg-drafts/issues/1301 [2] https://groups.google.com/a/chromium.org/d/msg/blink-dev/j7l8_DjMsVE/0HKZgZXNAQAJ [3] https://bugs.chromium.org/p/chromium/issues/detail?id=646265#c17 On Tue, Mar 7, 2017 at 1:05 PM, Boris Chiou <bch...@mozilla.com> wrote: > As of Firefox 55, I intend to land the patches of Frames timing functions > in Bug 1248340 <https://bugzilla.mozilla.org/show_bug.cgi?id=1248340>. > Currently, we decide not to add a pref for that, so we will ship it > directly. In this bug, we also contribute the tests into > web-platform-test*, > *web-platform-tests/css-timing-1/*. *Other UAs haven't ship this > *.* > This feature was previously discussed in this "intent to implement" thread: > https://groups.google.com/forum/#!topic/mozilla.dev.platform/w-3HBnN3sc4 > > *Bug to turn on by default*: > https://bugzilla.mozilla.org/show_bug.cgi?id=1248340 > > *Link to standard*: > https://drafts.csswg.org/css-timing/#frames-timing-functions > > -- > Regards, > Boris > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
