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

Issue 660626 link

Starred by 8 users

Issue metadata

Status: Closed
Owner:
Closed: Dec 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

XPATH/CSS query result array elements are expanded as JavaScript objects

Reported by bhanupa...@indeed.com, Oct 29 2016

Issue description

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

Steps to reproduce the problem:
1. Open Devtools > Console
2. Run $('body') or $x("//body")
3. Verify the result

What is the expected behavior?
Previously $('body') array elements were expanded as HTML elements (DOM tree
was shown).

What went wrong?
Now $('body') array elements are expanded as JavaScript objects (properties are
shown).

Did this work before? Yes 53

Chrome version: 54.0.2840.71  Channel: stable
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 23.0 r0

NA
 
Screen Shot 2016-10-29 at 7.59.22 AM.png
85.6 KB View Download

Comment 1 by woxxom@gmail.com, Oct 29 2016

Broken by  issue 607682  resolution.

Comment 2 by woxxom@gmail.com, Oct 29 2016

Showing *HTML* elements as JS objects doesn't make much sense by default. It may make sense sometimes, for someone, in some cases.

A dev-friendly resolution would be to display some sort of ... button on the right or provide a Shift-click for the toggler triangle to expand in alternative fashion (a tooltip over the triangle would be useful).
Owner: einbinder@chromium.org
We use jQuery to verify the CSS property of element for automation. This defect is causing inconvenience and forcing us to use Firefox console.
Cc: kkaluri@chromium.org pfeldman@chromium.org
Labels: M-56 hasbisect OS-Linux OS-Windows
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on windows 10, Ubuntu 14.04 and Mac 10.11.6 on chrome stable version 54.0.2840.71 
Issue is broken in M54. 

Bisect Info:
===========

Good build : 54.0.2791.0,  Revision Range(404283)
Bad build  : 54.0.2793.0,  Revision Range(404564)

After executing the bisect script, i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/fdcd9441c6a62f381878d6bd5ffe408077263218..57237df88100d360800e6131cce2434642071023

But the above CL seems to be unrelated.

Omahaproxy UI CL :
https://chromium.googlesource.com/chromium/src/+log/54.0.2791.0..54.0.2793.0?pretty=fuller&n=10000

Suspecting the following is the culprit from the above CL
---------
https://chromium.googlesource.com/chromium/src/+/aa55ad395804cf21d2b1594289219eb63f8277a6
pfeldman@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.
Cc: krajshree@chromium.org
 Issue 662940  has been merged into this issue.
Cc: rbasuvula@chromium.org
Still able to reproduce the issue on windows 10, Ubuntu 14.04 and Mac 10.11.6 using latest chrome version 57.0.2926.0.

einbinder@ Could you please look into this issue.

Thanks!
Still able to reproduce the issue on Mac 10.11.6 using latest chrome version 57.0.2935.0

einbinder@, Could you please take a look
Labels: Hotlist-Polish
Still able to reproduce the issue on Ubuntu 14.04 using latest chrome version 57.0.2977.0.

einbinder@ Could you please look into this issue.

Thanks!
Status: Closed (was: Assigned)

Sign in to add a comment