-
Notifications
You must be signed in to change notification settings - Fork 163
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
[Android] Incorrect bold font processing #88
Comments
@fbartho, anyone? any clues? |
@Aviemore no idea! -- this is super interesting. It might be a bug in how the top level text object is built. I would expect those two cases to be the same. I would try to compare the Component tree in both cases (using the Inspector). I suspect something different is happening in react-native-parsed-text/src/ParsedText.js Line 110 in fded31e
|
Same issue here, hates any font beyond a regular weight. Bold, semibold, all act the same on Android |
@miamiappmachine Have you tried to use the inspector to understand what's happening to the Text / Font Styling? |
Bizarrely I can't even select it on the element inspector in Android. No problem at all to select it on iOS (where it works perfectly) |
That is indeed super strange. Maybe React-Native Android no longer supports Nested Please do report back what you found. I would totally accept a PR if you find the root issue! -- My team's apps no longer use this library (this was previously used by our Chat code, but we now have a Vendor for that, and that vendor doesn't use this library). So while I'm happy to help review code, and find a fix, I don't have an experimental test-bed actively set up. |
Hey all - problem solved. Patch file attached. |
Preconditions:
Platform: Android
Issue:
Could someone explain this behavior? And how could we fix it?
And this happens for any array of parse param. BUT SHOULD NOT!
I configured some banch of parse templates, but usual text is affected because of this.
Any clues?
I've put this font here as well
EENobblee-Bold.ttf.zip
The text was updated successfully, but these errors were encountered: