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

Semantic UI for latest version of Chrome #4629

Closed
akshayrpatel opened this issue Oct 5, 2016 · 6 comments
Closed

Semantic UI for latest version of Chrome #4629

akshayrpatel opened this issue Oct 5, 2016 · 6 comments

Comments

@akshayrpatel
Copy link

Hello,
Suddenly my app is experiencing front end issues on chrome but works fine on firefox. I did not make any changes to my app (no recent builds) and suddenly chrome is behaving weird - on scrolling some content scrolls up while some content just sticks to its original place. I view my console and get no errors in chrome but on the other side when I load my app on firefox (works fine) and view the console, it gives me 1000's of CSS warnings. I tried to look up those CSS properties and found them in semantic.css file & some in iconicons.css.
I installed an older version of chrome and my app worked fine on chrome(no errors in console) and firefox(those errors persisted).
Does this have to do with compatibility between chrome and Semantic UI ?

I am using Semantic UI v2.0.0 & Iconicons v2.0.0

-Thanks

@SrPatinhas
Copy link

It looks like this new version of chrome messed up with several components. im having the same issue with the vertical dividers

@jlukic
Copy link
Member

jlukic commented Oct 10, 2016

Vertical dividers are the only component I am familiar with being broken. #4342

I've posted a bug with Chromium. There does not appear to be a workaround from a framework level. Hopefully Chrome team can fix this soon.

View Chrome Issue 633011

w3c/csswg-drafts#401

@akshayrpatel
Copy link
Author

Any updates on this lately ?

@awgv
Copy link
Member

awgv commented Feb 20, 2017

Hi @akshayrpatel, have you resolved it since then?

@vinayakkulkarni
Copy link
Member

Hey @akshayrpatel, did you resolve it? SUI is at 2.2.9 and you used 2.0.0 which is history 😛

@akshayrpatel
Copy link
Author

@Banandrew @vinayakkulkarni the issue resolved on its own, I assume some Chrome update fixed it.
@vinayakkulkarni hahaha true, the tool I worked on was built long time ago, probably that's why, nothing I can do...🙃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants