Closed Bug 1746124 Opened 3 years ago Closed 3 years ago

Use PRIORITY_RENDER_BLOCKING runnable priority for Fluent async l10n

Categories

(Core :: Internationalization: Localization, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
97 Branch
Tracking Status
firefox97 --- fixed

People

(Reporter: zbraniecki, Assigned: zbraniecki)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

In bug 1738748 :smaug suggested that we try using nsIRunnablePriority::PRIORITY_RENDER_BLOCKING to alleviate some of the async l10n frame delay.

This is a smaller task with less friction than what I suggested in bug 1738748, and the sync-shortcut for resolved messages may still be implemented on top of it.

This is possible thanks to :nika's recently landed improvements to moz_task Rust API in bug 1739727.

Blocks: 1737951
Depends on: 1739727
Assignee: nobody → zbraniecki
Severity: -- → S3
Status: NEW → ASSIGNED
Priority: -- → P2

I confirmed that with this patch and a small changes in bug 1737951 I was able to remove the flicker there.

Pushed by zbraniecki@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a9e0339866d2
Use nsIRunnablePriority::PRIORITY_RENDER_BLOCKING for Fluent async API calls. r=nordzilla,nika
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
Regressions: 1746879
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: