Inspector caching of CSS values is too aggressive
Categories
(DevTools :: Inspector, defect, P3)
Tracking
(Not tracked)
People
(Reporter: v+mozbug, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Used inspector to examine CSS values for a particular element.
Ran Javascript that changed some of the CSS values. These were immediately reflected in the browser tab viewing the HTML for the whole series of similar elements that were affected.
Used inspector to examine the values of the whole series of similar elements.
Actual results:
The element I had viewed previously, which was still selected in Inspector, did not show the updated value.
I selected a different element of the series, which I hadn't viewed before, and it showed the updated value.
I selected the original element again, and it still showed the old value.
Expected results:
The altered CSS value should be immediately updated. I've noticed that it isn't, for a long time. But in the past, it seemed like selecting a different element, and then going back to the original element, caused the original element's CSS values to be updated. That no longer happens, but should.
|
Reporter | |
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•5 years ago
|
||
Thanks Glenn. This is an important but complex problem that we couldn't solve at the time of the as-authored style support in the inspector 4 years ago. At the time we decided to postpone the fix for this in bug 1196250, and unfortunately have not addressed it yet. Sorry about that.
|
|
Reporter | |
Comment 3•5 years ago
|
||
The regression in behavior that I was reporting is too new to be a duplicate of the bug cited.
That's not to say that it might not be curable by the extensive rewrite that appears to be necessary to fix the cited bug, but it is to say that things that appeared to somewhat work in 70 branch are not longer behaving the same way, so something changed recently to make things worse.
|
|
||
Comment 4•5 years ago
|
||
Ha ok, so that might be a different problem then. To investigate this though, can you please explain in details what you mean exactly by:
Ran Javascript that changed some of the CSS values. These were immediately reflected in the browser tab viewing the HTML for the whole series of similar elements that were affected.
Could you perhaps give the JS code you use to change CSS? Or even better, provide a test page where the problem can be exhibited?
Description
•