If you put a <xul:spring> element (as a spacer) before an <html:select> element, the <html:select> element will wrap to the next line. I can't check in my example just yet because the tree is closed. I'll update this bug when I've checked in.
Spring isn't a real XUL tag. It's just a made up tag with display type of block that can be used with boxes. Because the spring is a block element, if it's placed in normal HTML flow, there will be a break after it. You have to put it inside a horizontal box in order to get it to behave like a horizontal spring. If you don't care about boxes and just want want to insert some space, you can always just use the HTML SPACER tag.
Yeah, i just realized that springs weren't real, that's pretty cool. So all block elements cause a wrap when placed [near, around?] html elements? The wierd thing is that this doesn't occur if the widget following the <spring> is a <html:input type="text"> Maybe that's the bug?
Weird. I don't know much about this actually. It doesn't sound like a XUL problem to me. More like a general layout question. :)
Assignee: hyatt → rickg
Status: ASSIGNED → NEW
Summary: <spring> then <html:select> causes wierd wrapping → <spring/> then <html:select> causes wierd wrapping - different behavior than <spring/><html:input type="text>
Ah, ok I'm assigning to rickg to take a look at it. Rick, to summarize: If you insert a <spring/> tag (which is a block element, according to hyatt) followed by a <html:select> tag, the <html:select> tag wraps. If you follow the <spring/> tag by a <html:input type="text"> it does not wrap. I don't know what the correct behavior is, but it should be consistent, it's making my dialogs look funny. :)
Can you please be more specific? What is wrapping here? How do I see recreate the test?
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
Doh, I feel like a dope. It turned out that the line with the <html:select> was enclosed by <html:div> and the line with by <html:input> was not. So basically: Don't use block layout elements inside <html:..> tags.
You need to log in before you can comment on or make changes to this bug.