Bug 35348 – Web Inspector: Adding a style attribute via the Style panel doesn't update the DOM view

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: Web Inspector (Deprecated)

[Anthony Ricaud]

Steps to reproduce:

1) Open any webpage
2) Add a style attribute in the Styles column (like color: red;)

Actual results:
The body node doesn't show the style attribute

Expected:
The body node shows the style attribute

Note that the added style is applied to the webpage. Only the DOM view is not updated.

[Adam]

What you are adding is css styles, not attributes.  They wouldn't show up as an attribute in the DOM like <font color=red>.  There isn't anything that should need to be updated at all on the dom view.

You are editing the properties and values of the selector.  If you want to add an attribute in the dom, you can right click a node and add an attribute, it will be added and reflected upon the page.

[Adam]

Sigh... disregard my entire comment, I'm confused.

It is a valid problem when editing in the "element's 'style' attribute".

[Joseph Pecoraro]

(In reply to comment #1)
> What you are adding is css styles, not attributes.

Actually this bug refers to editing the "Style Attribute" section in
the Styles Sidebar. Those are connected to the DOM Element's
style="..." attribute. This is a special section that always exists
in the Styles Sidebar.

For an example:

  <div>
    <p>Text</p>
  </div>

  1. Select the <div>
  2. In the "element.style" section, add "color:red"
  -> at this point the div's style attribute is set. But the DOM wasn't updated!

If you close and reopen the inspector you will see the correct
styles in DOM:

  <div style="color:red">
    <p>Text</p>
  </div>

[Joseph Pecoraro]

(In reply to comment #2)
> Sigh... disregard my entire comment, I'm confused.
> It is a valid problem when editing in the "element's 'style' attribute".

No problem =). Too bad Bugzilla doesn't allow deleting comments.

[Alexander Pavlov (apavlov)]

The symptoms sound like bug 51478, which has been fixed in ToT.

*** This bug has been marked as a duplicate of bug 51478 ***