So which rendering mode should I be vetting CSS for? Strict or limited
quirks? Some of the CSS that I review is specifically tweaked for
limited quirks since that's what the Wikimedia sites are running in.
Honestly, I don't know all of the problems that this change will cause.
I imagine it will just be lots of slight changes to how elements line
up, i.e. things shifting by a few pixels in most cases. For example, this:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/File:Login-applied-82…
instead of this:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/File:Login-simplesear…
I haven't thoroughly investigated the ramifications of switching our
rendering mode, and apparently no one else has either. I'm just as
anxious to start using HTML5 as everyone else, but I think we should
have a better plan than "break stuff and revert if enough people
complain". If we know that there are potential issues, shouldn't we have
developers assigned to investigate those issues and report back before
we start deploying things? At the very least, we should get some
developers to inventory the CSS changes that will be needed and have
patches ready for the switch. Otherwise each project is going to
implement their own fixes locally and we'll end up with totally
fragmented CSS. Also, does anyone know if this will affect $wgUseTidy?
Ryan Kaldari
On 3/28/11 8:21 PM, Chad wrote:
On Mon, Mar 28, 2011 at 11:11 PM, Ryan
Kaldari<rkaldari(a)wikimedia.org> wrote:
On 3/28/11 7:53 PM, Chad wrote:
It *was* reverted, it hasn't been deployed
again since.
Well, it still seems to be in place on truck, which is why I'm
getting CSS
bug reports. Can someone revert it on trunk as well?
I highly doubt it. It's been set to true in trunk for about a year now,
running on live sites (Translatewiki) for nearly as long, and this is
the absolute first I've heard of any such issues.
-Chad