Fix application of fontFamily to child nodes #131
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, applying a different
fontFamily
to a nested node doesn't work:One would expect
world
to be shown in the specified font, but it isn't. (It is correctly displayed in italics, though.)The cause is, apparently, this: flutter/flutter#35992
The workaround is easy, but yucky. I personally can't wait for the core issue to be fixed and the fix to make its way to the stable channel, so I will just use my fork, but I understand if you'd prefer to wait for this to be fixed upstream rather than merge this.