As reported via OTRS and via mobile-l:
http://lists.wikimedia.org/pipermail/mobile-l/2014-June/007469.html
Seems to be caused by a regression in the transitions mixin in I895679ff
Version: unspecified
Severity: normal
URL: http://en.wikipedia.org/
Description
Description
Details
Details
- Reference
- bz67286
Event Timeline
Comment Actions
Change 142975 had a related patch set uploaded by Brion VIBBER:
Remove 'webkit-backface-removal' rule which made iPads super blurry
Comment Actions
Change 142975 merged by jenkins-bot:
Remove 'webkit-backface-visibility' rule which made iPads super blurry
Comment Actions
Change 143503 had a related patch set uploaded by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry
Comment Actions
Change 143504 had a related patch set uploaded by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry
Comment Actions
Change 143503 merged by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry
Comment Actions
Change 143504 merged by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry
Comment Actions
This is quite a well known issue and there for a good reason I
suspect, so I'd urge you to reconsider the fix as by removing it you
have probably introduced jerky animations to mobile:
http://stackoverflow.com/questions/2946748/iphone-webkit-css-animations-cause-flicker
What would be better is to not apply animations willy nilly.
In mobile we have a class called animations that only gets applied to
the html when animations can be run safely.
It would be good to only apply vector-animateLayout for browsers we
know that can cope with it.
Comment Actions
(In reply to Jon from comment #9)
This is quite a well known issue and there for a good reason I
suspect, so I'd urge you to reconsider the fix as by removing it you
have probably introduced jerky animations to mobile:
http://stackoverflow.com/questions/2946748/iphone-webkit-css-animations-
cause-flicker
This just returns us to the rendering we had last week.
Comment Actions
There's been a duplicate bug report and at least one person complaining about this on IRC (today), in addition to what Brion pointed out in comment 0.
We rarely get that much feedback about broken features, and if non-developers report a bug this many times, then it means it's pretty noticeable, so I opted to revert this and consider solving the issue better later. If you can solve the issue better, by all means do :)