Open
Bug 293200
Opened 21 years ago
Updated 3 years ago
RDF generated listboxes don't sort if the datasource is added after generation
Categories
(Core :: XUL, defect)
Tracking
()
NEW
People
(Reporter: mossop, Unassigned)
References
()
Details
(Keywords: helpwanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050506 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050506 Firefox/1.0+
If you set the listbox datasource using the datasources attribute then sorting
with sortResource and sortDirection works fine. However if you user "rdf:null"
as the datasources attribute and set the datasource afterwards using
AddDataSource programmatically, the same data is displayed but it is not sorted.
Reproducible: Always
Steps to Reproduce:
| Reporter | ||
Comment 1•21 years ago
|
||
I haven't managed to make a reduced testcase for the problem I'm seeing yet, but
in my attempt I came across this problem with listbox sorting that is possibly
related/caused by the same thing.
If you go to the url you will see a listbox. The first time you visit the
listbox is not sorted. Clicking refresh sorts it. Then you have to restart
firefox before it will appear unsorted again.
Updated•21 years ago
|
Keywords: helpwanted,
qawanted
Comment 2•21 years ago
|
||
I suspect synch vs asynch foo and observing changes in datasources.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•19 years ago
|
||
Need an updated testcase here. The link isn't working.
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.widgets
Comment 4•12 years ago
|
||
Is this still an issue with current Firefox build? If so, please specify what is needed from QA here. An updated URL would also help speed things up.
Flags: needinfo?(dtownsend+bugmail)
| Reporter | ||
Comment 5•12 years ago
|
||
I have no idea what QA is needed here nor do I have the code anymore to see if it still fails
Flags: needinfo?(dtownsend+bugmail)
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•