Open squelart opened 3 years ago
I'm not convinced with this solution. The most prominent button should be the most probable action a user will do.
However we can maybe add such a button in a less prominent place. But that would need a Gecko patch too, because these actions are implemented in the WebChannel implementation.
It may be easier to show a message when the user enables the button explaining how to remove it? Or put this somewhere in the documentation simply?
A less prominent button would be an ideal solution. I agree that it can be confusing.
Here's where the Gecko code lives: https://searchfox.org/mozilla-central/search?q=ENABLE_MENU_BUTTON&path=&case=false®exp=false
It requires touching Gecko code, but I don't think it'd actually be a ton of work.
I wish to solve this issue. Please tell me what I would need. Just an overview. But don't assign me yet.
See issue #3184 for the reason (users may not know how to remove the profiler button).
Since https://profiler.firefox.com is the main page used to initially add the toolbar button, and it knows not to show the "Enable..." button anymore after it has been enabled, I would suggest that the same button area be reused to allow easy removal of the profiler toolbar button. This would make the page a bit more consistent before and after. And I think it would be one of the most obvious location where users would look at to remove the toolbar button when no longer needed.
Enable button:![profiler-enable](https://user-images.githubusercontent.com/8499548/112426956-f036e780-8d8c-11eb-9994-cf6e14662680.png)
Suggested "Remove" button:![profiler-remove](https://user-images.githubusercontent.com/8499548/112427032-0fce1000-8d8d-11eb-8359-14f184aa8445.png)
┆Issue is synchronized with this Jira Task