You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.
Result:
Line numbers are wrong: when you scroll the code view, the line numbers do not scroll. Since they're initially out of sync too, the breakpoint marker appears to have disappeared.
Expected:
Line numbers scroll width editor, as they would when you're not paused -- or when you hit the same breakpoint a 2nd time.
(Bug seems to only happen if the first time a given JS file's source is shown after Refresh is when you hit a breakpoint in that file).
The text was updated successfully, but these errors were encountered:
There seems to be a general class of problems in webkit where pausing JS execution in one tab/frame/window causes odd effects on the JS execution in other tabs/frames/windows. (On my copy of Safari for example, pausing at a breakpoint and then switching to another tab showing Google search results yields a totally broken page, seemingly because the search-as-you-type feature's JS code isn't executing).
I don't know if this is fixed in newer browser builds -- my copy of Chrome seems to have far fewer problems like this, and from looking at the Dev Tools UI it's clear it's a newer overall build than the Chromium that we're using.
Steps:
Result:
Line numbers are wrong: when you scroll the code view, the line numbers do not scroll. Since they're initially out of sync too, the breakpoint marker appears to have disappeared.
Expected:
Line numbers scroll width editor, as they would when you're not paused -- or when you hit the same breakpoint a 2nd time.
(Bug seems to only happen if the first time a given JS file's source is shown after Refresh is when you hit a breakpoint in that file).
The text was updated successfully, but these errors were encountered: