[Webkit-unassigned] [Bug 250138] [GTK] Changing system font-scaling factor results in messy rendering of the page (Epiphany, WebKitGtk)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=250138

--- Comment #19 from Glen Whitney <gwhitneycom5 at pobox.com> ---
(In reply to Michael Catanzaro from comment #18)
> So if I understand correctly, there is nothing more to do here after fixing
> bug #247980, yes? It's OK to close this?

That is indeed my feeling, but I have also come to realize that there is quite a diversity of GTK setups out there. So if I were a maintainer, I'd love to get feedback from one of the folks that was actually affected by the concerns as stated here, as they are phrased somewhat differently from the issue #247980 that I am directly addressing.

> The Large Text accessibility setting behaves reasonably when using GTK 4
> after your pull request?

Could you let me know how in a GTK4 environment I can for sure turn on that accessibility setting? (I don't use the Gnome desktop for example, but I can install and run any publicly available GTK4 app, so if there is some sort of GTK4 settings app that would include this accessibility setting please point me to it, thanks. Or maybe there is a `gsettings` command-line I could execute to do it?)

And what would you consider "behaves reasonably"?  E.g.,
  * makes type whatever percentage larger, but leaves the width of dimensioned divs like sidebars alone, so there will be fewer words per line in such dimensioned divs, making the text take up more vertical space and perhaps introducing some odd line breaks, etc.; or
  * makes type whatever percentage larger and also grows other dimensions, so that it basically acts like a screen magnifier within the context of a web page? (In other words, for web pages basically is equivalent to increasing the default zoom from one to some percentage larger than one.)
  * Or something else?

  I'd be happy to test it and see if its behavior matches your hopes/expectations.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240424/0f7fb64c/attachment-0001.htm>