|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
59 bytes, text/x-review-board-request
|Details | Review|
ActivityStream wants to be able to gauge perceived performance starting as close to the time as the user takes an action to open a new tab as possible. This won't capture 100% of tab opens because browser.js, <tabbrowser> and friends are fairly spaghetti-like due in part to their ancient heritage, but it seems it ought to get the vast majority. Patch forthcoming.
The first try run claimed that there were a bunch of failures (which didn't seem to be true, I could only see one, which was a known intermittent). Furthermore, it didn't generate any talos data. So I've fired off another one, and with luck, things will look better there.
Comment on attachment 8870624 [details] Bug 1367119 - make BrowserOpenTab fire browser-open-newtab-start observer, https://reviewboard.mozilla.org/r/142072/#review147990
Attachment #8870624 - Flags: review?(edilee) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/159c286ba575 make BrowserOpenTab fire browser-open-newtab-start observer, r=Mardak
Status: NEW → RESOLVED
Last Resolved: a year ago
status-firefox55: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
You need to log in before you can comment on or make changes to this bug.