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

Issue 662940 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 660626
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Console showing javascript properties instead of HTML

Reported by kevel...@gmail.com, Nov 7 2016

Issue description

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

Steps to reproduce the problem:
1. Enter into console: $('body')
2. Expand the output and notice it displays javascript properties of the element

What is the expected behavior?
Instead of javascript properties I expect it to show the HTML

What went wrong?
Console output is wrong.  See attached image.

Did this work before? Yes 

Chrome version: 54.0.2840.87  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
 
chrome inspector issue.png
9.5 KB View Download
Labels: Needs-Bisect
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows-10 using chrome reported version #54.0.2840.87 and latest canary #56.0.2912.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Entered into console: $('body')
2. Expanded the output and observed that it displayed html elements as expected.

Reporter@ - Could you please check this issue on latest canary #56.0.2912.0 by creating a new profile without any apps and extensions and please let us know if the issue persist or not.

Thanks...!!
662940.mp4
887 KB View Download

Comment 3 Deleted

Comment 4 by woxxom@gmail.com, Nov 8 2016

Er, the OP's screenshot shows output of jQuery $ function, not Chrome console API $, so the bug report seems invalid.

Tangentially related:  issue 660626 
Labels: -Needs-Feedback -Needs-Bisect
Mergedinto: 660626
Status: Duplicate (was: Unconfirmed)
This issue seems similar to Issue id :660626. Hence, merging into the bug id :660626 and marking it as duplicate.

Please feel free to undupe if not the case.

Thanks...!!

Sign in to add a comment