Tom Livingston wrote on 2014-09-19 16:19 (GMT-0400):
Felix Miata wrote:
I doubt
many practitioners using them have tested against user CSS to see how a UA
deals with the multiplied conflicts
[1]
What I do see is failure to
accommodate larger font sizes in the layout and therefore things over
flow their containers or get cropped. That's poor planning.
Such apparent lack is typical of large sites
This is
failure on the designers/devs part. Not CSS's. Is CSS responsible for
the containers not flexing? Technically, yes. Did it get into the site
by itself and mess things up? No. It was used incorrectly.
HTML for newegg.com home is 636,601 bytes. Its *.css is 407,595 bytes in 6
files. HTML for one newegg.com product http://tinyurl.com/n4cycdp page is
943,588 bytes, *.css 658,164 bytes in 10 files. HTML for logged in user
dashboard is 263,531 bytes, *.css 434,139 bytes in 10 files. How much CSS
may be embedded in scripts or HTML I'm not about spend the time to try to
figure out. The weight of *.css alone is nuts, and newegg.com is anything but
an anomaly. It's hard to imagine how anyone stuck on POTS can stand needing
to use today's Internet.
You've surely heard this by Lord Acton before:
Power corrupts. Absolute power corrupts absolutely.
CSS is power; IMO, too much power for too many to manage, widely misused,
widely misunderstood, and, in actual use, widely and wildly self-conflicting,
besides rude. All that misuse is routine in large sites, many fingers in each
pie surely, but too much power given those fingers nevertheless. At least
with presentation markup, there was a limit to how much the styling could
shrink the text below default. It wasn't as easy as now to make most text
gray on a gray background. With CSS, practitioners have the power, the
freedom, to ignore users' personalized optimums, and now that IE6 is dead,
more and more do exactly that.
Work of people frequenting here, regulars and noobs alike, is not
representative of the styling problems with big sites. One person, given and
using good instruction, is capable of enough restraint to stay out or get out
of most trouble; two or a few, probably the same. But, it's the same power of
CSS whether wisely used or not; no wonder why users complain web browsers use
too much RAM, or why pages don't work well; or in the case of defending via
user styles, why it takes noticeable time for content to stop jumping around
after switching pages within one domain.
[1]
$ ll new*
13706 Oct 21 2010 newegg.css
$ grep important newegg.css | wc -l
156
I know it's old, but the point is it's insane that one user stylesheet
applicable to just one site would have reason to be so big.
--
The wise are known for their understanding, and pleasant
words are persuasive. Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
