Re: [whatwg] Default (informal) Style Sheet

At 12:05 +0200 UTC, on 2007-04-06, Alfonso Martínez de Lizarrondo wrote:

> 2007/4/6, Sander Tekelenburg <<mailto:st@isoc.nl>st@isoc.nl>:

[...]

['CSS zapper'
<http://webrepair.org/02strategy/02certification/01requirements.php#req26>]

> That idea is basically a way for web authors to override the UA defaults
>and this way overcome the current differences in those defaults

Right.

>, but in no
>way it does assure that the users will get their expected rendering because
>the user could have specified a User Stylesheet.

By what logic would a user define User CSS  and not expect that to affect the
rendering? (And, as I said earlier, a specced default presentation doesn't
give that ensurance either.)

>Having the UA use all of them a common stylesheet will get the same effect
>that specifying a "CSS zapper", but most important: it will be easier to
>control the rendering if all the behavior is specified in a css file used by
>the browser.

Control by whom? (I ask specifically, because on the WHATWG mailing list now
and then people seem to think that control should be moved more from users to
authors, which I thoroughly disagree with.)

Anyway, you seem to be talking here about the problem that some UAs use
styling that cannot be targeted through CSS. As far as I can see that's a
different issue altogether. My initial take on that would be that users can
vote with their wallets.

> What I have in mind right now: trying to style a <br> (br:before {content:
>"\B6 ";}) it's impossible for example in Mozilla because it uses some magic
>in the rendering. If the rendering is only controlled by some CSS rules then
>it's possible for a web author to override them

I'd have to think about it some more, but I might well agree with the CSS
spec saying that UAs should privide users with a means to change
presentation. (If it doesn't say so already. I haven't checked.)

>, and having all the UA use
>the same defaults would be a good thing.

I don't see how, from what you said, you reach that conclusion.


-- 
Sander Tekelenburg
The Web Repair Initiative: <http://webrepair.org/>

Received on Saturday, 7 April 2007 13:22:14 UTC