[GraemeLion]

See, I don't think it was poorly communicated by the Mozilla team. I've been reading their volunteer emails and their public facing blogs, and seeing their commentary on e10s all along.

What HAS been a problem is that they keep pushing it back because they don't want to upset the applecart of the legacy apps, and thus, e10s has basically become stalled by fear. And they didn't really do much to push back on that until very recently.

I think the main problem is, people look at e10s refactoring for their extensions, and thought it would never need to happen. That Mozilla would always just offer a 'back door' for them. I think that the XUL heavy extensions thought the same thing. The problem is, those two areas are the areas where a lot of the instability and issues come from, and the only way to solve those issues is to excise the code completely.

Mozilla's problem isn't communication. It's that people never seem to believe them, and they kept pushing it back.

[alphapapa]

Again, this is not accurate.

1. Developers are lazy. This includes addon developers. Until there is a concrete time that their existing code will stop working, there's little incentive for them to bother rewriting their code.

2. For extensions which require non-existent WebExtensions APIs, there is nothing they can do but hope and pray that Mozilla will deign to make such APIs to enable them to rewrite their whole codebase to use them. If Mozilla declines, then the addon author can do nothing except watch their extension die.

It is not a matter of addon authors not believing Mozilla. The ball is in Mozilla's court to follow through and enable the extension authors.

Now Mozilla has set themselves an arbitrary deadline to disable XUL, using the excuse that e10s and other XUL-breaking stuff will arrive on that deadline--which is another arbitrary deadline that they set. Is there a term for this kind of internal self-buck-passing?