Open Bug 1895760 Opened 2 years ago Updated 1 year ago

Unify async control flow in WinUtils for async favicon fetching

Categories

(Core :: Widget: Win32, task)

Product:
Core
Component:
Widget: Win32
Type:
task

Tracking

()

People

(Reporter: mconley, Unassigned)

References

Details

In bug 1503809, I added a mechanism to allow a caller to await a MozPromise to resolve for the WinUtils favicon caching mechanism. This optional mechanism operates alongside a pre-existing optional nsIRunnable mechanism.

It's pretty awkward to have 2 similar optional mechanisms sit side-by-side. What'd be better is to either transition all of the callers to use the MozPromise mechanism and to get rid of the runnable, or to have the nsIRunnable mechanism get resolved by the MozPromise somehow.

The former might be better though, if possible - having just a single way of getting an answer back on if and when the favicon gets fetched would be really nice.

Severity: -- → S4
You need to log in before you can comment on or make changes to this bug.