Closed
Bug 721823
Opened 12 years ago
Closed 12 years ago
regression in image capture UI on native fennec
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 708175
Tracking | Status | |
---|---|---|
blocking-fennec1.0 | --- | + |
People
(Reporter: blizzard, Assigned: fabrice)
References
()
Details
When using the URL test case with native fennec I get two smooshed together buttons. I can't read them because they are pressed together. I assume one of them is to browse and one to capture. But I can't click on the capture button, and only ever get the browse button. On android 2.2.
Assignee | ||
Comment 1•12 years ago
|
||
Do we have a regression range?
Assignee | ||
Comment 2•12 years ago
|
||
I can repro on a fennec nightly, but things work fine on a b2g build. I'll look into fennec's content controls styling.
Comment 3•12 years ago
|
||
Why do we need the capture button if we use intents for image and video capture?
OS: Windows 7 → Android
Hardware: x86_64 → All
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Mounir Lamouri (:volkmar) (:mounir) from comment #3) > Why do we need the capture button if we use intents for image and video > capture? Because we can't use the same intent to pick files and to get an image from the camera. I'll bisect. It may be caused by a change in the way click events are dispatched to the content.
Assignee | ||
Comment 5•12 years ago
|
||
Testing with Kevin we figured out that this is a font inflation issue. Setting the "Text size" property to "Tiny" prevents the buttons to overlap. This is filed as Bug 708175
Comment 7•12 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #4) > (In reply to Mounir Lamouri (:volkmar) (:mounir) from comment #3) > > Why do we need the capture button if we use intents for image and video > > capture? > > Because we can't use the same intent to pick files and to get an image from > the camera. That seems like a very bad design which creates a very bad UI: all choices should be available at the same place, otherwise we should show a first popup asking the user if he/she wants to use the camera or a file instead of having this button with 'capture'. Anyway, that's a general issue with the file picker: the UI is bad but it's sad to see that Android is making it worse...
Comment 9•12 years ago
|
||
Interestingly http://people.mozilla.com/~jhammink/webapi_test_pages/CameraAPIdemo.html has the same problem, but the MWC demo at http://paulrouget.com/mwc-demos/apis/ works.
blocking-fennec1.0: --- → +
Comment 10•12 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #5) > Testing with Kevin we figured out that this is a font inflation issue. > Setting the "Text size" property to "Tiny" prevents the buttons to overlap. > This is filed as Bug 708175 So, there might be a bit of confusion here. Font inflation and the "text size" property are slightly different. Font inflation is turned on in about:config, with either the properties font.size.inflation.emPerLine or font.size.inflation.minTwips set to something other than 0. Can you confirm this is the case with this bug, and if so, is it resolved by turning these properties to 0?
Assignee | ||
Comment 11•12 years ago
|
||
In native fennec, the "Text size" preference sets the font.size.inflation.minTwips preference, with these values. See http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/resources/values/arrays.xml and http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/resources/xml/preferences.xml#32
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•