Closed Bug 1062418 Opened 10 years ago Closed 7 years ago

Move the remaining nsWindowSH methods to be instance methods of nsGlobalWindow

Categories

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

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla61
Tracking Status
firefox61 --- fixed

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

Attachments

(2 files)

This will probably mean moving a bunch of helper code too.
Depends on: 1017424
For now we preserve the current code structure and function signatures to make review simplere. That's about to get cleaned up. MozReview-Commit-ID: 4epLHQiEwDV
Attachment #8956241 - Flags: review?(nika)
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
MozReview-Commit-ID: HGy6CHx4sCP
Attachment #8956242 - Flags: review?(nika)
> review simplere. "simpler". Fixed locally. ;)
Attachment #8956241 - Flags: review?(nika) → review+
Comment on attachment 8956242 [details] [diff] [review] part 2. Clean up the bits that got moved from nsWindowSH Review of attachment 8956242 [details] [diff] [review]: ----------------------------------------------------------------- ::: dom/base/nsGlobalWindowInner.cpp @@ +16,5 @@ > #include "nsScreen.h" > #include "nsHistory.h" > #include "nsDOMNavigationTiming.h" > #include "nsIDOMStorageManager.h" > +#include "mozilla/dom/DOMJSProxyHandler.h" I presume this is for FillPropertyDescriptor. It looks like this would've been needed in the previous patch too. I'd rather if this hunk was moved into that patch. @@ +2938,3 @@ > { > // Keep track of how often this happens. > Telemetry::Accumulate(Telemetry::COMPONENTS_SHIM_ACCESSED_BY_CONTENT, true); I took a peek at this probe and it looked like ~1% of loads use this. I presume that's still high enough we can't afford to kill it yet :'-( It'd also be good to add a comment here just explaining why this thing has to exist >.<
Attachment #8956242 - Flags: review?(nika) → review+
> It looks like this would've been needed in the previous patch too. Good catch, moved there. > I presume that's still high enough we can't afford to kill it yet :'-( I wonder whether it's measuring what we think it's measuring. In particular, it's not super-obvious to me why we don't hit this for chrome windows. > It'd also be good to add a comment here just explaining why this thing has to exist >.< Can do.
Pushed by bzbarsky@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/f36074b39330 part 1. Move the remaining nsWindowSH bits into nsGlobalWindowInner. r=mystor https://hg.mozilla.org/integration/mozilla-inbound/rev/2f2b7d7d2805 part 2. Clean up the bits that got moved from nsWindowSH. r=mystor
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: