Closed
Bug 669596
Opened 15 years ago
Closed 14 years ago
Style inspector should allow editing of css property values within the UI
Categories
(DevTools :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: miker, Assigned: dcamp)
Details
(Whiteboard: [styleinspector][minotaur])
From the style inspector it is currently not possible to edit property values. I should be fairly simple to make the values editable by manipulating node.style.
Tracking changes may also be possible but that would be a separate bug.
| Reporter | ||
Updated•14 years ago
|
Whiteboard: [hydra]
| Reporter | ||
Updated•14 years ago
|
Whiteboard: [hydra] → [styleinspector]
| Assignee | ||
Updated•14 years ago
|
Priority: -- → P2
Whiteboard: [styleinspector] → [styleinspector][minotaur]
| Reporter | ||
Updated•14 years ago
|
Assignee: nobody → mratcliffe
Comment 1•14 years ago
|
||
Edit should be a single click, I think.
| Reporter | ||
Updated•14 years ago
|
Summary: Style inspector should allow editing of css property values → Style inspector should allow editing of css property values within the UI
| Assignee | ||
Updated•14 years ago
|
Priority: P2 → P3
| Assignee | ||
Comment 2•14 years ago
|
||
I've put a decent amount of thought into style editing while working on the rule view, I'll look into this for the property view too.
Assignee: mratcliffe → dcamp
| Assignee | ||
Comment 3•14 years ago
|
||
We're doing developer tool prioritization, filter on 'brontozaur'
to ignore the spam.
Dropping priority in favor of ruleview editing.
Priority: P3 → --
| Reporter | ||
Comment 4•14 years ago
|
||
Do we know if or how the editing will be done?
Comment 5•14 years ago
|
||
(In reply to Michael Ratcliffe from comment #4)
> Do we know if or how the editing will be done?
The style editor, and/or the rule view?
Comment 6•14 years ago
|
||
This bug existed before the Rule View was even a thing. In fact, it kind of led to the Rule View becoming a thing. Given that we now have editing capability in the rule view, I think this bug has become less of a priority.
Do we still want to even do this?
Comment 7•14 years ago
|
||
If we do, I think a similar approach to the Rule View's popup text editor is probably the way to go.
Comment 8•14 years ago
|
||
(In reply to Rob Campbell [:rc] (robcee) from comment #6)
> This bug existed before the Rule View was even a thing. In fact, it kind of
> led to the Rule View becoming a thing. Given that we now have editing
> capability in the rule view, I think this bug has become less of a priority.
>
> Do we still want to even do this?
In my opinion, no.
Comment 9•14 years ago
|
||
Note that WebKit doesn't allow editing styles in the Computed Style section either.
| Reporter | ||
Comment 10•14 years ago
|
||
The only way I can see rules being editable is if the user clicks a selector css link. In my opinion this should open the style editor (bug 585563).
The problem with this approach is that it is only possible to edit a properties css if it has user styles but I still think it is the best approach.
If we all agree on this then we can resolve this as wontfix in favor of bug 585563.
Comment 11•14 years ago
|
||
Yes - wontfix
I'd like to see the style editor be able to edit styles on elements one day. Until then we have the rule view.
Comment 12•14 years ago
|
||
alright! We are agreed. :)
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•