0. Unsandboxed Chromium in Wayland ((unsupported and just for testing purposes!) /snap/chromium_edge/current/usr/lib/chromium-browser/chrome --ozone-platform-hint=wayland) has no issues responding to 'large text' setting. This must be a downstream problem.
1. Chromium in the sandbox can see changes to text-scaling-factor via gsettings: nteodosio@canonical:/home/nteodosio$ gsettings get org.gnome.desktop.interface text-scaling-factor 1.0 #After changing to 1.5 in the host...: nteodosio@canonical:/home/nteodosio$ gsettings get org.gnome.desktop.interface text-scaling-factor 1.5 2. It moreover acknowledges the change in that setting with: (chrome:33484): Gdk-DEBUG: 10:20:33.195: Using changed portal setting org.gnome.desktop.interface text-scaling-factor: 1.5 3. Judging by //gdk/wayland/gdkdisplay-wayland.c, GTK gets it from the settings portal when a Gsetting changes. All Gnome applications (but the here discussed snapped Chromium on Ozone) respond. However, in the stderr one does see 4. Why does Chromium bundle the GTK tree (in //third_party/wayland- protocols), though? At any rate it does not seem to use it: The debug statements I injected there are never triggered. 5. There is a --enable-wayland-server option but judging by the variable name (kAshEnableWaylandServer) it probably does nothing in Linux. Indeed, if the Wayland interface is disconnected from Chromium, it fails to launch regardless. 6. Xorg's side of it does not have any mention to text-scaling-factor and indeed no application responds to that Gsetting in Icewm or Dwm. But they do on Gnome-Shell (in Xorg). Gnome-Shell has //js/ui/status:_buildFontItem which responds to that setting, but I do not understand how it is able to propagate it to its windows (as these are other programs, other processes, right?). 7. --force-device-scale-factor is experimental and indeed Chromium goes wild with it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium - 127.0.6533.119 wayland Chromium app ignores large text setting if started with --ozone- platform-hint=wayland. ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 18 20:25:21 2024 InstallationDate: Installed on 2024-08-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> Snap: chromium 127.0.6533.119 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
