New issue
Advanced search Search tips

Issue 630551 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

New feature request Variables

Reported by valtid.c...@gmail.com, Jul 22 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
I wish to submit a feature request for dev tools.

The feature should be called "Variables":

Where we can inspect the variables (DOM objects like window, jQuery etc..).
It should be split in the following groups:
GLOBAL SCOPE User defined variables (anything that isn't defined by the browser itself, like jQuery, _, underscore,)
USER AGENT defined variables (window, HTMLElement, JSON,...)
USER AGENT reserved keywords (optional) (e.g: var, global, window, for etc...)
The reason: 
It should help to keep global scope clean from pollution and at a minimum and give an incentive to developer to not pollute the global scope.

This is simply an idea, not sure if this is the best approach or something worth while but I would be more inclined to keep the global scope at a minimum if I see too many variables on one place, where as if it's all mixed with user agents variables because there are so many there and I don't get a sense of how much pollution I have caused I would be less sensitive to creating more.

Over time it should help libraries and developer to keep the global scope at a minimum.

What is the expected behavior?
[see above]

What went wrong?
Nothing

Did this work before? N/A 

Chrome version: 51.0.2704.103  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0
 

Comment 1 by caseq@chromium.org, Jul 22 2016

Status: WontFix (was: Unconfirmed)
I suggest you use Watch section to monitor values of variables of interest.
I don't think it would be practical to list all names within the global scope, either broswer- or user- defined, as they're too numerous.
Also, what's the point of listing JS reserved words?

Sign in to add a comment