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

Warning for -webkit-text-stroke #291

Open
3rd-Eden opened this issue Jul 5, 2012 · 4 comments
Open

Warning for -webkit-text-stroke #291

3rd-Eden opened this issue Jul 5, 2012 · 4 comments
Labels

Comments

@3rd-Eden
Copy link

3rd-Eden commented Jul 5, 2012

Using -webkit-text-stroke on pages with a lot of text completely murders the scrolling performance on your page. It's not noticeable on Safari on Mac (using decent hardware) but if you use Safari under windows you will notice a horrible lag in scrolling. Same issue also applies to Safari Mobile.

More information about this hack: http://dribbble.com/shots/6322-Text-thinning

I'm aware that it can also be used to create fancy pancy headings, so I would advice that the checks are only done against the body and html selectors.

@nzakas
Copy link
Contributor

nzakas commented Jul 5, 2012

@stubbornella ?

@dmcass
Copy link

dmcass commented Jul 5, 2012

Since that link is specifically talking about using -webkit-text-stroke for thinning text, it's probably worth bringing -webkit-font-smoothing into this conversation.

More info: http://maxvoltar.com/archive/-webkit-font-smoothing/

Edit: I realize now that I might be off-base here since -webkit-text-stroke has performance implications regardless of what it's used for...so if my comment isn't helpful just ignore me :)

@3rd-Eden
Copy link
Author

3rd-Eden commented Jul 5, 2012

the -webkit-font-smoothing has no performance implications. But there are more CSS rules that seriously murder your page rending performance, like translate3d on your body element etc..

@stubbornella
Copy link
Member

This sounds like a good test to me, but in order to be sure it is a problem, I think we need a simple test page that has the issue. That way if newer versions of the browser handle scrolling + -webkit-text-stroke better we can target the rule to only older versions.

@3rd-Eden - can you make a test page?

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

No branches or pull requests

4 participants