Closed
Bug 1328067
Opened 9 years ago
Closed 8 years ago
[e10s] <select> is limited by content area
Categories
(Core :: Layout: Form Controls, defect, P2)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: arni2033, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
70.52 KB,
image/png
|
Details |
>>> My Info: Win7_64, Nightly 52, 32bit, ID 20161001030430 (2016-10-01)
STR_1:
1. Open url data:text/html,<select><option>1<option>2</select><style>select{position:fixed;bottom:0}
2. Resize window so that there was enough space between the window and the bottom of the screen
3. Click on <select>
AR: List of options appears above <select>, i.e. it's limited to content area
ER: Either X or Y
X) e10s <select> shouldn't be limited to content area
Y) non-e10s <select> (e.g. in devtools and "Share this page" panel) should also be limited
Blocks:
1276976
This is regression from bug 1276976. Regression range:
> https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7fc8f70a567d4492607906d40532ef4a7124c8f5&tochange=2ce7e838634b204dcec9487452cabc20d709c4d6
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Blocks: e10s-select
Status: UNCONFIRMED → NEW
Has Regression Range: --- → yes
Has STR: --- → yes
Ever confirmed: true
Hardware: Unspecified → All
Version: Trunk → 50 Branch
Comment 1•8 years ago
|
||
[Triage] it's easy to imagine that this issue could be hit quite easily if the option list is longer. Would be good to fix this soon-ish, P2.
Priority: -- → P2
Comment 2•8 years ago
|
||
Screenshot of clipped dropdown list.
Comment 3•8 years ago
|
||
Blake, can you CC me in bug 1276976 or share reason behind its decision to limit <select> to content area?
Bug 1276976 results in this bug but owner Neil seems unavailable. I'd like to understand reason behind bug 1276976 to see whether/how we should solve this bug.
Flags: needinfo?(mrbkap)
Updated•8 years ago
|
Flags: needinfo?(mrbkap)
Updated•8 years ago
|
Comment 4•8 years ago
|
||
(In reply to Hsin-Yi Tsai (55 Regression Engineering support) [:hsinyi] from comment #1)
> [Triage] it's easy to imagine that this issue could be hit quite easily if
> the option list is longer. Would be good to fix this soon-ish, P2.
You see as much of the select dropdown as the content area allows, which seems quite reasonable. If the content area is so small as to now allow even a single option in the select area to show you won't see anything, which is unfortunate, but the content area to begin with is basically unusable. If the content area is a reasonable size that people actually use the select dropdown is perfectly usable. If there are cases where the content area is a realistic size that people actually use and the select dropdown is display sub-optimally then we'd want to fix, otherwise no.
Comment 5•8 years ago
|
||
(In reply to Timothy Nikkel (:tnikkel) from comment #4)
> (In reply to Hsin-Yi Tsai (55 Regression Engineering support) [:hsinyi] from
> comment #1)
> > [Triage] it's easy to imagine that this issue could be hit quite easily if
> > the option list is longer. Would be good to fix this soon-ish, P2.
>
> You see as much of the select dropdown as the content area allows, which
> seems quite reasonable. If the content area is so small as to now allow even
> a single option in the select area to show you won't see anything, which is
> unfortunate, but the content area to begin with is basically unusable. If
> the content area is a reasonable size that people actually use the select
> dropdown is perfectly usable. If there are cases where the content area is a
> realistic size that people actually use and the select dropdown is display
> sub-optimally then we'd want to fix, otherwise no.
Thanks :tnikkel for the additional remarks that sound reasonable.
Comment 6•8 years ago
|
||
Resolve as WONTFIX per comment 4.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•