1928311 - No obvious way to remove new search engine selector button from user interface (ScotchBonnet)

Status: RESOLVED DUPLICATE of bug 1928132

(Firefox :: Address Bar, defect)

Description

[saj]

Attachment: after.png

Firefox's old subtle magnifying glass icon, which was only visible on new blank tabs, has been replaced by an obtrusive widget. The new widget is visible at all times on all tabs. I find this to be an unnecessary distraction.

17:29.49 INFO: Narrowed integration regression window from [c57a7e20, 56a71d42] (3 builds) to [c57a7e20, 96fe9c78] (2 builds) (~1 steps left)
17:29.49 INFO: No more integration revisions, bisection finished.
17:29.49 INFO: Last good revision: c57a7e20d1bc3e96fa0a78b7c818ee14e70fe01b
17:29.49 INFO: First bad revision: 96fe9c781b68d282f7d4debe45042ad06c178f62
17:29.49 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c57a7e20d1bc3e96fa0a78b7c818ee14e70fe01b&tochange=96fe9c781b68d282f7d4debe45042ad06c178f62

I first tried to remove the new widget by clicking 'Customise Toolbar...' but found it was not possible to remove the widget from there.

I then tried to navigate into the Firefox application preferences (⌘-,) but could not find an obvious toggle switch in there.

Finally, I ran the mozregression pictured above, read the source code, and found the flag.

browser.urlbar.scotchBonnet.enableOverride

Please make it easier for users to remove this widget from the Firefox user interface.

Comment 1

[saj]

Attachment: before.png

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Setting Regressed by field after analyzing regression range found by mozregression in comment #0.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

:daleharvey, since you are the author of the regressor, bug 1916679, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 4

[Mark Banner (:standard8)]

Thank you for the feedback. We are currently testing the feature in nightly. We will be changing when the button is visible in bug 1928132 which should hopefully improve the situation.