Temporarily enable "Report site compatibility issue" inside Help section of App menu
Categories
(Firefox :: Toolbars and Customization, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox88 | --- | verified |
People
(Reporter: RT, Assigned: mconley)
References
(Blocks 1 open bug)
Details
(Whiteboard: [proton-hamburger-menu] [proton-address-bar])
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Goal:
With the meatball menu removal as part of Proton, we want to make sure early that our mitigation plan for "Report site compatibility issue" works for the webcompat team in terms of the volume and quality of reports they get as a result of the change.
Once this lands the webcompat team will validate that they approve this change after a few weeks of collecting data.
Acceptance criteria:
- Enable "Report site issue" by default in the Help section of the Application menu
- Make this a "pre release" only change so that only nightly, Beta and dev edition users see it. "Report site compatibility issue" is an option of the meatball menu that currently only appears for pre-release users.
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 1•4 years ago
|
||
(Maybe this is actually a Hamburger Menu bug…)
Comment 2•4 years ago
|
||
Is this only going into the app menu, or does this need another bug to add it to the menubar?
Comment 3•4 years ago
|
||
For this first attempt it's just going into the App Menu. If the team decides that that has negatively impacted their data, we can come up with alternative places then.
Comment 4•4 years ago
|
||
(In reply to Blake Winton (:bwinton) (:☕️) from comment #3)
For this first attempt it's just going into the App Menu. If the team decides that that has negatively impacted their data, we can come up with alternative places then.
I think it is unexpected that the app menu has functions not available in the menu bar - the menu bar has traditionally been a superset of options available in Firefox (and the app menus as a subset) - I think it will be very confusing for the type of experienced user who is likely to use this option, to not have it be available in the "superset" menu and instead "hidden" inside of the ostensibly more pared down app menu.
Comment 5•4 years ago
|
||
Be that as it may, this is the option we're testing first. If changes are needed later on, we will open new bugs for them, but they are explicitly out of scope at this time.
Updated•4 years ago
|
Comment 7•4 years ago
|
||
Going to put this on [proton-address-bar] as well for tracking. The pageAction should be removed from the webcompat extension when it moves to the Help menu, if that isn't part of this bug (it's just to add a menu entry?) then we'll need a new bug for the address bar.
Comment hidden (obsolete) |
Comment 9•4 years ago
|
||
Added "Report site issue..." to the Help submenu: https://docs.google.com/presentation/d/1Ufd0A3HsziyXXAjXYNH84P2bu7RdTxARsA0xpKmwIWs/edit#slide=id.gb61155b0a3_8_41
Assignee | ||
Comment 10•4 years ago
|
||
Thanks, Meridel!
The string for the menuitem should be "Report Site Issue…" for both the menubar and appmenu variants, and the item should be placed below the "Task Manager" menuitem and above the "Report Deceptive Site" menuitem.
Comment 11•4 years ago
|
||
Thanks Mike for the context.
Just a reminder for the context, that this is an attempt at understanding which impact it will have on the volume of webcompat bugs reporting. And given the results of this experiment, we might want to decide to put "Report Site Issue" elsewhere. I'm saying this because Comment #8 seems to involve quite a lot of work and I would like to avoid people being worn out by something which might be changed in the future. Or maybe I'm reading too much into the comment. :)
Assignee | ||
Comment 12•4 years ago
|
||
Okay, I got up to speed with karlcow and denschub on Matrix about what this is about. Basically, we want to test moving access to the Help menu to see if that's right place, but we want to do it in as cheap a way as possible because we're not 100% certain that the Help menu is the right place.
I've obsoleted comment #8. That'll only be the plan if we decide to do this permanently. I'll come up with a new plan.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 14•4 years ago
|
||
We're not 100% certain if Help is the right spot for this, but we're going
to give it a shot and see. If it turns out it is the right spot, we'll
probably do something a little more self-contained, and less hacky.
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 15•4 years ago
|
||
Hey DenSchub, now that soft freeze is over, do you think you might have time to take another look at this?
Comment 17•4 years ago
|
||
Comment 18•4 years ago
|
||
bugherder |
Comment 19•4 years ago
|
||
We verified this issue using Fx 88.0b5 on Windows 10 x64, macOS 10.13 and Ubuntu 18.04 LTS.
Description
•