Hi,

You'll excuse me if this has been answered before but I must have
missed it on my travels:

Is there a definitive style sheet with includes a definition for
everything that a particular browser sets to not-null/zero/inherit?


Given all the usual pixel adjustments here, browser specific bug
fixes there and that, by definition, all browsers set some defaults
is there not any mileage in having a complete stylesheet defining all
the settings from which you can work without tripping over an obscure
:first-child padding when you least expect it?

Feel free to say I'm asking a dumb question, but do at least say why
:-)

Cheers,

Ian

Ian Fitchet wrote:[color=blue]
>
> Is there a definitive style sheet with includes a definition for
> everything that a particular browser sets to not-null/zero/inherit?[/color]

Uh... no. I'm not sure why you would expect this to be the case. Do
you think that:

(a) every browser is equipped with the same CSS rendering engine (if all
browsers came from one company I imagine this "could" be a possibility)

OR

(b) that the CSS specs are so crystal clear and that CSS is so simple
that every browser is surely to get it right (and that every time a
browser vendor finds - better yet is informed of - a CSS bug that they
will care to fix it)

[color=blue]
> Given all the usual pixel adjustments here, browser specific bug
> fixes there and that, by definition, all browsers set some defaults
> is there not any mileage in having a complete stylesheet defining all
> the settings from which you can work without tripping over an obscure
> :first-child padding when you least expect it?[/color]

In a word - NO.
[color=blue]
> Feel free to say I'm asking a dumb question, but do at least say why
> :-)[/color]

I don't think any question is dumb ;-)

What you need to understand is that CSS spec interpretation coupled with
multiple browser vendors (doing the interpretation) doesn't boil down to
a simple 2 + 2 = 4 math problem (and that's assuming we don't even start
to consider bugs or other factors).

--Nikolaos

Nikolaos Giannopoulos <nikolaos@solmar.ca> writes:
[color=blue]
> Ian Fitchet wrote:[color=green]
>> Is there a definitive style sheet with includes a definition for
>> everything that a particular browser sets to not-null/zero/inherit?[/color]
>
> Uh... no. I'm not sure why you would expect this to be the case. Do
> you think that:
>
> (a) every browser is equipped with the same CSS rendering engine (if
> all browsers came from one company I imagine this "could" be a
> possibility)
>
> OR
>
> (b) that the CSS specs are so crystal clear and that CSS is so simple
> that every browser is surely to get it right (and that every time a
> browser vendor finds - better yet is informed of - a CSS bug that they
> will care to fix it)[/color]

I don't think either and I didn't mean to suggest either.

Another way: given browser X, version Y is there a stylesheet Z which
if applied replicates the default style settings?

As there is a drive towards CSS conformant browsers in my naivety I
would have thought we could entertain the possibility. Thereafter,
with the set of Z, developers could see which, if any, settings are
likely to cause them problems and better be able to see how and why
certain presentation is effected.

Cheers,

Ian

Ian Fitchet wrote:[color=blue]
> Another way: given browser X, version Y is there a stylesheet Z which
> if applied replicates the default style settings?[/color]

There are CSS files in Mozilla installations containing style
declarations for many elements.
--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)

"Ian Fitchet" <idf@lunanbay.LESS-SPAM.com> wrote in message
news:x7k77rjoma.fsf@s59br.home.lunanbay.com...[color=blue]
> Nikolaos Giannopoulos <nikolaos@solmar.ca> writes:
>[color=green]
> > Ian Fitchet wrote:[color=darkred]
> >> Is there a definitive style sheet with includes a definition for
> >> everything that a particular browser sets to not-null/zero/inherit?[/color]
> >
> > Uh... no. I'm not sure why you would expect this to be the case. Do
> > you think that:
> >
> > (a) every browser is equipped with the same CSS rendering engine (if
> > all browsers came from one company I imagine this "could" be a
> > possibility)
> >
> > OR
> >
> > (b) that the CSS specs are so crystal clear and that CSS is so simple
> > that every browser is surely to get it right (and that every time a
> > browser vendor finds - better yet is informed of - a CSS bug that they
> > will care to fix it)[/color]
>
> I don't think either and I didn't mean to suggest either.
>
> Another way: given browser X, version Y is there a stylesheet Z which
> if applied replicates the default style settings?[/color]


