Chromaniac
Well-known member
check in beta and dev builds. if it is working fine in those browsers, it's likely that chrome developers messed something in current build and it should eventually get fixed in a future update. if beta/dev/canary are showing the same behavior, it becomes complicated.What's the normal process for a fix on something like this? Thanks!