Install date vs. enabled date for extension settings overrides

Krupa Raj kraj at mozilla.com
Thu Oct 5 17:02:48 UTC 2017


We should definitely fix that. The user should always be in control of
setting their homepage to whatever they'd like it to be.

thanks,
Krupa

On Thu, Oct 5, 2017 at 9:53 AM, Bob Silverberg <bsilverberg at mozilla.com>
wrote:

> Mark and I were having a discussion about the ExtensionSettingsStore with
> regards to the search engine setting and Jazz, and came to the realization
> that we may have an issue with the way precedence is designed around
> re-enabling extensions.
>
> Here's a scenario:
>
> Extension A is installed, which changes the home page to
> https://www.aaa.com.
> Extension B is installed, which changes the home page to
> https://www.bbb.com. This gets control as the most recently installed
> extension.
> Both extensions are disabled (the order doesn't matter), which restores
> the home page to its default value.
>
> The user changes their mind and re-enables Extension B, setting the home
> page to https://www.bbb.com once again.
> The user decides they actually liked the other home page better, so they
> re-enable Extension A, expecting the home page to change to
> https://www.aaa.com, but it does not. It remains as https://www.bbb.com.
>
> This is because currently the precedence is based on extension install
> date, and ignores enabled date.
>
> The only way for a user to have Extension A in control again is to disable
> Extension B.
>
> Does this sound like something we should fix, or does this sound like the
> desired behaviour?
>
> Thanks,
> Bob
>
>
> _______________________________________________
> Dev-addons mailing list
> Dev-addons at mozilla.org
> https://mail.mozilla.org/listinfo/dev-addons
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/dev-addons/attachments/20171005/fef051cf/attachment.html>


More information about the Dev-addons mailing list