Open
Bug 376246
Opened 18 years ago
Updated 2 years ago
Splitter don't work between grid columns
Categories
(Toolkit :: XUL Widgets, defect)
Tracking
()
NEW
People
(Reporter: daniel, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
(deleted),
application/vnd.mozilla.xul+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.9a3pre) Gecko/20070226
In older versions (Firefox 2.0) one could use a splitter between grid columns to size the columns. This doesn't work anymore using the current trunk.
Example:
<grid>
<columns>
<column />
<splitter collapse="before" resizeafter="farthest"/>
<column flex="1"/>
</columns>
<rows>
<row>
<label value="foo" />
<button label="bar" />
</row>
</rows>
</grid>
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Reporter | ||
Comment 1•18 years ago
|
||
Comment 2•18 years ago
|
||
Regression between 2006-01-25 17 and 2006-01-26 09:
http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2006-01-25+16%3A00&maxdate=2006-01-26+10%3A00
Bug 317375 ?
Reporter | ||
Comment 3•18 years ago
|
||
The row element is rendered on top of all other elements. This way, the splitter will not receive events.
Simple testcase:
<grid onmousedown="alert(event.target.nodeName)">
...
Reporter | ||
Comment 4•18 years ago
|
||
Strange things happen.
When using a <spacer> element it works.
Even when setting -moz-binding in it's style attribute.
<spacer style="-moz-binding:url(...)" />
When setting the same binding by class, it doesn't work and the object will be rendered behind the row.
<spacer class="usersplitter" />
usersplitter {
-moz-binding:url(...);
}
So the current workaround for me is to use a homemade splitter which will be referenced by an inline style binding.
Reporter | ||
Comment 5•18 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.9a6pre) Gecko/20070612
It's getting worse. With the latest XULRunner the second column in the testcase is not shown anymore. Probably because the element between the <column> tags is interpreted as a column as well.
Comment 6•18 years ago
|
||
The last comment is an unrelated bug, but may be a regression from bug 382899 or 382746.
Comment 7•18 years ago
|
||
(In reply to comment #6)
>The last comment is an unrelated bug, but may be a regression from bug 382899
>or 382746.
Bug 382746 changed the behaviour in that area, yes.
Reporter | ||
Comment 8•18 years ago
|
||
Should I file a new bug from comment #5?
Comment 9•18 years ago
|
||
(In reply to comment #8)
> Should I file a new bug from comment #5?
When in doubt, it's much better to err on the side of filing a bug. Duping bugs is cheap, not knowing about bugs can be costly :)
Reporter | ||
Comment 10•18 years ago
|
||
Additional bugreport about the missing second column created. see bug 384874
Reporter | ||
Comment 11•18 years ago
|
||
Something similar happens to a splitter between listcol elements. See bug 387529
Comment 12•18 years ago
|
||
(In reply to comment #11)
>Something similar happens to a splitter between listcol elements. See bug 387529
Listcols are basically column elements; bug 384874 should have fixed that too.
Reporter | ||
Comment 13•18 years ago
|
||
(In reply to comment #12)
> bug 384874 should have fixed that too.
Not really. Using the latest XULRunner nightly bug 384874 seems of course beeing fixed. Additional (non "column") elements are visible again. However, the splitter doesn't work when placed between any columns in a grid or list.
Comment 14•17 years ago
|
||
I confirm this bug still exists in rv:1.9b2pre Gecko/2007121017 Minefield/3.0b2pre. Both, on test case provided here, and on my own grid.
Updated•17 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 15•17 years ago
|
||
bug 268834 about ability to use splitter in listbox has been marked as wontifx. Since listbox implementation is based on grid then probably it makes sense to mention that bug here.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•