Right. But in my mind, "not tested in automation" ~= "always broken".
And if I understand the whole addon picture correctly (unlikely), then
WebExtension Experiments is basically our only answer to the mountain of
legacy extensions that we're breaking. (Not that it fixes them, just
that it's the answer to "yeah, you can't do stuff like that anymore in
Firefox".)
I don't want to hold up an always broken solution as our defense against
the claim that we've completely nerfed our extension capabilities. If
it's the most realistic path forward for any addon that extends in
currently unsupported places, then it would behoove us to make it truly
realistic. (If, instead, we decided to tell people wanting additional
extension points that they need to land them directly in gecko, then
fine, but my understanding is that Experiments is there to provide a
gentler path.)
It's ok if they break, even, as long as we *know* what's broken and
aren't in a state where developers have no trust in Experiments actually
working. "Try it and see, but you'll probably have to fix it before you
can use it" is not where we want to be.
On 06/14/2017 10:25 AM, Andrew McKay wrote:
WebExtension Experiments are a way to write WebExtension APIs without
having to write an API in mozilla-central.
There are no WebExtension Experiments enabled on release.
They have been enabled on release in Firefox 55 for a restricted set
of users *only*. Basically, Test Pilot. When that team proposes
pushing out an experiment to release, the usual release process for
that team will take place.
There is no need to think about interface compatibility in the future
with external clients.
On 14 June 2017 at 10:07, Nathan Froyd <nfr...@mozilla.com> wrote:
On Wed, Jun 14, 2017 at 12:54 PM, Steve Fink <sf...@mozilla.com> wrote:
On 06/14/2017 09:23 AM, Andrew Swan wrote:
I would hope that if we have promising or widely used webextension
experiments, that the relevant peers would be aware of them when reviewing
changes that might affect them but of course changing IDL bindings is only
one of a number of ways that a change to central could break an existing
experiment. This is one of the drawbacks of having out-of-tree code, I
think its up to us (the webextensions maintainers) to either deal with
this
or get experiments worked into automation if this becomes a real problem
in
practice.
Whoa. Experiments aren't tested in automation?
Whoa. We're going to still have to think about interface compat with
external clients in a post-57 world? This is the first I've heard of
this.
Can they be, please? At least snapshotted versions.
+1 Almost anything automation-related would be better than "hope
peers think hard about this".
-Nathan
_______________________________________________
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
