Closed Bug 1785983 Opened 3 years ago Closed 3 years ago

Expose CTW in Nightly Experiments

Categories

(Core :: Disability Access APIs, task)

task

Tracking

()

RESOLVED FIXED
106 Branch
Tracking Status
firefox106 --- fixed

People

(Reporter: Jamie, Assigned: Jamie)

References

Details

(Whiteboard: [ctw-m2])

Attachments

(1 file)

This will make it easier for users to test now that we're ready for opt-in Nightly testing.

Pushed by jteh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9863ef8a45cb Expose the parent process accessibility cache in Nightly Experiments. r=morgan,fluent-reviewers,preferences-reviewers,flod,Gijs
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch

Jamie, I thing this should be noted into our Nightly release notes to ask for wider testing, wdyt?

Flags: needinfo?(jteh)

I confess I forgot we had Nightly release notes. 😳

I think this makes sense. Note that this won't be enabled by default in Nightly this cycle and thus nor will it ride the trains this cycle.

The note might say something like this:

Firefox can now cache all accessibility information from all documents in the Firefox main process. This improves performance for screen readers and other applications which use accessibility APIs. This can be enabled in the Nightly Experiments section of Settings.

What's the process here? I assume I shouldn't set the relnote-firefox flag given that this is not intended for the final release notes, only for Nightly?

Flags: needinfo?(jteh)

(In reply to James Teh [:Jamie] from comment #5)

Firefox can now cache all accessibility information from all documents in the Firefox main process. This improves performance for screen readers and other applications which use accessibility APIs. This can be enabled in the Nightly Experiments section of Settings.

What's the process here? I assume I shouldn't set the relnote-firefox flag given that this is not intended for the final release notes, only for Nightly?

Setting the relnote-firefox flag is fine for this purpose, just precise in the request that it is nightly only. Pinging a release manager about it is also fine and I added the note to our Nightly release notes, thanks!
https://www.mozilla.org/en-US/firefox/106.0a1/releasenotes/

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: