Bug 249064

Summary: www/firefox: after upgrade to 80.0 the extensions "floccus" and "conex" are not working anymore
Product: Ports & Packages Reporter: Martin Birgmeier <d8zNeCFG>
Component: Individual Port(s)Assignee: freebsd-gecko (Nobody) <gecko>
Status: Closed Overcome By Events    
Severity: Affects Only Me Flags: bugzilla: maintainer-feedback? (gecko)
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   

Description Martin Birgmeier 2020-09-02 15:33:49 UTC 
Scenario:
- FreeBSD 12.1-RELEASE-p6 #6 r362488M
- Latest ports (but issue started with first update to 80.0)
- Firefox at firefox-80.0.1,1
- Extensions "conex" and "floccus bookmarks sync" installed
- "conex" configured with multiple containers and multiple pages in each container
- "floccus" configured with a webdav location as sync storage

Result:
- Both extensions stop working
- When clicking on the "conex" icon directly after upgrading firefox, the list of containers is briefly displayed and then immediately replaced by a white canvas; subsequent clicks show an empty list
- When clicking on the "floccus" icon, no sync storage is shown as configured

Expected result:
- Clicking on the "conex" icon should bring up the regular list of containers
- Clicking on the "floccus" icon should show the configured sync storage mechanism

Notes:
- From the behavior it seems that these extensions somehow lost the access to their private storage.
- From the FF 80.0 and 80.0.1 release notes it is not immediately obvious that the interface for extensions should have changed significantly.
- On a Windows machine where FF has been updated to 80.0.1 by the mozilla update mechanism, both extensions are still working flawlessly.

-- Martin
Comment 1 Martin Birgmeier 2020-09-04 08:42:59 UTC 
The following lines are ouput on the console by firefox while the "conex" button is misbehaving (showing a single line of white background only):


###!!! [Parent][MessageChannel] Error: (msgtype=0x210001,name=PBrowser::Msg_AsyncMessage) Channel error: cannot send/recv


###!!! [Parent][MessageChannel] Error: (msgtype=0x210001,name=PBrowser::Msg_AsyncMessage) Channel error: cannot send/recv


###!!! [Parent][MessageChannel] Error: (msgtype=0x210001,name=PBrowser::Msg_AsyncMessage) Channel error: cannot send/recv


###!!! [Parent][MessageChannel] Error: (msgtype=0x39013A,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv

JavaScript error: moz-extension://6cc31497-00c7-4c69-abf8-c3b47c1dcab4/conex-browser-action.js, line 2: TypeError: bg is null
JavaScript error: moz-extension://6cc31497-00c7-4c69-abf8-c3b47c1dcab4/conex-browser-action.js, line 2: TypeError: bg is null
JavaScript error: moz-extension://6cc31497-00c7-4c69-abf8-c3b47c1dcab4/conex-browser-action.js, line 2: TypeError: bg is null
JavaScript error: moz-extension://6cc31497-00c7-4c69-abf8-c3b47c1dcab4/conex-browser-action.js, line 2: TypeError: bg is null
JavaScript error: moz-extension://6cc31497-00c7-4c69-abf8-c3b47c1dcab4/conex-browser-action.js, line 2: TypeError: bg is null

Furthermore, firefox dumps core when exiting.
Comment 2 Martin Birgmeier 2020-09-19 11:35:06 UTC 
Interestingly, with today's upgrade to firefox-81.0,2, both floccus and conex are working again.

-- Martin