[www.kde.org] [Bug 317553] www.kde.org webpages should not set font-size of unstyled body text and should comply with 100% Easy-2-Read Std

Gérard Talbot browserbugs at gtalbot.org
Sun Mar 31 11:45:31 UTC 2013


--- Comment #16 from Gérard Talbot <browserbugs at gtalbot.org> ---

I still very much disagree with your decision to close, to resolve this bug as
WONTFIX. This bug report has intrinsic merits, intrinsic accessibilty values,
worth. Ingo, I can not read these bugzilla bug reports pages and KDE Forums
pages if I set minimal font-size to 15px!

You close this bug report for reasons that have nothing to do with those
intrinsic merits and advantages. Your theme, maintenance horror, etc.. may
provide a perspective and reasons as to why kde.org webpages can not honor
*now* the 100% Easy-2-Read Std. But, by itself, this bug report is worth
implementing, worth achieving.

That is why your decision to close this bug seems to me to be mostly tactical
or purely contextual and is not about the goal and merits of this bug report.


Link update:
Truth & Consequences of Web Design: Font size
(percent encoding)


Is plasmaMenu.css one of the old themes you were talking about? Or is it a new

I have started to look at plasmaMenu.css and I see a lot of questionable code
and decisions.

at line 70 of
we can see the following:

.header .plasmamenu_box  div div div div ul li a,
.header .plasmamenu_box  div div div div ul li div div ul li a { 
    color: #444;
    text-shadow: #ffffff 1px 1px 1px;
    font-size: 13px;
    vertical-align: top;
    display: block;

Now, that means that the target HTML document of such rule has to have a depth
of 13 levels of containment hierarchy! ... but it could be more than 13 as the
selector uses the descendant selector 13 times!! So, if you have complex
layouts to do, try to reduce the number of containers.

Avoid the descendant selector

The descendant selector is the most expensive selector in CSS. It is dreadfully
expensive (...)
Writing Efficient CSS (a bit outdated but still relevant)

text-shadow: #ffffff 1px 1px 1px;
everywhere I saw text-shadow, box-shadow (and other typical purely cosmetic
properties, sometimes not even in PR states and using vendor prefixes), I
wondered and asked myself if such declarations were helping accessibility, text
legibility. Here, I would say it does not (a white shadow of 1px will never be
noticed by humans and all the time, 100% of the time) and, on other hand, it
does put a performance burden on the style module of browsers. Unneedlessly.

font-size: 13px;
I have not seen the pages where this rule is being applied. I would not be
surprised if such font-size: 13px; declaration was entirely unneeded because,
you see, font-size is inherited by default.

vertical-align: top;
display: block;
vertical-align property is one of the most misunderstood, most misused and most
abused property in stylesheets of webpages on the web. Here, no exception.
vertical-align does *not* apply to block boxes.
    Value:      baseline | sub | super | top | text-top | middle | bottom |
text-bottom | <percentage> | <length> | inherit
    Initial:      baseline
    Applies to:      inline-level and 'table-cell' elements 

You are receiving this mail because:
You are the assignee for the bug.

More information about the kde-www mailing list