In Mozilla:

The problem we are trying to solve: We are using XSL/XML to generate
tables with text in the rows. The spacing is wider then when those same
exact tables are created in regular HTML. We figured out that this has
to do with Mozilla rendering the HTML page in quirks mode, versus the
XML/XSL page being rendered in strict mode.

I can find no way to enable quirks mode in Mozilla for XML/XSL
documents, since it does not appear possible to use the DOCTYPE tag. So
then the question is, how do we fix it the "right" way, within strict
mode, so that the table rows are spaced the way they are in quirks
mode?

This document makes reference to some CSS settings that can be used to
do it:

http://www.mozilla.org/docs/web-deve...q.html#margins

But it gives no specifics, and I can find nothing specifically
explaining the issue and how to fix it.

Any help is welcomed!

Thanks,
Thomas

It was somewhere outside Barstow when "Thomas" <tomwinzig@gmail.com>
wrote:
[color=blue]
>I can find no way to enable quirks mode in Mozilla for XML/XSL
>documents, since it does not appear possible to use the DOCTYPE tag.[/color]

What do you mean ? You can't generate it, or Mozilla doesn't use it?

Try something like this in the top of your XSLT

<xslt:output omit-xml-declaration="yes"
encoding="iso-8859-1"
indent="yes"
method="xml"
media-type="text/html"

doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"
/>

In article <1110412361.837594.167680@g14g2000cwa.googlegroups .com>,
"Thomas" <tomwinzig@gmail.com> wrote:
[color=blue]
> I can find no way to enable quirks mode in Mozilla for XML/XSL
> documents, since it does not appear possible to use the DOCTYPE tag.[/color]

Knowingly trying to activate the quirks mode is generally a bad
"solution".
[color=blue]
> This document makes reference to some CSS settings that can be used to
> do it:
>
> http://www.mozilla.org/docs/web-deve...q.html#margins
>
> But it gives no specifics, and I can find nothing specifically
> explaining the issue[/color]

I think the answer explains the issue. How could the answer be improved?
[color=blue]
> and how to fix it.[/color]

td>p:last-child {
margin-bottom: 0;
}
td>p:first-child {
margin-top: 0;
}

--
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Mozilla Web Author FAQ: http://mozilla.org/docs/web-developer/faq.html

Thomas wrote:[color=blue]
> I can find no way to enable quirks mode in Mozilla for XML/XSL
> documents, since it does not appear possible to use the DOCTYPE tag.[/color]

Firstly, it's not a DOCTYPE tag, it's a DOCTYPE declaration.
http://lachy.id.au/log/2004/12/html-tags

Secondly, quirks mode is an intentionally broken and evil parsing and
rendering mode designed to be compatible with non-conformant pages
designed for IE and NN 4.x browsers, so why would you want to enable it
in the first place? Please try to avoid it at all times by including an
HTML 4.01 Strict or Transitional DOCTYPE in all of your pages.
(Although, in Mozilla, transitional will trigger Almost Standards Mode
with the system identifier (the URI for loose.dtd) included, and quirks
mode without)

--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox

"Lachlan Hunt" <spam.my.gspot@gmail.com> wrote in message
news:422ff516$0$22862$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
[snip][color=blue]
> Secondly, quirks mode is an intentionally broken and evil parsing and
> rendering mode designed to be compatible with non-conformant pages
> designed for IE and NN 4.x browsers, so why would you want to enable it
> in the first place?[/color]
[snip]

Please explain how parsing can be "evil"?
Signed,
me

me wrote:[color=blue]
> "Lachlan Hunt" <spam.my.gspot@gmail.com> wrote in message
> news:422ff516$0$22862$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
> [snip]
>[color=green]
>>Secondly, quirks mode is an intentionally broken and evil parsing and
>>rendering mode...[/color]
>
> Please explain how parsing can be "evil"?[/color]

I didn't say that just parsing was evil, I said the "parsing ... mode".
The way documents are parsed in quirks mode is different from
standards mode, and it's these non-standard differences in both parsing
and rendering that are evil.

--
Lachlan Hunt
http://lachy.id.au/
http://GetFirefox.com/ Rediscover the Web
http://GetThunderbird.com/ Reclaim your Inbox

"Lachlan Hunt" <spam.my.gspot@gmail.com> wrote in message
news:4232b670$0$5501$5a62ac22@per-qv1-newsreader-01.iinet.net.au...[color=blue]
> me wrote:[color=green]
> > "Lachlan Hunt" <spam.my.gspot@gmail.com> wrote in message
> > news:422ff516$0$22862$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
> > [snip]
> >[color=darkred]
> >>Secondly, quirks mode is an intentionally broken and evil parsing and
> >>rendering mode...[/color]
> >
> > Please explain how parsing can be "evil"?[/color]
>
> I didn't say that just parsing was evil, I said the "parsing ... mode".
> The way documents are parsed in quirks mode is different from
> standards mode, and it's these non-standard differences in both parsing
> and rendering that are evil.
>
> --
> Lachlan Hunt[/color]

OK, why then do you call these "non-standard differences" evil?
Signed,
me