[Bug 249064] www/firefox: after upgrade to 80.0 the extensions "floccus" and "conex" are not working anymore

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249064

            Bug ID: 249064
           Summary: www/firefox: after upgrade to 80.0 the extensions
                    "floccus" and "conex" are not working anymore
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gecko at FreeBSD.org
          Reporter: d8zNeCFG at aon.at
             Flags: maintainer-feedback?(gecko at FreeBSD.org)
          Assignee: gecko at FreeBSD.org

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

-- 
You are receiving this mail because:
You are the assignee for the bug.