Let's make sure to add a test that's expected to fail as well for this
so we can verify that we don't accidentally ship this enabled in chrome.
Not that we've had any recent instances of thinking we'd disabled a
feature only for it to get unknowingly shipped :)
-Ryan
On 3/27/2017 12:31 PM, Shu-yu Guo wrote:
I agree that disabling for chrome is the right thing here over prefs. I
want Nightly and DevEdition to have stage 3+ TC39 proposals unflagged and
ready to play with -- asking folks to turn on prefs to do that is not the
way to go here from my perspective.
Benjamin's concern is legit, though, so let's disable it in chrome.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
