[css-contain] Contain:style does not have an effect when value changed via inspector
Reported by
myser...@gmail.com,
Jun 23 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 Example URL: Steps to reproduce the problem: 1. Open any contain:style test case for counter-scoping (e.g. http://test.csswg.org/suites/css-contain-1_dev/nightly-unstable/html/counter-scoping-001.htm). 2. Try to uncheck contain:style via inspector after the page is loaded. 3. Observe that checking&unchecking does not have any effect on the page. What is the expected behavior? Expected behavior is the refresh of the counter values with ot without contain:style applied depending on it being checked or not. What went wrong? Browser did not take dynamic change of contain:style property when rendering the page. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 69.0.3464.0 Channel: n/a OS Version: 10.0 Flash Version: Is this situation by design rather than a bug? I suspect that having contain:style change dynamically might or might not have collaterally effects. So, I am curios if the issue I described here is on purpose. Thanks!
,
Jun 25 2018
,
Jun 26 2018
Thanks for filling the issue... As per comment #0 we have tested this issue on reported chrome version 69.0.3464.0 using Windows 10. and observed the same behavior on latest chrome stable 67.0.3396.99, latest chrome 69.0.3473.0 and 60.0.3112.113. Steps: -------- 1. Launched chrome 2. Navigated to given URL ""http://test.csswg.org/suites/css-contain-1_dev/nightly-unstable/html/counter-scoping-001.htm"" 3. Opened Dev tools and navigated to Source>Counter-scooping and set break point at 12th line @Reporter: As we have not seen any changes in the above mentioned versions, Could you please have a look on screenshot and let us know if we have missed anything in the process. Thanks!
,
Jun 26 2018
Thanks for your response! Just to make my issue clearer, please consider the two attached test cases (same test as in the above link). One of them has contain:style enabled (lets call this number 1), and the other one has contain:style commented out (and number 2). Other than that, they are identical. Now, run test 1 in one tab. And, run test 2 in another tab. Then, uncomment contain:style via the inspector panel after the page is loaded. Now, both test 1 and test 2 are expected to be exactly identical. However, you will see that the displayed values are different, i.e. pages don't produce the same result despite having the exact same code. Basically, dynamically adding/removing contain:style (after the page is loaded) does not take any affect, from what I observed.
,
Jun 26 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 28 2018
,
Jan 9
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by krajshree@chromium.org
, Jun 24 2018