duckduckgo / Android

DuckDuckGo Android App
https://play.google.com/store/apps/details?id=com.duckduckgo.mobile.android
Apache License 2.0
3.77k stars 892 forks source link

[Bug] font size for plaintext should mirror html font size #4555

Closed akkana closed 3 months ago

akkana commented 4 months ago

Describe the bug

I have font size set to 120% in Accessibility Settings, and basic web pages look fine (as long as they have a or equivalent, otherwise they're tiny).

But plaintext files, .txt, and HTML files that don't have that meta viewport directive, display in a font that's absolutely microscopic. Please, can the browser obey the accessibility settings in those two cases?

Chrome on android now defaults to a nice readable font for .txt files and for html files without meta viewport. But I'd rather use DDG for all my android browsing. :-)

How to Reproduce

Go to: https://shallowsky.com/python/lesson1.txt (or any file ending in .txt).

Notice the tiny font size.

Call up Settings -> Accessibility and drag the slider to set the font size larger, say, 120% or more.

Go back to the text file. Still tiny.

To see the meta viewport difference in HTML files: https://shallowsky.com/python/ is a page that has https://shallowsky.com/obsreport.cgi is an HTML page that doesn't include the meta viewport line.

Notice how tiny the text is on the obsreport page compared with the python page/

Expected behavior

A font large enough to be readable. If I need to increase the text for accessibility reasons, I need it for all types of files, not just one type.

I can pinch-zoom to make the font bigger temporarily, but then the lines disappear off the right side of the screen, whereas if the font size had been larger to begin with, long lines would wrap.

Environment

- DDG App Version: 5.199.5 (51995000)
- Device: Pixel 6a and Lenovo Tab M9
- OS: Android 14 and 13
github-actions[bot] commented 4 months ago

Thank you for opening an Issue in our Repository. The issue has been forwarded to the team and we'll follow up as soon as we have time to investigate. As stated in our Contribution Guidelines, requests for feedback should be addressed via the Feedback section in the Android app.

malmstein commented 3 months ago

@akkana thanks for the bug report. We’ll be working on this in the near future, closing this as triaged.