Add missing property use counters to Window
Categories
(Core :: DOM: Core & HTML, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Bug 1588194 part 1. Factor out the missing property use counter code into helper functions. r=peterv
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
7.23 KB,
text/plain
|
bmiroglio
:
data-review+
|
Details |
Like bug 1584630 but for Window.
Assignee | ||
Comment 1•5 years ago
|
||
Due to bug 1588257 I can measure Window.defaultStatus
or Window.defaultstatus
but not both. I'll measure the former, but please let me know if you think the latter is more useful...
Assignee | ||
Comment 2•5 years ago
|
||
This incidentally reduces the codesize, while allowing us to call those
functions from elsewhere. The performance impact of the extra out-of-line call
is not measurable (that is, is within the noise level) on the testcase at
https://bugzilla.mozilla.org/attachment.cgi?id=9096814.
Assignee | ||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
Huh. Mike wrote a blog post about this: https://miketaylr.com/posts/2019/03/a-historical-look-at-lowercase-defaultstatus.html
Chrome's use counters say that defaultStatus
is only about twice as popular as defaultstatus
, but the former is the more popular one, so this seems like the right thing to instrument.
Comment 6•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/cd01e6cc73d8
https://hg.mozilla.org/mozilla-central/rev/784c94ebc27f
Comment 7•5 years ago
|
||
Ben, can you pronounce on this review request? Note that code has landed but collection is gated by a pref so we haven't begun collection yet.
Comment 8•5 years ago
•
|
||
Description
•