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

Invalid YGDisplay 'inline-block' #257

Closed
WDDong opened this issue Apr 19, 2019 · 10 comments
Closed

Invalid YGDisplay 'inline-block' #257

WDDong opened this issue Apr 19, 2019 · 10 comments
Labels
is:FAQ candidate A canonical issue to put in the FAQ.

Comments

@WDDong
Copy link

WDDong commented Apr 19, 2019

DA2B8E4DF27DB292E483F8DA4DE282B7

@nolife08021
Copy link

i have same issue like @WDDong too.
any advices?

@hadi13
Copy link

hadi13 commented May 26, 2019

same for me

2 similar comments
@happylinhdn
Copy link

same for me

@Wellington01
Copy link

same for me

@sumudu-dewasurendra
Copy link

If anyone can put similar issues in here, at least we can ignore those styles and use this library :-D

@jpamarohorta
Copy link
Contributor

jpamarohorta commented Aug 6, 2019

I'm having the same issue. Created PR 282 that fixes it.

@AlanQuadros
Copy link

Just add 'display' in ignoredStyles.

Ex.:
ignoredStyles={['font-family', 'display']}

@jpamarohorta
Copy link
Contributor

Adding display to ignoredStyles can not always be possible. I have a case when if the display is “none” I want to hide the element for example.

@hai2san
Copy link

hai2san commented Aug 28, 2019

I'm having the same issue.

@jsamr jsamr added the is:FAQ candidate A canonical issue to put in the FAQ. label Jul 4, 2020
@jsamr jsamr linked a pull request Jul 4, 2020 that will close this issue
@jsamr jsamr added the is:waiting pr A pull request is awaiting reviews to solve the problem. label Jul 4, 2020
@jsamr jsamr closed this as completed in 4997f2f Jul 17, 2020
@jsamr jsamr removed the is:waiting pr A pull request is awaiting reviews to solve the problem. label Jul 17, 2020
@jsamr
Copy link
Collaborator

jsamr commented Jul 24, 2020

This issue will be fixed in version 4.2.2.
A pre-release is already available if you want this fix now, see #385.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:FAQ candidate A canonical issue to put in the FAQ.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants