New issue
Advanced search Search tips

Issue 604188 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Inconsistent behaviour of variables named dir, table, etc in Chrome console

Reported by inian1...@gmail.com, Apr 17 2016

Issue description

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

Steps to reproduce the problem:
1. Go to the Chrome JS Console
2. define a variable called dir and print its length (see attached screenshots)

What is the expected behavior?
The wrong length gets printed

What went wrong?
Chrome's console Object gets precedence when evaluating the expression leading to incorrect values. 
Funnily, this doesn't happen to variables named "log" 

Did this work before? N/A 

Chrome version: 49.0.2623.112  Channel: stable
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0
 
Screenshot 2016-04-17 22.35.00.png
46.3 KB View Download
Components: -Blink Platform>DevTools

Comment 2 by allada@chromium.org, Apr 25 2016

Status: Fixed (was: Unconfirmed)
Looks like this has been fixed in Tip of Tree.
dir_issue.png
10.8 KB View Download

Comment 3 by inian1...@gmail.com, Apr 26 2016

Yup. I confirm this is fixed in the latest Canary. 

Sign in to add a comment