Waterfox Current upgrade from Waterfox Classic: add-on peculiarities

[grahamperrin]

Upgrade-related #983 is quite specific. Lossy (relatively serious, if the user has no backup and intends to attempt a downgrade).

---

Other issues are relatively minor but potentially confusing, unnerving.

about:addons for example, can temporarily get into this state:

ⓘ The address wasn't understood

Waterfox doesn't know how to open this address, because one of the following protocols (addons) isn't associated with any program or is not allowed in this context.

• You might need to install other software to open this address.

[Try again]

As a priority, I'll try to make the case above reproducible. IIRC most surprising was that it did not directly involve a legacy extension.

---

Less of a priority, the UX when non-modified legacy extensions are enabled but non-functional. Extensions such as Session Manager fall under this umbrella. Normally I'd keep issues separate, where there might be significant differences in symptoms and causes, but for now (to keep the numbers down) …

… I'll mix things up. Might regret it later :-)

---

Meta, tracking: #538

[grahamperrin]

ⓘ The address wasn't understood

… IIRC most surprising was that it did not directly involve a legacy extension.

True. Early indications were that this failure involves non-legacy version 19.1.31.1822 of Refined GitHub. See both:

• https://redd.it/aw8rqm and
• https://redd.it/ctttof

Screen recording of Waterfox Current 2019.10:

• 2019-11-29 15:49.mp4 https://put.re/player/bhpyLVc9.mp4
• 2019-11-29 15:49.zip

Side note

Maybe irrelevant … a Firefox 71 view of preferences for the extension simply added to a new profile (no import/migration, no upgrade):

Postscript

Unfortunately: whilst I can reproduce this issue with a real Waterfox Classic profile in a test environment, I can not reproduce it with a clean profile – not even after adding the more-dropdown preference as shown at refined-github/refined-github#2357 (comment)

[grahamperrin]

UX when non-modified legacy extensions are enabled but non-functional

Deep sigh.

extensions.legacy.enabled is true and locked.

Locks such as this defeat attempts to troubleshoot.

I might review this issue after the lock is removed. Until then, I'm drawing a line.

---