 |
|
|
Dan Morrison wrote:
>Michael Beddow wrote:
>> But in html, the new ol block
>> element
>> implicitly closes the p element, so that the browser
>> in effect rewrites to
>>
>> <p class="myclass">
>> Text before list
>> </p> <<=============== !!!!
>I don't get it. This result is not a product of an XSL processor, right?
>The view-source in the browser does not actually show the (invalid) html
>you illustrated?
>It just displays 'as if' there was a </p> there, if I understand your
>use of the word 'effectively'.
>
>I'm guessing your problem is a layout/browser one, rather than an
>XSL/Syntax one.
>
>So which is the browser?
>Netscape, which has a habit of dropping out of styles at every level of
>nesting it can, or IE, which 'effectively' throws <p>s around everything
>it finds?
<snip/>
I think Dan got it right.
I'd try changing the <p class=...> to <div class=...> and close the div
where the last </p> was. [untested]
Rick Suiter
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
