[Webkit-unassigned] [Bug 30212] Each JS execution in console adds extra item into "scripts" combo

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Oct 29 07:42:01 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=30212


Patrick Mueller <pmuellr at yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pfeldman at chromium.org,
                   |                            |timothy at hatcher.name




--- Comment #2 from Patrick Mueller <pmuellr at yahoo.com>  2009-10-29 07:42:01 PDT ---
Over IRC yesterday, pfeldman suggest the current thinking was to just remove
all unnamed (program) entries from the Scripts drop-down, although allow any
"real" evals from code to be able to stepped into.

The downside of this approach is for someone who actually depends on seeing
eval()'d code in the drop-downs, they won't see it anymore.  As a work-around,
they can add

   \n//@sourceURL=some-name-here\n

to their script, and we'll "name" the eval string in the Scripts drop-down.

Think of this as the opt-in approach.

Another story would be the opt-out approach.  Support another directive comment
like the @sourceURL one, but one indicates that this eval should NOT be listed
in the drop-down.  

The idea would then be for the evals that we actually do today (command-line,
watches, etc), we augment the strings we eval with said directive, and nothing
will get added to the Scripts drop-down.  Users would still see their own
evals, as they won't be adding the directive (unless they really want to).

Here are some kinda rando suggestions for directives.

//@do-not-list-script
//@not-enumerable
//@invisible-script

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list