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

Issue 808406 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 4
Cc:
yangguo@chromium.org
█ susanjun...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug

Blocking:
issue v8:6513



Sign in to add a comment

Wrong SyntaxError reporting on 'illegal break statement'

Reported by i...@manekeno.com, Feb 2 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce the problem:
1. Demo file that shows aspects of this problem is attached
2. 
3. 

What is the expected behavior?
It is expected that Chromium is going to be generating Error messages on truthful 'illegal break statement', rather than on totally correct one instead.

What went wrong?
I'm getting 'Illegal break statement' Error message about correct break statement. Meanwhile, the incorrect one, which is also present, remains hidden.

Firefox Error message points at the incorrect break statement, as it should.

Did this work before? N/A 

Chrome version: 64.0.3282.119  Channel: n/a
OS Version: 10.0
Flash Version: 

Dmitry, info@manekeno.com
IllegalBreakBugPrototype.html
1.8 KB View Download

Comment 1 by manoranj...@chromium.org, Feb 3 2018

Labels: Needs-Triage-M64

Comment 2 by tkent@chromium.org, Feb 5 2018

Components: -Blink Blink>JavaScript

Comment 3 by susanjun...@techmahindra.com, Feb 5 2018

Cc: susanjun...@techmahindra.com
Labels: Triaged-ET M-66 FoundIn-66 Target-66 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Reporter@ Thanks for the issue.
Tested this issue on Windows 10, Mac OS 10.13.1 and Ubuntu 14.04 on the latest Stable 64.0.3282.140 and Canary 66.0.3340.0 and able to reproduce the issue by following the steps in the original comment.

Can observe the error 'Uncaught SyntaxError: Illegal break' in Devtools -> Console, on opening the given html page.
Attached is the screen shot for reference.

This is a Non-Regression issue as this behavior is observed form M60 Chrome builds. 
Hence marking this as Untriaged for further updates from Dev.

Thanks..
808406.PNG
69.5 KB View Download

Comment 4 by i...@manekeno.com, Feb 6 2018 

Thanks for verification. I just can add that for unknown reason, for a couple of days after I first reported, I stopped seeing this problem in my browser. I even thought my browser was updated with the bug has been fixed. But now I'm seeing it again, and I'm glad that you were able to reproduce it independently and put it on your list.

Comment 5 by hablich@chromium.org, Feb 13 2018

Cc: yangguo@chromium.org
Components: -Blink>JavaScript Blink>JavaScript>Language
Status: Available (was: Untriaged)

Comment 6 by adamk@chromium.org, Feb 13 2018

Blocking: v8:6513

Comment 7 by adamk@chromium.org, Aug 16

Components: -Blink>JavaScript>Language Platform>DevTools>JavaScript
I can't repro this in d8 (there, I get a pointer to the correct thing). So I think this might be a devtools issue.

Comment 8 by pfeldman@chromium.org, Dec 4

Status: WontFix (was: Available)
Can't repro.
►

Sign in to add a comment