New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 638264 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

LiveEdit: editing regexps

Reported by remysh...@gmail.com, Aug 16 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2830.0 Safari/537.36

Steps to reproduce the problem:
I've included a screencast of the problem as it's a little complicated to explain (the video is 2m45s long), and an attachment of code: https://www.youtube.com/watch?v=p-dZCV875UU

Ensure that a workspace is set up, then:

1. Set a break point in the .js on line 384.
2. Add a watch exp of `commits.map(template)`
3. Click the page anyway to trigger the break point
4. Edit the regexp from `/(%.+%)/` to `/(%.+?%)/` (note that I'm unsure if it's the *two* changes that trigger this issue or not).
5. After saving, now change `pluck(data, match)` to `pluck(data, match.slice(1, -1)`
6. Save again, but notice that the page does not render the text.
7. Reload the page, and the expected result is show.

What is the expected behavior?
I'm expecting all functions to be evaluated. 

What went wrong?
The anonymous function _appears_ to be completely optimised out of the the stack. Again, see screencast.

Did this work before? Yes It's working in stable chrome at the moment, and certainly 3 years ago: https://remysharp.com/2013/11/27/using-watches-in-my-devtools-workflow

Chrome version: 54.0.2830.0  Channel: canary
OS Version: OS X 10.10.3
Flash Version: Shockwave Flash 23.0 r0
 
bug.zip
4.7 KB Download
Labels: TE-NeedsTriageHelp
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Looks like a live edit failure. ALexey, could you please take a look?
Cc: kozyatinskiy@chromium.org
Owner: yangguo@chromium.org
Summary: LiveEdit: editing regexps (was: In memory changes do not always work)

Sign in to add a comment