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

Issue 607511 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Invalidation for entered number in 'Sensors' section is not shown in dev tools.

Reported by rk...@etouch.net, Apr 28 2016

Issue description

Chrome version : 52.0.2719.0 db7757b63f29696b9b465949f9704a0d9d149f2b-refs/heads/master@{#390251} 32/64 bit
OS :  Windows (7, 8, 10), Mac 10.10.5, Linux

What steps will reproduce the problem?
1. Launch chrome and open dev tools window.
2. Press Esc key,navigate to Sensors section and click on 'Accelerometer' drop down list.
3. Select 'Custom Orientation', click in text box and enter invalid number, observe.

Invalidation doesnot shown for invalid numbers in sensors text box.

Invalidation should be show  for invalid numbers in sensors text box.

This is a regression issue, broken in 'M-52', below is bisect info:

Good Build : 52.0.2718.0
Bad Build : 52.0.2719.0

Narrow Bisect info:
https://chromium.googlesource.com/chromium/src/+log/7e7d3daff9117163ca29f1614a9e45ee1cb47b23..c80c8d6b64756dbd6b3a34cbf2f7f5e6473eed0c?pretty=fuller&n=100

Suspecting : r390131 

 
Actual_Devtools.mp4
1.2 MB Download
Expected_DevTools.mp4
814 KB Download
Labels: ReleaseBlock-Stable
Adding RB label as this is a recent regression.
Issue is still reproducible on Windows 7 using chrome latest canary M52-52.0.2723.0. Observed that invalidation does not show for the invalid numbers in sensors text box.

luoe@ - Any update on this bug? Could you please look in to this issue.

Thanks!

Comment 3 by l...@chromium.org, May 3 2016

Status: Started (was: Assigned)
@brajkumar, yes, there is a CL in review right now, which should re-introduce validation for those fields.

https://codereview.chromium.org/1923393006/

Hopefully it will land today or very soon.

Comment 5 by l...@chromium.org, May 4 2016

Status: Fixed (was: Started)
Changes committed.  Please review if needed.

Sign in to add a comment