I think this is a great question. However, as I just recently learned in
the "Font sizes - Best practice... px vs. em" thread, you probably can't do
this without losing some accessibility. That is, browser X might use a
different font size than browser Y, and the end user's settings are
dependent upon that.

But I still think it's a valid question. I don't think there currently
exists a stylesheet that forces browsers to act the same (at least I haven't
seen one). If you were going to write one, though, the best approach would
probably be to write it for an XML document (giving your XML elements the
same names as HTML elements). That way you are not using any of the
built-in styles of HTML. This of course forces you to specify EVERY detail
(like display:block). The stylesheet would be pretty huge I would imagine.

Regards,
Peter


[color=blue]
>
> As there is a drive towards CSS conformant browsers in my naivety I
> would have thought we could entertain the possibility. Thereafter,
> with the set of Z, developers could see which, if any, settings are
> likely to cause them problems and better be able to see how and why
> certain presentation is effected.
>
> Cheers,
>
> Ian[/color]

Peter Foti wrote:[color=blue]
> "Ian Fitchet" <idf@lunanbay.LESS-SPAM.com> wrote in message
> news:x7k77rjoma.fsf@s59br.home.lunanbay.com...
>[color=green]
>> I don't think either and I didn't mean to suggest either.
>>
>> Another way: given browser X, version Y is there a stylesheet Z which
>> if applied replicates the default style settings?[/color][/color]

<snip>
[color=blue]
> But I still think it's a valid question. I don't think there currently
> exists a stylesheet that forces browsers to act the same (at least I haven't
> seen one). If you were going to write one, though, the best approach would
> probably be to write it for an XML document (giving your XML elements the
> same names as HTML elements).[/color]

Do you really believe what you are suggesting or are you just making
this up because honestly I have to wonder.

Do you honestly believe that you can make *all* browsers behave the same
way for *all* CSS rules by simply creating some unified style sheet.

You'll will discover - as I imagine you haven't yet - that this is an
impossibility and I could give you numerous cases wherein this is flat
out impossible and you simply have to live with the nuances or change
your design accordingly (if you can that is).

BTW what does XML have to do with solving this problem? Is that the
unifying part - the magic ingredient that solves the problem?

[color=blue]
> That way you are not using any of the
> built-in styles of HTML. This of course forces you to specify EVERY detail
> (like display:block). The stylesheet would be pretty huge I would imagine.[/color]

Even if you could specify every detail what makes you believe this is
even possible. I'll argue that no matter how large your style sheet
that this is not going to work and you would probably be surprised that
it would break down a lot sooner than you think i.e. I don't think you
would get very far with this without realizing it is fruitless.

If you don't believe me then what can I say - give it a try ;-)

--Nikolaos

In article <x7oex3k0as.fsf@s59br.home.lunanbay.com>,
Ian Fitchet <idf@lunanbay.LESS-SPAM.com> wrote:[color=blue]
>
> You'll excuse me if this has been answered before but I must have
> missed it on my travels:
>
> Is there a definitive style sheet with includes a definition for
> everything that a particular browser sets to not-null/zero/inherit?
>[/color]

Not quite what you asked. But do you mean something like:

http://www.w3.org/TR/2003/WD-CSS21-20030915/sample.html

nhoJ
--
John P Baker

