New issue
Advanced search Search tips

Issue 849858 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Code evaluation when hovering over highlighted code shows wrong value

Reported by liran...@gmail.com, Jun 5 2018

Issue description

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

Steps to reproduce the problem:
See attached screenshot

What is the expected behavior?
Correct evaluation value: 26

What went wrong?
Got 27 in the hover evaluation, even though the console evaluation correctly showed 26.

Did this work before? N/A 

Chrome version: 66.0.3359.181  Channel: n/a
OS Version: OS X 10.13.4
Flash Version:
 
Screen Shot 2018-06-05 at 22.37.16.png
77.8 KB View Download
Labels: Needs-Triage-M66
Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

Tried checking the issue on reported chrome version 66.0.3359.181 using Mac 10.13.1 with the below mentioned steps.
1. Inspected the page -> Console
2. Entered "stats.generation - settings.skip" and hit enter.
It says "Uncaught ReferenceError: stats is not defined". 

@Reporter: Could you please share a sample test file/URL which helps us to triage the issue in a better way. And please let us know if anything missed from our end.

Comment 3 by liran...@gmail.com, Jun 7 2018

Hi Vamshi,

Thanks for your response.

After closer inspection, this seems to be an issue with the source map I was using rather than with Chrome.

This ticket can now be closed.

Kind regards,
Liran
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 7 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
As per comment#3 closing this issue and marking it as Won't fix.

Thanks!

Sign in to add a comment