listbox fires 'select' event even if 'suppressonselect' attribute is specified when removing a selected listitem from the document

NEW
Unassigned

Status

()

Core
XUL
12 years ago
10 years ago

People

(Reporter: surkov, Unassigned)

Tracking

({testcase})

Trunk
testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

720 bytes, application/vnd.mozilla.xul+xml
Details
(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4

I have <listbox suppressonselect='true'/>. Listbox have selected child. When I
remove all childs of listbox then 'select' event is fired. As usually select
event is fired by _fireOnSelect() method of listbox binding. But I guess
'select' event is fired by someone else when items are removed. I think it would
be more gracefully if 'select' event will be fired by _fireOnSelect() method
only. If such way isn't acceptable then event fierer should look at
'suppressonselet' attribute.

Reproducible: Always
(Reporter)

Comment 1

12 years ago
Created attachment 199282 [details]
testcase

Comment 2

12 years ago
At all related to bug 135172?
(Reporter)

Comment 3

12 years ago
(In reply to comment #2)
> At all related to bug 135172?

I guess, no

Comment 4

12 years ago
The event is fired by nsXULElement::RemoveChildAt
http://lxr.mozilla.org/seamonkey/source/content/xul/content/src/nsXULElement.cpp#1114
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: testcase
OS: Windows 2000 → All
Hardware: PC → All
Summary: listbox fired 'select' event even if 'suppressonselect' attribute is specified → listbox fires 'select' event even if 'suppressonselect' attribute is specified when removing a selected listitem from the document

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.