Closed
Bug 1021258
Opened 10 years ago
Closed 10 years ago
Prototype mutation warning no longer displays when invoking __proto__ setter
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: bholley, Assigned: bholley)
References
Details
(Keywords: regression)
Attachments
(1 file)
3.85 KB,
patch
|
luke
:
review+
|
Details | Diff | Splinter Review |
This is a regression from bug 992958. Patch coming up.
Assignee | ||
Updated•10 years ago
|
tracking-firefox32:
--- → ?
Assignee | ||
Comment 1•10 years ago
|
||
(Tracking given proximity to the merge)
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8435277 -
Flags: review?(luke)
![]() |
||
Updated•10 years ago
|
Attachment #8435277 -
Flags: review?(luke) → review+
Assignee | ||
Comment 3•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/8b809afd1cea
Comment 4•10 years ago
|
||
Comment on attachment 8435277 [details] [diff] [review] Restore the __proto__ mutation warning for __proto__ sets. v1 >+ window[0].eval('var foo = {}; Object.setPrototypeOf(foo, {});' + >+ 'var bar = {}; Object.getPrototypeOf(bar, {});'); Typo? (I assume here your intention is to expect one mutation warning for two prototype sets.)
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/257a99604e30 for somehow breaking Android m8: https://tbpl.mozilla.org/php/getParsedLog.php?id=41162065&tree=Mozilla-Inbound
Flags: needinfo?(bobbyholley)
Assignee | ||
Comment 6•10 years ago
|
||
That is one of the most bizarre failures I've ever seen. Let's figure out whether it relates to the code change or to the test (somehow).
Assignee | ||
Comment 7•10 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=8f6334293b27
Flags: needinfo?(bobbyholley)
Comment 8•10 years ago
|
||
(In reply to Wes Kocher (:KWierso) from comment #5) > Backed out in > https://hg.mozilla.org/integration/mozilla-inbound/rev/257a99604e30 for > somehow breaking Android m8: > https://tbpl.mozilla.org/php/getParsedLog.php?id=41162065&tree=Mozilla- > Inbound It turns out the test is broken & this landing just bumped it from one mochitest chunk to another causing it to fail (since that test must rely on previous state; sigh). The test will be disabled in bug 1021644, after which this can reland :-)
Comment 9•10 years ago
|
||
Relanded: remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/31c707eb3a4b
Comment 10•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/31c707eb3a4b
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Updated•10 years ago
|
Updated•10 years ago
|
status-firefox32:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•