190025 - First anchor in a list displays incorrectly (smaller font, with carriage return ahead of it)

Status: RESOLVED INVALID

(Tech Evangelism Graveyard :: English US, defect)

Description

[Steve Magruder]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Given the following CSS:

ul { margin-left: 0px; padding-left: 12px; margin-top: 0px; margin-bottom: 
8px; }
li { color: purple; font-size: 13px; text-align: justify; margin-bottom: 8px; 
line-height: 130%; margin-left: 4px; }
a { color: #990000; text-decoration: none; } 

and given this HTML:

<ul>
<li><b>Primizie Pizza, Pasta and Philly Steaks on Theatre Square</b></li>
<li><a href="http://www.hubbuch.com/main.html" target="_blank"><b>Hubbuch & 
Company Architecture & Interior Design</b></a></li>
</ul>

The problem listed in the summary occurs.  If a second anchor is added as a 
list item, it gets displayed as expected.  This problem also occurs in 1.3a.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Attachment: testcase based on that description

Comment 2

[Boris Zbarsky [:bzbarsky]]

Steve, that testcase worksforme with linux build 2003-01-18-22.  Are you seeing
the problem with it?  If not, please attach a testcase that _does_ show the problem.

Comment 3

[Steve Magruder]

Check out http://www.stevemagruder.com/artzmo/?section=projects

Under the "Sponsors" header (2/3 down the page), the problem will show itself.  
I'm sorry, but I'm unable to narrow down a test case.

Comment 4

[Boris Zbarsky [:bzbarsky]]

The site contains nested <a> tags; the inner one closes out the outer one and
also the paragraph and <ul> that were started inside it.  The rendering is
correct given that markup....

Comment 5

[Steve Magruder]

Well, actually, no, there aren't nested anchors on that page.  But there is an
anchor that reads "<a name="sponsors"/>" (closes itself) ahead of the list with
the problem.

Comment 6

[Steve Magruder]

And why was this changed to "Tech Evangelism" when this is clearly a Browser
issue? (whether it's a bug or not)

Comment 7

[Boris Zbarsky [:bzbarsky]]

<a/> is not a closed anchor in an HTML document.  It _is_ in an XHTML document,
but this document is sent as text/html.  Which means "parse this as HTML, not
XHTML, please".  Further, the XHTML specification states that the only way to
send an XHTML document as text/html is if it complies with Appendix C of that
specification. Using miminized forms for non-EMPTY elements violates Appendix C.

This is Tech Evangelism because it's not a browser bug.  The other option is to
mark it invalid, of course.

Comment 8

[Steve Magruder]

Er, sorry, but this is an XHTML page we're dealing with here.

Comment 9

[Boris Zbarsky [:bzbarsky]]

Yes.  But the site is requesting that we treat it as HTML, by sending it with
the HTML MIME type instead of the XHTML one.  See
http://www.hixie.ch/advocacy/xhtml for more information on that...

Also, I repeat that this document is violating appendix C of the XHTML spec, so
sending it as text/html is not allowed at all, per that spec.

If you want us to treat the content as XHTML, you need to send it as XHTML
(after all, if you sent it as text/plain, would you mind us rendering it as
plaintext?).  

Comment 10

[Steve Magruder]

OK... I'll modify the site and see what happens.  By the way, Opera 6.0x and IE
6 render it just fine--they probably look at other indicators to see if it's
XHTML, like the info in the doctype.  But, yes, I know Mozilla is trying to be
absotootly perfect on standards, so I guess I understand.  :)

Comment 11

[Steve Magruder]

Tested with "application/xhtml+xml" and "text/xml" and "text/xhtml"... still 
fails.  Is it a bug yet?  If it's deemed to be "tech evangelism", I'll just 
write a workaround and assume that Mozilla is broken with XHTML.

Comment 12

[Boris Zbarsky [:bzbarsky]]

Steve, I just tried saving that page as test.xhtml, adding the xmlns decl on the
<html> element so that it's actually XHTML, and loading it in Mozilla.  The
problem you point to with the linebreak disappeared, as it should.  Are you sure
you tested the application/xhtml+xml and text/xml MIME types?  And cleared the
cache before loading the page?

Comment 13

[Steve Magruder]

What's the "xmlns decl"?  I think I did the other things, but I'll double-check
about clearing the cache.

Comment 14

[Boris Zbarsky [:bzbarsky]]

> What's the "xmlns decl"?

xmlns="http://www.w3.org/1999/xhtml" on the root element.  If you did _not_ add
that and got the page to look anything like a webpage, it was not being loaded
as XHTML....

Comment 15

[Steve Magruder]

Doesn't appear to be a problem any longer.  Please close.

Comment 16

[Boris Zbarsky [:bzbarsky]]

ok