Opening dev tools causes web application to lose all styles
Reported by
corey.p....@gmail.com,
Sep 26 2016
|
||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Example URL: it's behind our firewall. :( Steps to reproduce the problem: 1. open application 2. right click any element and "inspect" 3. What is the expected behavior? The application shouldn't lose it's style What went wrong? The application loses all styles as if the stylesheets are no longer loaded. Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? Yes 52.0.2743.116 (64bit) Does this work in other browsers? Yes Chrome version: 53.0.2785.116 Channel: stable OS Version: OS X 10.10.5 Flash Version: Shockwave Flash 23.0 r0 The application in question is an Ember/Rails application. Opening the inspector and spawning a new window instance from the application both cause the styles of the original page/tab to be removed.
,
Sep 28 2016
Video attached as requested.
,
Sep 29 2016
,
Sep 30 2016
I'm unable to debug this instance from just the video. Is there any way you can provide a reproducible test case? Are there any other websites which show this behavior for you when you inspect elements? Can you isolate the activity with a static version of the web page you're looking at?
,
Oct 7 2016
Thank you for providing more feedback. Adding requester "shrike@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 10 2016
Adding the FB label as per # 4 corey.p.murphy@, can you please provide the information requested in # 4.
,
Oct 11 2016
The behavior is only exhibited in this application which is proprietary and behind our corporate firewall so I'm unable to share the source in a public way. The web application and it's built on Ember so I'm unable to test using a "static" view of the app given how the "bug" presents itself during the lifecycle or refresh of the application instance in the browser. I understand all this makes it difficult to debug and identify the issue from your end.
,
Oct 19 2016
Thank you for providing more feedback. Adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 19 2016
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
,
Sep 21 2017
Is this still occurring with what is now 8 stable releases later? If so, does it occur in a clean profile with no extensions or settings reconfigured?
,
Sep 21 2017
,
Oct 3 2017
Can you try this in a new profile or in Canary? I am starting to think it might have to do with workspaces and a fresh profile should ensure you do not have workspaces setup.
,
Oct 16 2017
Closing as not reproducible. |
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by shrike@chromium.org
, Sep 27 2016