Updates:
Status: Upstream
Comment #12 on issue 32040 by a...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
Filed bug upstream and will upload patch.
https://bugs.webkit.org/show_bug.cgi?id=33584
Updates:
Status: Started
Owner: a...@chromium.org
Cc: -a...@chromium.org
Comment #11 on issue 32040 by a...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
I'm pretty sure I know whi
Comment #10 on issue 32040 by a...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
My guess would be that there are some fast checks that we can do to check
if the
property name is present in the DOM befo
Comment #9 on issue 32040 by mbel...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
I believe the binding is ok - V8DOMWindow::namedPropertyGetter is
replicating the
behavior of the JSC reference implem
Comment #8 on issue 32040 by dj...@google.com: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
I ran my test case on Safari 4, it does not exhibit the same slowdown with
this test.
--
You received this message becaus
Updates:
Cc: ant...@chromium.org vita...@chromium.org
Comment #7 on issue 32040 by a...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
Would be interesting to know if Safari has a similar slowdown
Comment #6 on issue 32040 by jam...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
I don't think Document::windowNamedItems() is doing what the author of
V8DOMWindowCustom.cpp thought it did. I doubt we w
Updates:
Labels: -Area-Undefined
Comment #5 on issue 32040 by da...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
(No comment was entered for this change.)
--
You received this message because yo
Updates:
Status: Available
Cc: dglaz...@chromium.org
Labels: Performance Mstone-5 Area-WebKit WebKit-JavaScript
Comment #4 on issue 32040 by da...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/deta
Updates:
Cc: mbel...@chromium.org
Comment #3 on issue 32040 by jam...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
Most of the time is going into WebCore::HTMLNameCollection::itemAfter(),
accor
Updates:
Cc: a...@chromium.org
Comment #2 on issue 32040 by jam...@chromium.org: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
(No comment was entered for this change.)
--
You received this message because you
Comment #1 on issue 32040 by dennis.lee.code: Amount of HTML on a page
seems to affect script load+parse time
http://code.google.com/p/chromium/issues/detail?id=32040
I missed a field when filling out the bug; I tested IE8 too, also seems ok
without
extra delay on scriptLoadParseTest.html.
12 matches
Mail list logo
