Closed
Bug 904656
Opened 12 years ago
Closed 9 years ago
[responsive mode] Select element down arrow not visible
Categories
(DevTools :: Responsive Design Mode, defect, P2)
Tracking
(firefox22 affected, firefox23 affected, firefox24 affected, firefox25 affected, firefox26 affected)
RESOLVED
DUPLICATE
of bug 1276629
People
(Reporter: andre42m, Unassigned)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130730113002
Steps to reproduce:
1. Open a page that has a select(this bug report for example)
2. Open responsive mode(Ctrl+Shift+M)
Actual results:
The down arrow of the select elements are hidden.
Expected results:
The down arrow of the select elements should stay as they were before entering the responsive mode.
Reporter | ||
Updated•12 years ago
|
Component: Untriaged → Developer Tools: Responsive Mode
![]() |
||
Comment 1•12 years ago
|
||
Regression window(fx)
Good:
http://hg.mozilla.org/integration/fx-team/rev/6b087f0ef2cb
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20130312 Firefox/22.0 ID:20130312040207
Bad:
http://hg.mozilla.org/integration/fx-team/rev/a9d191946bb2
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20130313 Firefox/22.0 ID:20130313040209
Pushlog:
http://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=6b087f0ef2cb&tochange=a9d191946bb2
Regressed by:
3a6837d404c Paul Rouget — Bug 850480 - [responsive mode] Re-introduce mobile scrollbars. r=vporof Bug 850480 - [responsive mode] Re-introduce mobile scrollbars. r=vporof
Blocks: 850480
Status: UNCONFIRMED → NEW
status-firefox22:
--- → affected
status-firefox23:
--- → affected
tracking-firefox24:
--- → ?
tracking-firefox25:
--- → ?
tracking-firefox26:
--- → ?
Ever confirmed: true
Keywords: regression
Version: 23 Branch → 22 Branch
Comment 2•12 years ago
|
||
Not a blocker but will take a low risk uplift.
Also passing this onto paul given this may be a fallout from 850480
Assignee: nobody → paul
status-firefox24:
--- → affected
status-firefox25:
--- → affected
status-firefox26:
--- → affected
tracking-firefox24:
? → ---
tracking-firefox25:
? → ---
tracking-firefox26:
? → ---
Comment 3•11 years ago
|
||
Is firefox even working on this?
Comment 4•11 years ago
|
||
(In reply to Amit Navindgi from comment #3)
> Is firefox even working on this?
Not at the moment.
Comment 5•10 years ago
|
||
FWIW this is still broken in Nightly 38.0a1 (2015-02-01).
Sebastian
Severity: normal → minor
Comment 6•10 years ago
|
||
Reproduced on 36.0.4 on Ubuntu 14.04
Updated•10 years ago
|
Assignee: paul → nobody
Comment 7•9 years ago
|
||
Still happens in FF developer version: 48.0a2 (2016-05-04)
Guys, you need to change this issue status from NEW to REALLY OLD. Since 2 and a half years you do not fixed it, and not works on this?
For the moment, this is not a high priority issue. If this changes, we'll assign someone. Of course we're also happy to have anyone investigate and provide patches if they would like to.
Priority: -- → P2
This sounds like the same issue as bug 1276629, which was fixed in Firefox 52. Please reopen if this is a separate problem.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•