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

Issue 779679 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit 28 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

view property values rather than whole object values on mouse over/ hover

Reported by somi...@gmail.com, Oct 30 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Steps to reproduce the problem:
1. Say, I have,  element{
   actualPrice: 12,
   actualHrs: 3,
   actualPrice: 40
   ... 
   }
2. In my source code I have let i = 'element.actualHrs'
3. If I mouse over element, it shows the whole object properties with values. - Nice
4. If I mouse over actualHrs, it shows the whole object properties with values. I am expecting to see only the value of the property I am mouse hovering.

What is the expected behavior?
I am expecting to see only the value of the property I am mouse hovering.

What went wrong?
Shows the entire object rather than single property.

Did this work before? Yes Not sure, probably couple of months back

Chrome version: 62.0.3202.75  Channel: stable
OS Version: 10.0
Flash Version:
 
Untitled.png
33.2 KB View Download
Labels: Needs-Triage-M62
Cc: krajshree@chromium.org
Labels: Needs-Feedback
somitha@ - Thanks for filing the issue...!!
Could you please provide a sample test file to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Comment 3 by somi...@gmail.com, Oct 31 2017

Hi,
 This is a simple html file I created to recreate the issue. But looks like dev tools is working as expected on mouse over. I noticed this issue in my project which is an angular2 application. So this issue is to do with typescript files. I will confirm. Thanks
app.html
468 bytes View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 31 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sc00335...@techmahindra.com
Labels: Needs-Feedback
As per comment#3 Issue is not reproducible from reporters end.

@Reporter: Could you please confirm whether we can close this issue.

Thanks!
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 7 by somi...@gmail.com, Nov 2 2017

Hi, comment #3 is just about replicating the issue with the file I uploaded. 
This issue still happens with the typescript source mapped file of my  angular2 application. But unfortunately I don't know any easy way to upload the angular2 project for you guys. This happens with all my colleagues who debug typescript files in dev tools.
Status: WontFix (was: Assigned)
The hovering behavior over typescript sources is heuristic: it uses sourcemaps to infer selection ranges, so it gets only as good as sourcemaps are.

In certain cases, sourcemaps are not granular enough, thus the observed behavior.


Closing as WontFix due to lack priority / resources. 

Sign in to add a comment