You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more of an FYI for your reference rather than a bug because I believe the issue is with Chrome itself (OS X only - Windows and Linux seem fine, as are FireFox, Safari and IE).
I've noticed if you have a very long page with a lot of text nodes there is a definite lag before users are able to interact with the page, i.e. before they're able to scroll, or click. You can see the page and the contents, and it's styled, but you can't do anything.
This site uses normalize-opentype and all but one of the pages are fine - we had to remove it from this page due to the performance issue mentioned above. I don't have a working example of the problem unfortunately (as I said before, I removed normalize-opentype from the page we were having problems with).
Let me know if you've come across this before and if you have any thoughts on it. Maybe if I have some spare time I'll set up a test page to see if I can replicate the problem. Of course it's very likely that new versions of Chrome on OS X will fix it...
The text was updated successfully, but these errors were encountered:
This is more of an FYI for your reference rather than a bug because I believe the issue is with Chrome itself (OS X only - Windows and Linux seem fine, as are FireFox, Safari and IE).
I've noticed if you have a very long page with a lot of text nodes there is a definite lag before users are able to interact with the page, i.e. before they're able to scroll, or click. You can see the page and the contents, and it's styled, but you can't do anything.
This site uses normalize-opentype and all but one of the pages are fine - we had to remove it from this page due to the performance issue mentioned above. I don't have a working example of the problem unfortunately (as I said before, I removed normalize-opentype from the page we were having problems with).
Let me know if you've come across this before and if you have any thoughts on it. Maybe if I have some spare time I'll set up a test page to see if I can replicate the problem. Of course it's very likely that new versions of Chrome on OS X will fix it...
The text was updated successfully, but these errors were encountered: