[Webkit-unassigned] [Bug 33644] Aliasing javascript globals to elements with matching name/id is inconsistent with Firefox and slow

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 15 10:17:42 PST 2010


Ojan Vafai <ojan at chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |ojan at chromium.org

--- Comment #8 from Ojan Vafai <ojan at chromium.org>  2010-01-15 10:17:37 PST ---
It's not clear to me what the benefit of changing this is outside of purity.
Have you encountered sites where this is actually causing performance problems?
If we were starting from scratch, we obviously wouldn't do this, but there's a
very high likelihood that a non-trivial number of sites depend on this

The downsides of this behavior are that it will confuse some people and in some
cases may cause a minor performance problem. It's unlikely to cause significant
performance problems in practice though. Most sites that I know of that depend
on significant amounts of javascript a) don't rely heavily on globals,
especially not in hot code paths and b) will wrap all their code in an
anonymous function, avoiding this problem.

Not that it weighs in heavily here, but I use this "feature" all the time for
quick debugging.

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