Chromium changes:
https://chromium.googlesource.com/chromium/src/+/9c2a3c87dbd2168e374e611422f9d815c67293ab
commit 9c2a3c87dbd2168e374e611422f9d815c67293ab
Author: Shuhei Takahashi <nya@chromium.org>
Date: Mon Dec 8 19:32:36 2025 -0800
extensions: Initialize extension UI post-native-init
This is a part of the patch series to use ExtensionActionViewModel on
Desktop Android.
We currently inflate the extension UI before native initialization,
following many other UI components. This is why we use OneshotSupplier
for ChromeAndroidTask because it is available only after native init.
As we update the extension UI to rely on browser-keyed shared view
models, such as ExtensionActionViewModel, they would introduce many
OneshotSupplier<T>, which is going to be cumbersome.
This patch avoids the problem by moving the extension UI initialization
to post-native-init. After all, we don't show the extension UI before
checking the profile eligibility, whereas profiles are available only
after native init.
Bug: 448199168
Change-Id: Ib0ea1bbb6f0adfc868ddfc1e7eb653f9eb189361
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7214707
Reviewed-by: Patrick Noland <pnoland@chromium.org>
Reviewed-by: Masa Fujita <massan@google.com>
Commit-Queue: Shuhei Takahashi <nya@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1555878}
Artem Samoilenko
94c0253870