Closed
Bug 690762
Opened 13 years ago
Closed 5 years ago
[TABLETUI] Appearance of the navigation bar should be consistent with the appearance of the top bar in other apps on Samsung's Honeycomb devices
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: hsivonen, Unassigned)
References
Details
Attachments
(2 files)
Steps to reproduce: 1) Use Honeycomb device from Samsung, e.g. Galaxy Tab 10.1 2) Open and take a look at each of the following apps: * Calendar * Settings * Alarm * Video * Contacts * Email (not Gmail) * Music Hub * Music Player * My Files * Social Hub * World Clock 3) Open Firefox nightly. Actual results: The top bar in the apps mentioned in step #2 has a subtle gray gradient. The navigation bar in Nightly has a flat gray background. Expected results: Expected the navigation bar in Nightly to conform to the native Samsung-shipped theme on Samsung devices and to have the same subtle gray gradient as the apps mentioned in step #2.
Reporter | ||
Comment 1•13 years ago
|
||
Also, the top bar in the apps mentioned in step #2 has a 1px black bottom border and a slight drop shadow under the bar.
Reporter | ||
Comment 2•13 years ago
|
||
Reporter | ||
Comment 3•13 years ago
|
||
Updated•13 years ago
|
Blocks: 655762
Summary: Appearance of the navigation bar should be consistent with the appearance of the top bar in other apps on Samsung's Honeycomb devices → [TABLETUI] Appearance of the navigation bar should be consistent with the appearance of the top bar in other apps on Samsung's Honeycomb devices
Comment 4•13 years ago
|
||
What about other Honeycomb tablets? Like the EEE Transformer?
Reporter | ||
Comment 5•13 years ago
|
||
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #4) > What about other Honeycomb tablets? Like the EEE Transformer? I'd expect Firefox to match the theme that EEE Transformer ships when run on EEE Transformer.
Comment 6•13 years ago
|
||
We would need native theme support (bug 674041) in order to do this correctly, though in the meantime we *could* also try detecting the most popular devices/skins and putting in a few special cases for major items like the action bar background.
Depends on: 674041
Comment 7•13 years ago
|
||
(In reply to Matt Brubeck (:mbrubeck) from comment #6) > We would need native theme support (bug 674041) in order to do this > correctly, though in the meantime we *could* also try detecting the most > popular devices/skins and putting in a few special cases for major items > like the action bar background. I dont think this would be good in cases where a user has the ability to change their devices screen mode, (i.e., "Dynamic/Standard/Movie) which alters the native appearance of the system affecting all native applications. * * Samsung only?
Reporter | ||
Comment 8•13 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #7) > (In reply to Matt Brubeck (:mbrubeck) from comment #6) > > We would need native theme support (bug 674041) in order to do this > > correctly, though in the meantime we *could* also try detecting the most > > popular devices/skins and putting in a few special cases for major items > > like the action bar background. > > I dont think this would be good in cases where a user has the ability to > change their devices screen mode, (i.e., "Dynamic/Standard/Movie) which > alters the native appearance of the system affecting all native > applications. * Are more drastic measures that just changing the setting needed to provoke a theme change with that setting? AFAICT, the setting affects a global screen color transformation--not what apps think they are painting.
Comment 9•5 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•