1207482 - "Html Validator" add-on does not work with e10s

Status: RESOLVED INCOMPLETE

(Firefox :: Extension Compatibility, defect)

Description

[mgueury]

HTML Validator compatiblity with e10s.

I am the extension author. I tried to check the compatibility with Firefox 44 and it is unhappily completely broken :-/

- view-source is now in tab (making my XUL code obsolete)
- CPOW seems to block the extension from working in several case

A political remark :-)
----------------------
This is annoying since due the the AMO time to approve and sign extensions with binary file like mine(2 months or so). It is nearly impossible for me to release fast fixes for my extension anymore. 

If Firefox introduces more incompatibilities with previous versions, 
- I can not release a new version before 2 months... 
- I can not provide a downloadable fix for my extension on my website anymore.

While I am not against this new technology. I come to a dead-end where 
- the fast release cycle of Firefox 
- incompatibility introduced regularly for extensions 
- and the time to get my extension signed 

are incompatible. Whatever I do :-/

Comment 2

[Matthew N. [:MattN]]

(In reply to mgueury from comment #0)
> I am the extension author. I tried to check the compatibility with Firefox
> 44 and it is unhappily completely broken :-/

Great to hear.

> - view-source is now in tab (making my XUL code obsolete)

Note that this isn't directly related to e10s as this was wanted for UX reasons.

> - CPOW seems to block the extension from working in several case

CPOWs should be avoided if possible by sending messages with the message manager. If you have specific code that you're having trouble converting then #e10s on IRC or the add-on forums could probably help.

> A political remark :-)
> ----------------------
> This is annoying since due the the AMO time to approve and sign extensions
> with binary file like mine(2 months or so). It is nearly impossible for me
> to release fast fixes for my extension anymore. 

I think we've improved this situation quite a bit since you filed this bug. New reviewers have been added and I believe the queue length is much shorter.

> If Firefox introduces more incompatibilities with previous versions, 
> - I can not release a new version before 2 months... 
> - I can not provide a downloadable fix for my extension on my website
> anymore.
> 
> While I am not against this new technology. I come to a dead-end where 
> - the fast release cycle of Firefox 
> - incompatibility introduced regularly for extensions

Unfortunately e10s was necessary and it's the biggest change to Firefox/Gecko ever. Once your extension is compatible with e10s I would expect that the incompatibilities would go back to the previous rate.

> - and the time to get my extension signed 
> 
> are incompatible. Whatever I do :-/

I think some of the code signing policies may have been refined/loosened since you filed this but I'm not sure. If you have suggestions to help smooth the process then it's worth sharing.

Thanks,
Matthew

Comment 3

[Firefox Bug Husbandry Bot]

With Firefox 57 only WebExtensions are permitted and are, by default, e10s compatible.