The variant `editor-legacy-direction` expiration is on 2023-09-01
Categories
(Core :: DOM: Editor, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox119 | --- | fixed |
People
(Reporter: release-mgmt-account-bot, Assigned: masayuki)
Details
(Whiteboard: [variant-expiration], [wptsync upstream])
Attachments
(1 file)
If the variant is not used anymore, please drop it from the variants.yml file. If there is a need to keep the variant, please submit a patch to modify the expiration date. Variants will not be scheduled to run after the expiration date.
This bug will be closed automatically once the variant is dropped or the expiration date is updated in the variants.yml file.
More information about variants can be found on Firefox Source Docs.
Note: please do not edit the bug summary or close the bug, it could break the automation.
|
Reporter | |
Comment 1•10 months ago
|
||
The variant will expire in 14 days from now.
A patch to drop the variant or extend its expiration date should be attached to this bug.
:kmag, could you please follow up on this?
|
|
Reporter | |
Comment 2•10 months ago
|
||
The variant will expire in 11 days from now.
A patch to drop the variant or extend its expiration date should be attached to this bug.
:edgar, could you please follow up on this?
|
Assignee | |
Comment 3•10 months ago
|
||
I'll prepare that. I think that we don't need to keep the legacy mode check anymore because there is no new regression reports about the new mode. However, ESR 115 may not be yet tested in some user organizations.
Hsin-Yi-san, what do you think? Should we keep the legacy mode tests for a couple of releases until ESR 102 finishes completely?
|
|
Assignee | |
Comment 4•10 months ago
|
||
Err, sorry, I was confused. ESR 115 branch won't receive new uplifts from m-c. So, we don't need to run them in m-c.
|
|
Assignee | |
Comment 5•10 months ago
|
||
The new join/split node direction mode seems working well in the wild because
we have no regression reports about it. Therefore, we won't revert the pref
anymore, thus, the legacy mode behavior check is not required.
|
|
Reporter | |
Comment 6•10 months ago
|
||
The variant will expire in 4 days from now.
A patch to drop the variant or extend its expiration date should be attached to this bug.
:farre, could you please follow up on this?
|
|
Assignee | |
Comment 7•10 months ago
|
||
jgraham, could you review the patch? It's trying to drop the task added in bug 1827541.
|
|
Reporter | |
Comment 8•10 months ago
|
||
The variant has expired. Expired variants will not be scheduled for testing. Please remove the variant from the variants.yml file.
|
||
Updated•10 months ago
|
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/dd6f6a4acfbf Get rid of the tasks checking the legacy join/split direction mode of editor r=m_kato,jmaher,taskgraph-reviewers,gbrown,webdriver-reviewers,jgraham
|
||
Comment 10•10 months ago
|
||
| bugherder | ||
Failed to create upstream wpt PR due to merge conflicts. This requires fixup from a wpt sync admin.
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/41844 for changes under testing/web-platform/tests
Upstream PR was closed without merging
Upstream PR was closed without merging
Upstream PR merged by moz-wptsync-bot
|
||
Updated•10 months ago
|
|
||
Comment 16•9 months ago
|
||
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5cc9f9d13312 [wpt PR 41844] - [Gecko Bug 1846997] Get rid of the tasks checking the legacy join/split direction mode of editor, a=testonly
|
||
Comment 17•9 months ago
|
||
| bugherder | ||
Description
•