Powerpoint is broken when the scheduling API is enabled.
Categories
(Core :: DOM: Performance, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox99 | --- | unaffected |
firefox100 | --- | unaffected |
firefox101 | --- | fixed |
People
(Reporter: sefeng, Assigned: sefeng)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: perf-alert, regression)
Attachments
(1 file)
https://www.office.com/launch/powerpoint?auth=1 (need to login first) is not loading when the scheduling API is enabled.
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1734997
Assignee | ||
Comment 2•2 years ago
|
||
This is missing from the original implementation.
Updated•2 years ago
|
Pushed by sefeng@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/df8cc0e83371 Mark the scheduler attribute replaceable r=smaug
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/33766 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
Comment 6•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Comment 7•2 years ago
|
||
(In reply to Pulsebot from comment #3)
Pushed by sefeng@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/df8cc0e83371
Mark the scheduler attribute replaceable r=smaug
== Change summary for alert #33927 (as of Mon, 25 Apr 2022 17:09:33 GMT) ==
Regressions:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
81% | office loadtime | linux1804-64-shippable-qr | fission warm webrender | 226.74 -> 411.08 |
75% | office loadtime | linux1804-64-shippable-qr | cold fission webrender | 442.28 -> 774.04 |
55% | office fcp | linux1804-64-shippable-qr | fission warm webrender | 253.14 -> 392.79 |
21% | office fcp | linux1804-64-shippable-qr | cold fission webrender | 481.04 -> 583.46 |
For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=33927
Updated•2 years ago
|
Assignee | ||
Comment 8•2 years ago
|
||
We first got the improvement in bug 1734997 which was due to a bug in the implementation. This bug fixes the bug and reverted the improvement back to normal. So the regression here is good.
Description
•