Last modified: 2014-07-01 23:32:31 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69286, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67286 - Recent regression caused blurry content text on iPad (desktop/Vector skin)
Recent regression caused blurry content text on iPad (desktop/Vector skin)
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Brion Vibber
http://en.wikipedia.org/
:
: 67308 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-29 22:19 UTC by Brion Vibber
Modified: 2014-07-01 23:32 UTC (History)
7 users (show)

See Also:
Web browser: Apple Safari
Mobile Platform: iOS 7.x
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2014-06-29 22:19:13 UTC
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
Comment 1 Brion Vibber 2014-06-29 22:22:27 UTC
https://gerrit.wikimedia.org/r/#/c/142975/ <- patch to remove the bad rule
Comment 2 Gerrit Notification Bot 2014-06-29 22:30:24 UTC
Change 142975 had a related patch set uploaded by Brion VIBBER:
Remove 'webkit-backface-removal' rule which made iPads super blurry

https://gerrit.wikimedia.org/r/142975
Comment 3 Bartosz Dziewoński 2014-06-30 17:38:30 UTC
*** Bug 67308 has been marked as a duplicate of this bug. ***
Comment 4 Gerrit Notification Bot 2014-06-30 17:43:16 UTC
Change 142975 merged by jenkins-bot:
Remove 'webkit-backface-visibility' rule which made iPads super blurry

https://gerrit.wikimedia.org/r/142975
Comment 5 Gerrit Notification Bot 2014-07-01 22:56:36 UTC
Change 143503 had a related patch set uploaded by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry

https://gerrit.wikimedia.org/r/143503
Comment 6 Gerrit Notification Bot 2014-07-01 22:57:31 UTC
Change 143504 had a related patch set uploaded by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry

https://gerrit.wikimedia.org/r/143504
Comment 7 Gerrit Notification Bot 2014-07-01 23:00:44 UTC
Change 143503 merged by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry

https://gerrit.wikimedia.org/r/143503
Comment 8 Gerrit Notification Bot 2014-07-01 23:02:30 UTC
Change 143504 merged by MaxSem:
Remove 'webkit-backface-visibility' rule which made iPads super blurry

https://gerrit.wikimedia.org/r/143504
Comment 9 Jon 2014-07-01 23:26:00 UTC
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 10 Brion Vibber 2014-07-01 23:27:29 UTC
(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 11 Bartosz Dziewoński 2014-07-01 23:32:23 UTC
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 :)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links