So you mean 'in Chrome', right?
I can indeed no longer reproduce #12.0... Either I screwed up during
testing or something changed in between, which is highly unlikely in
such a short time frame.
Anyway, added debug statements confirm that Chromium is running with
GTK3. Additionally, it DOES recei
I also want to say that the deb version of Google Chrome has the same
behavior 'large text accessibility setting not reflect in Chromium'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.n
8. Chromium is using GTK 3. And the unsandboxed one is too, so the
difference in behavior does not lay on the different GTK versions. Might
be the signal not being caught in the sandbox... I'm building it with a
patch with debugging statements to verify that.
--->
# For snapped Chromium
% for p in
...Chromium builds against GTK 3 but a different version may be loaded
at runtime.
--
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 accessibil
3.1. In GTK4 Chromium listens to the gtk-xft-dpi signal in
//ui/gtk/gtk_ui.cc, thereat calling UpdateDeviceScaleFactor. In GTK3 it
listens to screen resolution's notify::resolution only. Todo: Confirm
the GTK version and whether the respective signal is actually caught and
if so why it cannot do wh
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 change
** Changed in: chromium-browser (Ubuntu)
Status: Fix Released => Triaged
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Description changed:
Chromium - 127.0.6533.119
wayland
- Chromium app ignores large text setting
+ Chro
Glad to hear everything fell into place.
> I think it's best to hide this by default to avoid confusing users
like me.
I do not agree there.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of D
https://issues.chromium.org/issues/360909063
I created a bug report
** Bug watch added: issues.chromium.org/issues #360909063
https://issues.chromium.org/issues/360909063
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-brows
It seems that everything fell into place, the scale is preserved, the title bar
is present again. Indeed, the "use system title bar and borders" option works.
But it is confusing.
Because in the flatpak version, the deb version of Google Chrome, as well as
Chromium downloaded from AUR (I did thi
Reversion committed: https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=66a95be63c03ae2b8c0c5a5d5ee612ded8b51dbd
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a memb
Answering my own question:
> Is anything in your report a regression, i.e., a new issue that was
not there a few days ago?
This is a regression of Chromium in native Wayland, it does not occur in
older releases.
Chromium on Xwayland is fine as tested with --ozone-platform-hint=x11.
** Tags adde
** Summary changed:
- Difference in behavior in wayland and xorg sessions
+ Gnome's large text accessibility setting not reflect in Chromium in Wayland
** Changed in: chromium-browser (Ubuntu)
Status: New => Triaged
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medi
13 matches
Mail list logo
