Closed
Bug 1349898
Opened 7 years ago
Closed 1 year ago
support browser_style in devtools, but using devtools styles
Categories
(WebExtensions :: Developer Tools, enhancement, P3)
WebExtensions
Developer Tools
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ntim, Unassigned)
References
Details
(Whiteboard: [design-decision-approved][triaged])
Similarly to "browser_style": true/false for browser/page action, we should provide "devtools_style" true/false for devtools panels.
Comment 1•7 years ago
|
||
I've got a couple of questions about this… 1) Why is the devtools style different from the browser style? At best that makes it seem like we're building an unrelated collection of random stuff, not a single product. 2) If they have to be different, why would "browser_style" not be the devtools style for devtools panels? The intent of "browser_style" is fairly clearly "Make this look like part of the browser", so we should do that.
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to Blake Winton (:bwinton) (:☕️) from comment #1) > I've got a couple of questions about this… > > 1) Why is the devtools style different from the browser style? At best that > makes it seem like we're building an unrelated collection of random stuff, > not a single product. The advantage is that devtools_style will also integrate with whatever theme is selected. > 2) If they have to be different, why would "browser_style" not be the > devtools style for devtools panels? The intent of "browser_style" is fairly > clearly "Make this look like part of the browser", so we should do that. browser_style as name is fine too.
Comment 3•7 years ago
|
||
I don't think there's any need for discussion here. We've got a standard pattern for providing a style that matches the rest of the UI if the developer wants it. Let's do the same here.
Whiteboard: [design-decision-needed] → [design-decision-approved]
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [design-decision-approved] → [design-decision-approved][triaged]
Comment 4•6 years ago
|
||
TBH given the amount of problems and limitations with browser_style I'm hesitant about this. However, lets at least use "browser_style" for the name.
Summary: Add devtools_style: true/false as option when creating a devtools panel → support browser_style in devtools, but using devtools styles
Updated•6 years ago
|
Product: Toolkit → WebExtensions
Updated•2 years ago
|
Severity: normal → S3
Comment 5•1 year ago
|
||
Closing bug because support for browser_style
feature is going to be removed (at least in MV3), see bug 1827910.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•