Re: [WikimediaMobile] Special casing of main pages on mobile

On 17 jul. 2012, at 21:23, Jon Robson wrote: Agreed Yes this is the problem. I don't see this as a requirement. We just need to provide alternate CSS and HTML layout (without fundamentally breaking IE6) and it needs to be implemented. I still don't agree with your comments on removing inline styling. If we move all inline styling we have on en.wp, we will have a style file of over 1 MB easily. We need to be more sensible about it. Portal styling is arguably one of those things used on only about 15 pages per wiki. There is no point in having it globally. At most there is a point in having a separate stylesheet for those 10 pages, though that leads to cache fragmentation and slower loading times I fear. (I can see a use for cache fragmentation over namespaces, because most readers never get out of main space, but other than that, you never really want to fragment the cache of mainspace much I think). For years the en.wp community has tried to specifically keep certain styles inline if they are used infrequently (anything under about a 100 transclusions) simply to keep connection and download size per page per reader somewhat consistent and usable. That styling is usually captured in templates for easy switching, and everything has id's and classes. Yes this system is now also reaching it's limits, but it means we need to be smart and take into account WHY we use inline styles, and for en.wp it's because bytes do add up. After weeding down several css filesizes in 2010, the difference was measurable (both in parsing and visually). Yes connection count was a worse problem, and RL does solve some of that, but size also does add up. Never forget how extreme the english wikipedia is in size. Perhaps we need transcluded internal stylesheets for these kinds of pages, so only pages that need this css get this css. DJ