Updates:
Status: Fixed
Comment #15 on issue 1547 by dcar...@chromium.org: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
(No comment was entered for this change.)
--
You received this message because this project is configured to send all
Updates:
Labels: ES5
Comment #14 on issue 1547 by ri...@chromium.org: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
(No comment was entered for this change.)
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8
Comment #12 on issue 1547 by erig...@google.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
The latest WebKit nightly and the latest FF Nightly now both show .
As agreed in comment 10 above, ignore the "Should be iooo" in my test
Comment #11 on issue 1547 by therealb...@gmail.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
Comment 10 seems to be based on ES5 and argues from consistency on that
basis. ES5 is new and not the same as the historical de-facto and de-jure
Comment #10 on issue 1547 by l...@chromium.org: Wrong global in cross-frame
this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
ES5 wants .
I can agree with that. The inconsistency is actually having iooo, which
also makes the leak hazard moot.
*Calling* a funct
Comment #9 on issue 1547 by therealb...@gmail.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
and I believe IE10pp says ioio.
I had hopes. Microsoft dashed them. My testing help says "ioioioio" still.
Naughty IE!
/be
--
v8-dev maili
Comment #8 on issue 1547 by therealb...@gmail.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
ES5 wants . Picking i instead of o for the non-Reference-callee is
a form of dynamic scope and a capability leak hazard.
There's no a-prio
Comment #7 on issue 1547 by l...@chromium.org: Wrong global in cross-frame
this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
We do get the final four 'u's in at least Chrome 14 (don't have Chrome 13
here).
It's the 'o's that we differ on (and that I say has not caused any
Comment #6 on issue 1547 by therealb...@gmail.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
Sorry for the redundant comment -- the issue tracker did not show my first
even on a shift-reload in Chrome or Firefox.
Attached is a test Mark ha
Comment #4 on issue 1547 by therealb...@gmail.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
ES3 + reality of multiple global objects differs from ES5. We can make a
concerted effort to change several implementations to conform to ES5 +
mu
Comment #5 on issue 1547 by therealb...@gmail.com: Wrong global in
cross-frame this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
it doesn't seem that it actually affects anyone.
It certainly affected the person who filed
https://bugzilla.mozilla.org/show_bug.cgi?id=634590 -
Updates:
Labels: -ES5 Priority-Low
Comment #3 on issue 1547 by l...@chromium.org: Wrong global in cross-frame
this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
On the other hand, having different behavior for f() and (1,f)() is pretty
inconsistent. It also means that i
Updates:
Labels: ES5 Type-Bug
Comment #2 on issue 1547 by l...@chromium.org: Wrong global in cross-frame
this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
I.e., the problem is with calling a function where the expression does not
evaluate to a Reference. The bugzilla e
Updates:
Status: Accepted
Owner: l...@chromium.org
Comment #1 on issue 1547 by ri...@chromium.org: Wrong global in cross-frame
this-coercion
http://code.google.com/p/v8/issues/detail?id=1547
Lasse actually already had some input on this a few months back, assigning
to him
14 matches
Mail list logo
