Closed
Bug 1191953
Opened 9 years ago
Closed 7 years ago
[RedSquare] Need to emulate a non-touch small screen flip-phone on a smart phone
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(feature-b2g:2.2r+)
RESOLVED
WONTFIX
feature-b2g | 2.2r+ |
People
(Reporter: djf, Unassigned)
References
Details
(Whiteboard: [caf priority: p2][CR 906607])
For the RedSquare project, we need to be able to emulate a non-touch flip-phone on a smartphone device.
This bug is to make the required changes to b2g/chrome/content/shell.html and related files to display a flip phone keypad and a 240x320 screen on a larger touchscreen device.
Blocks: CAF-v2.2r-FL-metabug
Updated•9 years ago
|
blocking-b2g: 2.2r? → ---
feature-b2g: --- → 2.2r+
Updated•9 years ago
|
Whiteboard: [CR 906607]
Updated•9 years ago
|
Whiteboard: [CR 906607] → [caf priority: p2][CR 906607]
Comment 1•9 years ago
|
||
The description of the bug is very brief, so as far as we understand it is necessary to create some kind of 'skin' for system application which will restrict screen area available for applications to small part of actual smartphone screen and use remaining space to draw virtual flip-phone keyboard. Is this correct understanding? What functionality should be supported by this “skin” then? Is it necessary to provide some kind of secondary screen emulation/support or it is not required by now?
Updated•9 years ago
|
Flags: needinfo?(dflanagan)
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Alexey Yakimov from comment #1)
> The description of the bug is very brief, so as far as we understand it is
> necessary to create some kind of 'skin' for system application which will
> restrict screen area available for applications to small part of actual
> smartphone screen and use remaining space to draw virtual flip-phone
> keyboard. Is this correct understanding? What functionality should be
> supported by this “skin” then? Is it necessary to provide some kind of
> secondary screen emulation/support or it is not required by now?
Alexey: yes, that is the basic idea. See my patch in bug 1191151 for example code. In that case the skin is created by the responsive mode code. That code for creating this skin will have to move to b2g/chrome/content/
Note that the skin is created with XUL, not HTML.
It is not clear to me how we change the Screen.width and Screen.height values in this emulator, but maybe the same approach used by responsive mode will work
It is also not clear how to handle devicePixelRatio. To start, we might be emulating a flip phone with the wrong dpr, but we can live with that to start.
At some point we'll want to support a secondary screen with this emulator, but that can come later. For now we can just simulate a flip phone that is always open.
Flags: needinfo?(dflanagan) → needinfo?(Alexey.Yakimov)
Reporter | ||
Comment 3•9 years ago
|
||
I meant bug 1191951 in the comment above. Sorry about that.
Comment 4•9 years ago
|
||
I'm not sure what kind of information is required from my side. In general this is more or less clear what is needed in scope of this bug, however implementation of this emulator requires some investigation and prototyping first. We are eager to contribute here, but for the moment we don't have spare resources to start working on this feature.
David, please clarify if you need any technical feedback from our side since you set the needinfo flag.
Flags: needinfo?(Alexey.Yakimov)
Comment 5•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•