Alright, got it. ungoogled/disable-ai.patch is a bit overzealous in
removing code from chrome/renderer/chrome_render_frame_observer.cc:
-#if !BUILDFLAG(IS_ANDROID)
- if (process_state::IsInstantProcess()) {
- SearchBoxExtension::Install(render_frame()->GetWebFrame());
- }
-
- // Install ReadAnythingAppController on render frames with the Read
Anything
- // url, which is chrome-untrusted. ReadAnythingAppController installs v8
- // bindings in the chrome.readingMode namespace which are consumed by
- // read_anything/app.ts, the resource of the Read Anything WebUI.
- if (render_frame()->GetWebFrame()->GetDocument().Url() ==
- chrome::kChromeUIUntrustedReadAnythingSidePanelURL) {
- ReadAnythingAppController::Install(render_frame());
- }
-#endif // !BUILDFLAG(IS_ANDROID)
The ReadAnythingAppController::Install() part is related to AI code, but
the SearchBoxExtension::Install() part up top is the search bar on the
new tab page and didn't need to be removed. I'm preparing the new 147
release now, and once that's out the door I'll submit a MR to
ungoogled-chromium to fix it there as well.
On 4/8/26 16:47, Daniel Richard G. wrote:
On Wed, 2026 Apr 8 16:25-04:00, Andres Salomon wrote:
I've narrowed it down to the switch from disable/glic.patch ->
ungoogled/disable-ai.patch. Basically I took all the new stuff
(non-upstream) from .177, including deleting the .pb files, and was able
to reproduce the problematic new tab page on .164. Then if I switch back
from disable-at.patch to glic.patch, it fixes the issue.
It did seem like the new-tab page was being revised for some new AI
feature, but not with an explicit intent to yield the behavior
we're seeing.
I'm looking through the differences between the two now to see if I
can figure out what is causing it.
I was summarizing the diff on the disable-ai PR; aside from your handful
of "assert(enable_glic)" removals, there were only a few code lines
changed. If one of those turns out to make the difference, then we'll
have a quite strange example of a code tweak having a significant yet
non-obvious side effect on the UI.
