Open
Bug 1330163
Opened 9 years ago
Updated 3 years ago
[e10s] should focus on the disabled option with pre-selected for <select>
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: over68, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
166 bytes,
text/html
|
Details |
Steps to reproduce:
1. Open testcase.
2. Open the <select> element.
Expected results:
should focus on the disabled option with pre-selected for <select>.
Screenshot https://dl.dropboxusercontent.com/u/95157096/85f61cf7/xva6d5mavt.png
I think this is related to bug 1091592.
https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=f03e2740d604d339ed553dad62a3fc54c317f8fa&tochange=83461556cda59e8bcd54f09b9263e3202ce01dc2
Blocks: 1091592, e10s-select
Comment 2•8 years ago
|
||
Win7 behaviour is inconsistent b/w e10s (no focus) and non-e10s (with focus). Chrome and Edge on Win7 behave the same as our non-e10s Win7, i.e. focusing on the disabled pre-selected option.
Firefox behaves consistently b/w e10s and non-e10s, i.e. both are focusing on the disabled pre-selected option. However, Chrome and Safari on OSX behaves differently here, i.e. no focusing.
I guess we should think about what's our preferred behaviour cross platforms.
Priority: -- → P3
Comment 3•8 years ago
|
||
(In reply to Hsin-Yi Tsai (Firefox55 Regression Engineering secondary) [:hsinyi] from comment #2)
> Win7 behaviour is inconsistent b/w e10s (no focus) and non-e10s (with
> focus). Chrome and Edge on Win7 behave the same as our non-e10s Win7, i.e.
> focusing on the disabled pre-selected option.
>
> Firefox behaves consistently b/w e10s and non-e10s,
Apparently I missed some words. The above sentence should be: Firefox on OSX behaves consistently ...
> i.e. both are focusing
> on the disabled pre-selected option. However, Chrome and Safari on OSX
> behaves differently here, i.e. no focusing.
>
> I guess we should think about what's our preferred behaviour cross platforms.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•