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

Issue 676574 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome swallows a warning when specific breakpoint not set

Reported by jpoch...@college.harvard.edu, Dec 22 2016

Issue description

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

Steps to reproduce the problem:
1. open https://jsfiddle.net/y7wjLo1h/1/
2. run the fiddle in chrome with the dev tools console open
3. you will get no warning
4. now open react-dom.js in the sources tab and put a breakpoint on line 7020
5. rerun the fiddle, and continue when you hit the breakpoint
6. Chrome will give a warning in the console: react-dom.js:7020 The specified value "" does not conform to the required format.  The format is "#rrggbb" where rr, gg, bb are two-digit hexadecimal numbers.

What is the expected behavior?
The warning should show regardless of whether the breakpoint is set.

What went wrong?
The warning does not show if the breakpoint is not set.

This particular warning is about setting an <input type="color" />'s value to "" which doesn't match the #rrggbb format.  I don't know if the warning showing vs not showing is tied to it being this particular color picker warning.

There are presumably other things making the warning show or not show, but setting a breakpoint vs not was the easiest to reproduce. In the code I was working on that surfaced this bug, the warning was showing and the breakpoint was not set, although presumably something else was different.

Did this work before? N/A 

Chrome version: 54.0.2840.98  Channel: n/a
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0
 
Labels: Needs-Milestone
Adding 'Needs-Milestone' label, TE will check the issue and update the bug with comments & tag with respective Mstone
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Status: WontFix (was: Assigned)
Thank you for report.

I'm not able to reproduce it in ToT. It looks like react-dom.js was changed from the time when issue was filled. A lot things were changed in recent release: starting with console implementation to the how V8 engine run code, I hope this issue was fixed.
Please create another issue or reopen this one if it's still a problem.

Sign in to add a comment