5551 - [PP][NATIVE-WIDGETS] List boxes: vertical scrollbar doesn't work

Status: VERIFIED WONTFIX

(Core :: Layout: Form Controls, defect, P3)

Description

[Pierre Saslawsky]

- go to a page that displays some listboxes (like http://bugzilla.mozilla.org/
query.cgi)
- click on a vertical scrollbar arrows to scroll the list
==> nothing happens


Notes:
It's a weird bug. In nsListBox::DispatchMouseEvent(), if we use LClick(), the
scrollbar never works but if we use TrackControl(), it works from time to time.
Go figure... Of course, we have to make LClick() work because TrackControl()
doesn't allow to pass the 'modifiers' and do some multi-selection in the list.

Assigned to myself.

Comment 1

[Pierre Saslawsky]

*** Bug 6734 has been marked as a duplicate of this bug. ***

Comment 2

[Pierre Saslawsky]

*** Bug 7234 has been marked as a duplicate of this bug. ***

Comment 3

[Pierre Saslawsky]

Moving to M15 all the bugs that have a dependancy on GFX widgets and/or Ender.

Comment 4

[Pierre Saslawsky]

*** Bug 7683 has been marked as a duplicate of this bug. ***

Comment 5

[leger]

Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze.  Widget Set component will be retired
shortly.

Comment 6

[Simon Fraser [no longer active]]

patrick, didn't you fix this?

Comment 7

[Pierre Saslawsky]

This bug was reported against native widgets.
Resolved as WontFix because the final product will use gfx widgets.

(Answering for Patrick to the question above: no, it's not fixed yet)

Comment 8

[Jesse Ruderman]

Instead of marking this as "resolved wontfix", why not mark it as depending on 
a "bug" to use gfx widgets instead of native widgets for that control?  That 
sounds a lot better than "won't fix" and shows up on the default query (new, 
reopened, assigned).

Comment 9

[Pierre Saslawsky]

It's precisely the reason why these bugs have been closed: we don't want them to 
appear in the default queries. Handling a large bug list (>100 bugs) makes a 
programmer's life miserable and we don't want to keep things that will not be 
fixed. Some people suggested that we should have marked them Later instead of 
WontFix. Maybe... But it's done and it's not worth spamming everybody by 
reopening the bugs and closing them under a different denomination. Native 
widgets are dead. The code is being removed.

Comment 10

[Jesse Ruderman]

Well.. the problem with just closing these bugs is that they don't show up on 
default queries, which can cause newer bug reporters to miss the bug and submit 
duplicates.

I think I'm seeing it from the bug hunter/reporter's point of view (unfixed 
bugs should show up) while you're seeing it from the bug fixer's point of view 
(bugs that won't be fixed as originally stated should not show up).  There is 
the [native-widgets] thing in the summary, and the nobody@* trick, but I still 
understand the problem of this type of bug cluttering lists.

Comment 11

[Pierre Saslawsky]

Still, we don't even want these to get into the way of anybody - coders or QA - 
because native widgets are gone. They have been removed several months ago and 
nobody reports duplicates anymore.

However you are right for other kinds of bugs that have been marked Later or 
WontFix instead of going to [e-mail]. Note that the 'nobody' trick is 
recent (about 2 months) and many latered bugs were marked so before the trick 
existed.

Comment 12

[bsharma]

Updating QA contact.

Comment 13

[Vladimir Ermakov]

verifying