It's not unexpected that pinning may take a bit longer on MSIX (though I suspect there are ways we could speed it up). :pdahiya :mconley we don't seem to act on the results of pinning or setting default. If there any reason we're awaiting this for UI transitions?
Bug 1887011 Comment 11 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It's not unexpected that pinning may take a bit longer on MSIX (though I suspect there are ways we could speed it up). :pdahiya :mconley we don't seem to act on the results of pinning or setting default. If there any reason we're awaiting this for UI transitions? Or are we accidentally blocking the main thread?
It's not unexpected that pinning may take a bit longer on MSIX (though I suspect there are ways we could speed it up). :pdahiya :mconley we don't seem to act on the results of pinning or setting default. If there any reason we're awaiting this for UI transitions? ~~Or are we accidentally blocking the main thread?~~ Edit: doesn't look like there's any code path pinning-side that would block the main thread.
It's not unexpected that pinning may take a bit longer on MSIX (though I suspect there are ways we could speed it up). :pdahiya :mconley we don't seem to act on the results of pinning or setting default. If there any reason we're awaiting this for UI transitions? ~~Or are we accidentally blocking the main thread?~~ Edit: doesn't look like there's any code path native code-side that would block the main thread.
It's not unexpected that pinning may take a bit longer on MSIX (though I suspect there are ways we could speed it up). :pdahiya :mconley we don't seem to act on the results of pinning or setting default. If there any reason we're awaiting this for UI transitions? ~~Or are we accidentally blocking the main thread?~~ Edit: doesn't look like there's any code path "native code"-side that would block the main thread.