"Nikolaos Giannopoulos" <nikolaos@solmar.ca> wrote in message
news:CM6dncLYI9EcCuSiXTWJiw@magma.ca...[color=blue]
> Peter Foti wrote:[color=green]
> > "Ian Fitchet" <idf@lunanbay.LESS-SPAM.com> wrote in message
> > news:x7k77rjoma.fsf@s59br.home.lunanbay.com...
> >[color=darkred]
> >> I don't think either and I didn't mean to suggest either.
> >>
> >> Another way: given browser X, version Y is there a stylesheet Z which
> >> if applied replicates the default style settings?[/color][/color]
>
> <snip>
>[color=green]
> > But I still think it's a valid question. I don't think there currently
> > exists a stylesheet that forces browsers to act the same (at least I[/color][/color]
haven't[color=blue][color=green]
> > seen one). If you were going to write one, though, the best approach[/color][/color]
would[color=blue][color=green]
> > probably be to write it for an XML document (giving your XML elements[/color][/color]
the[color=blue][color=green]
> > same names as HTML elements).[/color]
>
> Do you really believe what you are suggesting or are you just making
> this up because honestly I have to wonder.[/color]


Please note that I said "the best approach". I never said it was a definate
solution.

[color=blue]
> Do you honestly believe that you can make *all* browsers behave the same
> way for *all* CSS rules by simply creating some unified style sheet.[/color]


While it would be nice, I suspect that browser bugs would make this
impossible.

[color=blue]
> You'll will discover - as I imagine you haven't yet - that this is an
> impossibility and I could give you numerous cases wherein this is flat
> out impossible and you simply have to live with the nuances or change
> your design accordingly (if you can that is).
>
> BTW what does XML have to do with solving this problem? Is that the
> unifying part - the magic ingredient that solves the problem?[/color]


Because UAs have default ways to render HTML elements (H1 is large and bold
for example), the only way to start from scratch is to use XML, where there
is no such default rendering for these elements.

[color=blue][color=green]
> > That way you are not using any of the
> > built-in styles of HTML. This of course forces you to specify EVERY[/color][/color]
detail[color=blue][color=green]
> > (like display:block). The stylesheet would be pretty huge I would[/color][/color]
imagine.[color=blue]
>
> Even if you could specify every detail what makes you believe this is
> even possible. I'll argue that no matter how large your style sheet
> that this is not going to work and you would probably be surprised that
> it would break down a lot sooner than you think i.e. I don't think you
> would get very far with this without realizing it is fruitless.[/color]


Perhaps.

[color=blue]
> If you don't believe me then what can I say - give it a try ;-)[/color]

You first. :)

-Pete

[color=blue]
>
> --Nikolaos
>[/color]

Johannes Koch <koch@w3development.de> writes:
[color=blue]
> There are CSS files in Mozilla installations containing style
> declarations for many elements.[/color]

ccjpb@shark.cse.bris.ac.uk (JP. Baker) writes:
[color=blue]
> http://www.w3.org/TR/2003/WD-CSS21-20030915/sample.html[/color]


Thank you, the two "John"s for providing examples. I accept that no
UA may actually follow these but they give a good starter for ten for
anyone wanting to understand a core stylesheet.

For example, you might note that for many things margin is defined in
terms of ems (1.17em, 0.83em etc.) except that some things define
margin in px (eg. blockquote 40px).


The reason for my question is that you can obviously extend such
simple introspection to work out why, as I have found, that some but
not all <input> within a <form> have a different background colour in
IE6 build XYZ to the one I choose. I might also have trivially seen
that <input> in IE6 ignores whatever parent font-size I have set and
I have to set one for it explicitly.

I don't want to have all browsers look the same (sorry, Peter!) but
I'd like to know what funny defaults I'm up against across my
favourite browser set. I don't think that's an unreasonable question
to ask (and orthogonal to the question many people seem to think I've
asked) and I'm surprised that so many eminent authors in the land of
CSS haven't addressed it explicitly rather than maintain browser
specific fixes which attempt to answer the same question but from the
other end erring on the side of incompleteness.

Cheers,

Ian