enable toggling private browsing in about:addons
Categories
(WebExtensions :: General, enhancement, P1)
Tracking
(relnote-firefox 67+, firefox67 verified)
People
(Reporter: mixedpuppy, Assigned: mixedpuppy)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-complete)
Attachments
(6 files, 5 obsolete files)
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Updated•6 years ago
|
Assignee | ||
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Assignee | ||
Comment 7•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 8•6 years ago
|
||
Assignee | ||
Comment 9•6 years ago
|
||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 13•6 years ago
|
||
(In reply to Shane Caraveo (:mixedpuppy) from comment #9)
Created attachment 9033423 [details]
Screen Shot 2018-12-27 at 12.12.29 PM.pngBanner is being worked on in bug 1516548. This is a request for alpha on
the disabled tag. I used rgba(128,0,215,.5) for disabled state,
rgb(128,0,215) for enabled state.
Almost there!
We need to move the tag below the description. Be sure to keep the text all caps.
Regarding the color, it's rgba(98, 0, 164, 1) for the enabled state and rgba(98, 0, 164, 0.4) for the disabled one.
Updated•6 years ago
|
Assignee | ||
Comment 14•6 years ago
|
||
Assignee | ||
Comment 15•6 years ago
|
||
Assignee | ||
Comment 16•6 years ago
|
||
hrm, I think a change I did in reaction to review feedback resulted in the text getting larger on the details view. will fix.
Assignee | ||
Comment 17•6 years ago
|
||
There, that's better.
The primary descriptions here are 1.36em (on osx). I've made the second line 1.1rem
Comment 18•6 years ago
|
||
Comment on attachment 9035923 [details]
extensions list view
The label is perfect, thank you!
Extensions icons and the buttons need to maintain the same positions they have when the label is not present.
Comment 19•6 years ago
|
||
Comment on attachment 9035937 [details]
details view
Closer!
I have some notes.
-
The color of the description seems very light for such a small font-size. I will suggest using ##4a4a4f (grey-60)
-
The color of the link seems off. I suggest #0060df (aka blue-60) and to make the link underline. If other links are present on the page, we should make all the links looks like this.
-
Can I see a screen with a full card? I need to understand if there is enough space around the description.
Assignee | ||
Comment 20•6 years ago
|
||
I had to use a test extension to get a full card screenshot, let me know if this gives enough visual info for you.
Assignee | ||
Comment 21•6 years ago
|
||
(In reply to emanuela [ux] [OOO 12/21 - 01/07] from comment #19)
The color of the description seems very light for such a small font-size. I will suggest using ##4a4a4f (grey-60)
The color of the link seems off. I suggest #0060df (aka blue-60) and to make the link underline. If other links are present on the page, we should make all the links looks like this.
The sub-description is new, so changes there would not affect anything else. However, the link color, underline, etc. would either globally affect about:addons, or make this link different than other locations we have "learn more". I think the style is also shared with other links (e.g. author, homepage) as they appear the same, but I haven't verified. Hovering over these links darkens and underlines them.
If we want to make global changes, I'd prefer to have that as a separate bug so I don't have to examine every possibility
Assignee | ||
Comment 22•6 years ago
•
|
||
- The color of the link seems off. I suggest #0060df (aka blue-60)
All links in about:addons are defined as var(--in-content-link-color) in css, which is 0a8dff. On hover it changes to #0060df.
Comment 23•6 years ago
|
||
the link color, underline, etc. would either globally affect about:addons, or make this link different than other locations we have "learn more". I think the style is also shared with other links (e.g. author, homepage) as they appear the same, but I haven't verified. Hovering over these links darkens and underlines them.
If we want to make global changes, I'd prefer to have that as a separate bug so I don't have to examine every possibility
Agree. Let's track it in a separate bug, which should not block this one.
Assignee | ||
Comment 24•6 years ago
|
||
Assignee | ||
Comment 25•6 years ago
|
||
Comment 26•6 years ago
|
||
Comment on attachment 9035984 [details]
extensions list view
Looks good to me.
Comment 27•6 years ago
|
||
Comment on attachment 9035985 [details]
full details card
Nice! The contrast is way better now. Thank you
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 28•6 years ago
|
||
Assignee | ||
Comment 29•6 years ago
|
||
Comment 30•6 years ago
|
||
Comment 31•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/26ac80bf3391
https://hg.mozilla.org/mozilla-central/rev/9553d0cc4eea
https://hg.mozilla.org/mozilla-central/rev/ba4db0fbeb24
Comment 32•6 years ago
|
||
This issue is verified as fixed on Firefox 67.0a1 (20190130001444) under Win 7 64-bit and Mac OS X 10.14.1.
The preference ‘extensions.allowPrivateBrowsingByDefault’ is set to true by default.
When the preference is set to true, the extensions are enabled by default in private windows.
When the preference is set to false, the extensions are not enabled by default in private windows.
Please see the attached screenshot.
Updated•6 years ago
|
Comment 34•6 years ago
|
||
I added a note to the incognito page:
Note: Firefox 67 also adds a new setting in about:config, extensions.allowPrivateBrowsingByDefault, which defaults to false. This means that the default for a newly installed extension would be "not_allowed" meaning that the extension would not be able to run in a private window or tab. See this support article: Extensions in Private Browsing for details from the user's perspective.
I will also add the incognito manifest key to the 67 release notes.
Assignee | ||
Comment 35•6 years ago
|
||
(In reply to Irene Smith from comment #34)
I added a note to the incognito page:
Note: Firefox 67 also adds a new setting in about:config, extensions.allowPrivateBrowsingByDefault, which defaults to false. This means that the default for a newly installed extension would be "not_allowed" meaning that the extension would not be able to run in a private window or tab. See this support article: Extensions in Private Browsing for details from the user's perspective.
I will also add the incognito manifest key to the 67 release notes.
I don't think we should be documenting preferences that are not visible to the use in about:preferences. This preference was there to be able to turn the feature on or off at an appropriate time, users should not touch it. It will be removed after a version or two.
Comment 36•6 years ago
|
||
Made the requested changes to the page and to the release notes.
Description
•