Open
Bug 1201743
Opened 9 years ago
Updated 2 years ago
don't allow editing of agent/user sheets in the Style Inspector for chrome pages
Categories
(DevTools :: Style Editor, defect, P3)
DevTools
Style Editor
Tracking
(firefox43 affected)
NEW
Tracking | Status | |
---|---|---|
firefox43 | --- | affected |
People
(Reporter: heycam, Unassigned)
Details
If I visit say about:about, then open the Style Inspector, I see all of the agent and user sheets that apply to the page, which includes ua.css, html.css, sheets added by add-ons, etc., and these are all modifiable. I'm not sure it should be so easy to change these, as you could easily cause the browser to be unusable. Can we either not show these sheets or make them read only somehow?
Comment 1•9 years ago
|
||
(In reply to Cameron McCormack (:heycam) from comment #0) > If I visit say about:about, then open the Style Inspector, I see all of the > agent and user sheets that apply to the page, which includes ua.css, > html.css, sheets added by add-ons, etc., and these are all modifiable. I'm > not sure it should be so easy to change these, as you could easily cause the > browser to be unusable. > > Can we either not show these sheets or make them read only somehow? Do we have a report from sumo, feedback or social media that this is an issue that developers encounter? If we did this, I would at least want a way to disable it as I suspect it's much nicer using the built-in tools to style / debug an in-content page than the browser toolbox. tbqh I'm leaning towards wontfix unless there is some sense of real impact. The simplest workaround once one has rendered the browser unusable is to close / re-open the window to reload everything.
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Jeff Griffiths (:canuckistani) from comment #1) > Do we have a report from sumo, feedback or social media that this is an > issue that developers encounter? If we did this, I would at least want a way > to disable it as I suspect it's much nicer using the built-in tools to style > / debug an in-content page than the browser toolbox. I don't have any evidence that people are bumping in to this problem currently. > tbqh I'm leaning towards wontfix unless there is some sense of real impact. > > The simplest workaround once one has rendered the browser unusable is to > close / re-open the window to reload everything. You'd need to close / re-open the whole browser as the style sheets you are editing are global to the whole browser.
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•