XUL content sink eats too much whitespace

NEW
Unassigned

Status

()

defect
18 years ago
9 years ago

People

(Reporter: hyatt, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
mozilla1.2alpha
x86
Windows 2000
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [xul1.0-widgets-button], )

Attachments

(1 attachment)

Reporter

Description

18 years ago
Go to the above URL using a current trunk build of Mozilla.  The second button 
shown is a multiline button that contains some markup.  The word "markup"
is bright red.

Even though there is ample whitespace in the markup, all of the spaces are 
being eaten, both those before and after the <html:span> that introduces the 
red color.

The XML content sink does this correctly, and you can verify this by visiting

http://www.mozilla.org/projects/xul/tests/buttons.xml

The above XML file is exactly the same as the XUL file, but it renders 
correctly.

Fixing this could result in many more objects in the content model, I suppose, 
but the fact that the whitespace is stripped out does not seem correct to me.
Reporter

Updated

18 years ago
Blocks: 70753
Whiteboard: [xul1.0-widgets-button]
Reporter

Comment 1

18 years ago
An idea might be to just make the content sink smart about the known block 
tags while continuing to strip whitespace from all the other XUL tags.  

The block tags in XUL include <html> (now deprecated but you could support it 
anyway), <description>, and <label>.  Anything in the HTML namespace could 
also be special-cased.
Reporter

Comment 2

18 years ago
Ok, mine.
Assignee: waterson → hyatt
Reporter

Updated

18 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0

Comment 3

18 years ago
Using 2001101008 I noticed that the when the button wraps, the buttons looks
like this:

A long label that contains
markup and that wraps to
multiple lines.

However, what I noticed was that there is alot of extra spacing within the
button on the right side.  I have made an attachment showing this effect.  I
don't really think this seems correct.

Comment 4

18 years ago

Comment 5

18 years ago
->098
Target Milestone: mozilla1.0 → mozilla0.9.8
Reporter

Updated

18 years ago
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Reporter

Updated

18 years ago
Target Milestone: mozilla0.9.9 → mozilla1.2

Updated

18 years ago
Keywords: mozilla1.0+

Comment 6

18 years ago
Moving non nsbeta1+ XUL 1.0 bugs to mozilla1.2

Updated

18 years ago
No longer blocks: 70753

Comment 7

18 years ago
not needed for 1.0. mozilla1.0-
Keywords: mozilla1.0+mozilla1.0-
*** Bug 145921 has been marked as a duplicate of this bug. ***

Updated

17 years ago
Blocks: 145921

Updated

11 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets

Updated

10 years ago
Assignee: hyatt → nobody

Updated

9 years ago
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.