New issue
Advanced search Search tips

Issue 785175 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

no connection between DOM and debugger / Dom view

Reported by eld...@satec-global.com, Nov 15 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. add a debugger
2. no dom changes appear while the debugger is active
3. cannot see the changes in the elements panel also

What is the expected behavior?
The changes must appear in real time, it seems like it jams

What went wrong?
There is no relation between the dev tools and the DOM which appear on the screen, changes do not affect the screen and cannot explore using the elements view (html)

Did this work before? Yes prior to 61

Chrome version: 61.0.3163.100  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

This is a problem in the last few versions... used to work well. please fix this

Comment 1 by l...@chromium.org, Nov 15 2017

Status: WontFix (was: Unconfirmed)
Thanks for the report.  Unfortunately, this sounds like intended behavior when the browser is about to paint a new frame.

When DevTools is paused on a 'debugger' statement, all execution is stopped.  In some cases, the page you are inspecting will be grayed out, but you can still make and see changes to the DOM.

In some other cases, the page might be paused just before Chrome is about to paint a new frame.  At this time, the inspected page is not grayed out and any changes you make to the DOM are applied, but will not be visible until you resume the debugger and leave the paused state.


If I'm not fully understanding the issue, please feel free to elaborate or send a screencast, and we will take another look.

Comment 2 Deleted

Comment 3 by merra...@runmyprocess.com, Nov 16 2017 

When debugging hovering over a DOM object in the devtools' tabs to highlight the related DOM node in the page is a crucial feature.

I think we should be able to do that even if the browser is about to paint a new frame.
►

Sign in to add a comment