-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
After update to MIUI 12,Text is cut off #29259
Comments
currently ,we hook Text render to make it work correctly. Text.render = function render(props, ref) {
` |
This is caused by the default FontFamily of MIUI 12: "小米兰亭 PRO". It's a |
@jinshiyi11 |
|
|
The same issue in miui 12 |
cannot fix the problem |
It did work to set a default property - {fontFamily: ''} in style property of Text |
same here, |
The same issue in RN0.63.2 |
the code likes below
|
any update ? |
MIUI 12.0.5 , same here |
This looks more like a MIUI 12 issue to me. We had the same problem, but when we changed the system's font weight to another value (in Settings - Display - Text size & font weight), the issue disappeared. When we changed it back to the original value, the rendering remained perfect. |
最后你们怎么解决问题的,RN0.62.2 小米10, MIUI12.0.8同样问题。 |
|
这个是写在app.js里面,全局设置字体? |
@magicismight where this code be put? |
it works for me |
This comment was marked as off-topic.
This comment was marked as off-topic.
This issue is waiting for author's feedback since 24 days. Please provide the requested feedback or this will be closed in 7 days. |
This issue was closed because the author hasn't provided the requested feedback after 7 days. |
Description
After update to MIUI 12, Text is cut off.
the actual text is QQ,but only Q is displayed
React Native version:
React Native version: 0.60.5
model: MI 10 Pro
android:10
MIUI:12.0.1
Fingerprint -> Xiaomi/cmi/cmi:10/QKQ1.191117.002/V12.0.1.0.QJACNXM:user/release-keys
Steps To Reproduce
updrade XiaoMi Phone's system to MIUI 12
Expected Results
full text is expected to display,like below
The text was updated successfully, but these errors were encountered: