[Webkit-unassigned] [Bug 27203] Inspector: Remove Unintended Global Variables

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jul 13 13:59:03 PDT 2009


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





--- Comment #5 from Joseph Pecoraro <joepeck02 at gmail.com>  2009-07-13 13:59:02 PDT ---
As far as modifying anything on the actually inspected page I have doubts that
anything else is affected.  From what I've seen, code in the Inspector is
separate from the inspected page and anything to go in the inspected page needs
to be specially evaluted.  The correction above is the only place where this is
done with any significance.

However, this could be useful to clean up Javascript inside the Inspector page
or better yet javascript in general.

Does WebKit have the ability to do a JSLint like compilation of a Javascript
file and identify potential problems such as "implied globals" or access
outside of an existing scope?  Seeing as there are JIT compilers then this kind
of static analysis would be useful for developers.

I haven't written an test cases before. I could look into doing something like
this (no promises yet).  The problem I see with a test case for this is that
the inspector adds a lot of functions on html/dom prototypes (see
utilities.js).  If any more are created or modified then the test-case should
be corrected.  Is that kind of dependency normal for test cases?

-- 
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