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

Issue 621839 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 646304
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Console prototype inaccessible in Chrome Canary

Reported by richardk...@gmail.com, Jun 21 2016

Issue description

Chrome Version       : 53.0.2770.0 (Official Build) canary (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK 9.1.1
    Firefox: OK 47.0

Some websites shim console.log/warn/debug/error with empty functions but the user has been able to undo this if needed by running "delete console.log" or using Object.getPrototypeOf() or console.__proto__ to get the original function. In Canary the prototype of console appears to be empty and all of the functions are properties of the console object instead.

What steps will reproduce the problem?
(1) Open the dev console 
(2) run "Object.getPrototypeOf(console).log"

What is the expected result?

Output should be should be something like "function log(){[native code]}"


What happens instead?

Output is undefined

Please provide any additional information below. Attach a screenshot if
possible.

Running Object.getOwnPropertyNames(console) in Canary returns ["debug", "error", "info", "log", "warn", "dir", "dirxml", "table", "trace", "group", "groupCollapsed", "groupEnd", "clear", "count", "assert", "markTimeline", "profile", "profileEnd", "timeline", "timelineEnd", "time", "timeEnd", "timeStamp", "memory"] which means that if any of these are replaced they can't be "brought back".
 
Components: Platform>DevTools
Labels: -Type-Bug -Pri-3 M-52 hasbisect OS-Linux OS-Mac OS-Windows Pri-2 Type-Bug-Regression
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on windows 7, Linux Ubutu 14.04 and Mac 10.11.5 using chrome version 53.0.2774.3 and beta 52.0.2743.41 but this is working fine on stable 51.0.2704.103.
This is regression issue broken in M52.Please find the bisect information as below

Narrow Bisect
================
Good : 52.0.2721.0  --  (official build revision 390803)
Bad : 52.0.2722.0 --   ((official build revision 390853)

CHANGELOG URL:
==============  https://chromium.googlesource.com/chromium/src/+log/13905ccd656349df4ec5e9bf196d4bc913a0a97b..dcdc0218d3404fb53a1b27f40b3ebed5dd5e277d

Possible suspect
=================
https://chromium.googlesource.com/chromium/src/+/dcdc0218d3404fb53a1b27f40b3ebed5dd5e277d

kozyatinskiy@ could you please look into this issue if it is related to your change,else please help us in finding the appropriate owner for this issue.

Thanks,
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 22 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 3 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 646304
Status: Duplicate (was: Assigned)

Sign in to add a comment