Closed
Bug 1389055
Opened 7 years ago
Closed 7 years ago
Intermittent behavior when calling getComputedStyle on an display: none element.
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
INVALID
People
(Reporter: emilio, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
STR: Open the testcase.
Expected: rgb(0, 255, 0), rgb(255, 0, 0), consistently.
Actual: Expected result when shift-reloaded, rgb(255, 0, 0), rgb(255, 0, 0) otherwise.
Running a regression test. This blocks my work on bug 1381071. I suspect the regressor is bug 1203766, but not sure yet.
Reporter | ||
Comment 1•7 years ago
|
||
This is not stylo-only, btw.
Reporter | ||
Comment 2•7 years ago
|
||
Err, I meant bug 1366964 above, of course.
Reporter | ||
Comment 3•7 years ago
|
||
But it can't be, of course, since I can repro it in 54.0.1...
Reporter | ||
Comment 4•7 years ago
|
||
I suspect I know why this happens for stylo, but digging now.
Reporter | ||
Comment 5•7 years ago
|
||
So I think this is happening because we don't increment the restyle generation when we find a style change that doesn't touch any frame... And thus we assume we can keep the style context around. I'm going to fix this for stylo in bug 1381071, first conservatively, then reworking a few things (I don't think after that bug we need all the generation mess anyway).
Reporter | ||
Comment 6•7 years ago
|
||
So, I retract my words, I don't think that's the root cause...
Reporter | ||
Comment 7•7 years ago
|
||
Oh, actually it's not due display: none at all, and it's because the script-set value is preserved across reloads... So this is invalid I fear, sorry all for the noise :(
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•