Closed Bug 1470017 Opened 8 years ago Closed 5 months ago

Consider to not change prototype when adopting nodes

Categories

(Core :: DOM: Core & HTML, defect, P3)

defect

Tracking

()

RESOLVED FIXED
151 Branch
Webcompat Priority P3
Tracking Status
firefox151 --- fixed

People

(Reporter: smaug, Assigned: emilio)

References

Details

(Keywords: perf-alert, webcompat:platform-bug)

User Story

user-impact-score:2400

Attachments

(1 file, 1 obsolete file)

Priority: -- → P3
We should consider doing some measurements on the memory aspect here somehow...
(In reply to Boris Zbarsky [:bz] (no decent commit message means r-) from comment #1) > We should consider doing some measurements on the memory aspect here > somehow... I already did, in [1]. So I'm not really in a hurry to do this. If we're going to do anything here, we might as well start with adopting Blink's model for document.open(), since the rationale in [2] is that we can drop transplanting from the spec if we do both of these things. [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567#c56 [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567#c74
Depends on: 1489308
Component: DOM → DOM: Core & HTML
Severity: normal → S3
Duplicate of this bug: 1813499
Webcompat Priority: --- → ?

The severity field for this bug is set to S3. However, the following bug duplicate has higher severity:

:hsinyi, could you consider increasing the severity of this bug to S2?

For more information, please visit auto_nag documentation.

Flags: needinfo?(htsai)

According to the know webcompat report, I am not quite sure if I see the rationale of Bug 1821790 being S2. Kagami, would you kindly answer this needinfo from comment 5 for me, as you have better ideas about this issue? Thank you.

Flags: needinfo?(htsai) → needinfo?(krosylight)

I have no idea, S3 looks fine to me. I'll pass that question to mccr8 who set it.

Flags: needinfo?(krosylight) → needinfo?(continuation)

I thought it was a regression, but this is apparently old behavior.

Flags: needinfo?(continuation)
Webcompat Priority: ? → P3
Duplicate of this bug: 1888296
Duplicate of this bug: 1899532
Assignee: nobody → emilio
Status: NEW → ASSIGNED
User Story: (updated)
Pushed by ealvarez@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/4521a4f9d7fa https://hg.mozilla.org/integration/autoland/rev/d6aba05c3f76 Don't reparent prototype chains on adopt. r=smaug,devtools-reviewers,jdescottes,webidl,nchevobbe
Pushed by sstanca@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/f58d86ae2499 https://hg.mozilla.org/integration/autoland/rev/8fb39fd0ea23 Revert "Bug 1470017 - Don't reparent prototype chains on adopt. r=smaug,devtools-reviewers,jdescottes,webidl,nchevobbe" for causing mochitests assertion failures in HTMLMediaElement.cpp.

Reverted this because it was causing mochitests assertion failures in HTMLMediaElement.cpp.

Also please check these mochitests failures and these ones.

Flags: needinfo?(emilio)

Child actors generally deal with content nodes, and those can be
adopted, in order to preserve behavior, switch to the new
.ownerDocGlobal.

Fix + rename the use-ownerGlobal lint since now it's wrong.
.ownerDocument.defaultView is .ownerDocGlobal, not .ownerGlobal now.

Pushed by ealvarez@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/3ca434ce61bd https://hg.mozilla.org/integration/autoland/rev/551161093ac6 Don't reparent prototype chains on adopt. r=smaug,devtools-reviewers,jdescottes,webidl,nchevobbe
Attachment #9570852 - Attachment description: Bug 1470017 - Use ownerDocGlobal where appropriate in child actors. r=#firefox-desktop-core-reviewers! → Bug 1470017 - Use ownerDocGlobal where appropriate in child actors and remote/. r=#firefox-desktop-core-reviewers!
See Also: → 2032691
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
Blocks: 2033191
Blocks: 1502814
No longer depends on: 1502814
Duplicate of this bug: 1502814
No longer blocks: 1502814
Blocks: 2033242

Comment on attachment 9570852 [details]
Bug 1470017 - Use ownerDocGlobal where appropriate in child actors and remote/. r=#firefox-desktop-core-reviewers!

Revision D294805 was moved to bug 2033242. Setting attachment 9570852 [details] to obsolete.

Attachment #9570852 - Attachment is obsolete: true
Flags: needinfo?(emilio)
QA Whiteboard: [qa-triage-done-c152/b151]

(In reply to Pulsebot from comment #16)

Pushed by ealvarez@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/3ca434ce61bd
https://hg.mozilla.org/integration/autoland/rev/551161093ac6
Don't reparent prototype chains on adopt.
r=smaug,devtools-reviewers,jdescottes,webidl,nchevobbe

Perfherder has detected a browsertime performance change from push 551161093ac62a253604afcf21977f4ecbb6f5cc.

No action is required from the author; this comment is provided for informational purposes only.

Improvement Test Platform Options Absolute values [old vs new] Performance Profiles
6% google-slides LastVisualChange (doc) linux2404-64-shippable bytecode-cached fission warm webrender 2,306.46 ms -> 2,168.27 ms Before/After

Need Help or Information?

If you have any questions, please reach out to afinder@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

Regressions: 2041720
Regressions: 2043569
Keywords: perf-alert
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: