Closed
Bug 1309941
Opened 8 years ago
Closed 8 years ago
The ContentSelectDropdown popup should open with the selected item appearing on top of the 'select' element
Categories
(Core :: Layout: Form Controls, defect)
Core
Layout: Form Controls
Tracking
()
RESOLVED
DUPLICATE
of bug 430745
People
(Reporter: jaws, Assigned: beachjar, Mentored)
Details
Right now the popup appears either above or below the <select> element, regardless of which is the selected option. When the menu is opened, the menu appears like so (animation from left to right), with a list of fruits that has Apple selected: [ Apple |v] [ Orange ] [-Apple--] [ Banana ] We should position the popup so that the option that was selected prior to opening appears on top of the select group-button. [ Apple |v] When the menu is opened, the menu should appear like so (animation from left to right): [ Orange ] [ Apple |v] [-Apple--] [ Banana ] (where -- means that the item is selected)
Comment 1•8 years ago
|
||
What you suggest is clearly the wrong behavior on Windows and GTK. But yes, we do want that behavior on OSX.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•8 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #1) > What you suggest is clearly the wrong behavior on Windows and GTK. > But yes, we do want that behavior on OSX. > > *** This bug has been marked as a duplicate of bug 430745 *** I think it is a stretch to say this is "clearly wrong behavior on Windows". More discussion here may be necessary as Edge now does this same behavior on Windows, so this would match Edge-compat there.
Flags: needinfo?(mats)
Comment 3•8 years ago
|
||
Interesting, I wasn't aware Edge was doing it this way. Fair enough, we might want to do this on Windows too then. My point is, there's a fair amount of platform specific behavior in form controls that we (until now at least) have considered important enough to implement, to avoid alienating users who often have an expectation of those behaviors in their "muscle memory". Have our reasoning about this changed recently? I haven't seen any discussion on m.d.platform or elsewhere about it. I certainly think it's a major change that should be discussed more widely if we're going to ditch that approach and implement a "common denominator" behavior across platforms.
Flags: needinfo?(mats)
Reporter | ||
Comment 4•8 years ago
|
||
Hey Philipp / Stephen, Can you comment here as to if we should make this change for Windows? Bug 430745 is already on file for doing this on OSX, which is where we could do the work for now and expand it to Windows if we feel that it is a good fit there as well.
Flags: needinfo?(shorlander)
Flags: needinfo?(philipp)
Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(shorlander)
Flags: needinfo?(philipp)
You need to log in
before you can comment on or make changes to this bug.
Description
•