Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Font fallback] From latin characters shown from the font for korean sometimes fallback to Roboto #1615

Open
3 tasks done
idontveapc opened this issue Feb 22, 2024 · 0 comments
Labels
type: possible bug Issues that seem to be a bug, but haven't been confirmed yet

Comments

@idontveapc
Copy link

idontveapc commented Feb 22, 2024

Checklist

  • I have used the search function for open and closed issues to see if someone else has already submitted the same bug report.
  • I will describe the problem with as much detail as possible.
  • If the bug only occurs with a certain link, post, image..., I will include the URL.

App version

7.0.0

Where did you get the app from

Other

Android version

11 GO (32bit)

Device model

First occurred

When selected one of CN, JP, or KR language

Steps to reproduce

  1. Select the app language to KR/JP/CN.
  2. Refresh or restart the app.
  3. Latin characters must be now changed from Roboto.

But

latin chars fallback to Roboto if you start see post faster, like a vid or pic. To check:

  1. Play a video or see a pic JUST WHEN the posts are showed. Leave the video/image viewer, scroll down and you should (scroll to where new posts would've load) see that latin chars now are Roboto style.
  2. If step above isn't reproducible; this must work: Tap on a post or comments icon to see comments BUT JUST BEFORE comments load you tap to view the image or video of that post. Then when you tap back you see all latin chars in the comments are in Roboto.

Example post, link, markdown...

Any post (Video/GIF/Image).

Expected behaviour

The fallback is also random sometimes. But the reproduction step above always do.

Current behaviour

I hope reproduction steps give the outcome im getting.

Logs

response

@idontveapc idontveapc added the type: possible bug Issues that seem to be a bug, but haven't been confirmed yet label Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: possible bug Issues that seem to be a bug, but haven't been confirmed yet
Projects
None yet
Development

No branches or pull requests

1 participant