Closed
Bug 1434624
Opened 7 years ago
Closed 7 years ago
Indicate in the title bar that the policy engine is in use
Categories
(Firefox :: Enterprise Policies, defect)
Firefox
Enterprise Policies
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: RT, Unassigned)
References
Details
User Story
As a Firefox user where policies have been applied, I want to be aware that I run a customized Firefox so I can make sense of potential limitations and react accordingly. Acceptance criteria: - An indicator in the title bar informs me that my Firefox was customized through the policy engine (only applicable on the ESR update channel) - Clicking the indicator provides me with more details about what is happening through a SUMO page Notes: re-use of the A11Y indicator sounds like an appropriate/simple way forward (https://bugzilla.mozilla.org/attachment.cgi?id=8932509) Next steps: - Get the icon as svg, with both a normal and a hover state - Get tooltip string to display there - Get a permalink defined to a sumo page (that can be written later) if we want to make it clickable
No description provided.
Comment 1•7 years ago
|
||
FWIW, a simple way to see the accessibility indicator:
- change accessibility.indicator.enabled pref to true
- Run this in the Browser Console (you need devtools.chrome.enabled to true):
Cc["@mozilla.org/accessibilityService;1"].getService(Ci.nsIAccessibilityService);
The indicator has a tooltip, hover state and clicking on it leads to a SUMO page
| Reporter | ||
Updated•7 years ago
|
User Story: (updated)
| Reporter | ||
Updated•7 years ago
|
User Story: (updated)
Comment 2•7 years ago
|
||
Did we decide that we were going to do this at some point?
Or did we decide we weren't going to do this at all?
| Reporter | ||
Comment 3•7 years ago
|
||
Shorlander and Amin decided it was not valuable and preferred focus on update of about dialogue (bug 1443771), blocked pages updated UX (bug 1438243) and preferences notice (bug 1432906).
I'm WON'T fixing it for this reason.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•