Closed
Bug 854469
Opened 12 years ago
Closed 12 years ago
Sliders are visually messed up when native <input type=range> is enabled
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:hd+, b2g-v1.1hd fixed)
People
(Reporter: jwatt, Assigned: jwatt)
References
Details
(Whiteboard: helix vsd, HD)
Attachments
(2 files)
2.08 KB,
patch
|
kaze
:
review+
|
Details | Diff | Splinter Review |
102.47 KB,
image/png
|
Details |
Even with the fix for bug 854138, the sliders in the Firefox OS Sound and Display settings screens are messed up if the native <input type=range> support is enabled. (This native support is enabled by default in Mozilla v22.)
There are various styling issues that I've been discussing with people via email, but it's probably time to take that discussion to a bug or two.
The sliders I'm talking about here are:
http://telefonicaid.github.com/Gaia-UI-Building-Blocks/index.html#widgets/seekbars/
![]() |
Assignee | |
Comment 1•12 years ago
|
||
Assignee: nobody → jwatt
Attachment #733870 -
Flags: review?(kaze)
![]() |
Assignee | |
Comment 2•12 years ago
|
||
I tested this with a master build on a Unagi device, against 1.0.1 on another Unagi device. The rendering of the sliders in the Sound and Display settings screen are virtually identical between the two. The master build is using <input type=range>, the 1.0.1 build is using the <div> and <span> polyfill.
![]() |
Assignee | |
Comment 3•12 years ago
|
||
The utils.js changes to add the without_bug344618_polyfill class are not necessary, but I thought it prudent in order to have a visual cue in the markup that would show up in the debugger in case anyone that is unaware of these changes ends up debugging the sliders at some point.
![]() |
Assignee | |
Comment 4•12 years ago
|
||
Comment 5•12 years ago
|
||
Comment on attachment 733870 [details] [diff] [review]
patch
https://github.com/mozilla-b2g/gaia/commit/7bc54c21c61c2b04c62ed2db061316e68ab2a8a4
Nit: I had to fix two linter issues. Next time, please check your patch with gjslint if you can.
Attachment #733870 -
Flags: review?(kaze) → review+
Comment 6•12 years ago
|
||
Tested with b2g18 and trunk.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
![]() |
Assignee | |
Comment 7•12 years ago
|
||
(In reply to Fabien Cazenave [:kaze] from comment #5)
> Nit: I had to fix two linter issues. Next time, please check your patch with
> gjslint if you can.
Will do, thanks, kaze!
Updated•12 years ago
|
status-b2g-v1.1hd:
--- → ?
Updated•12 years ago
|
blocking-b2g: --- → hd?
Whiteboard: helix vsd, HD
Updated•12 years ago
|
Comment 8•12 years ago
|
||
Does this fix any HD branch-specific issue?
If not we wont take it for now as HD should align as much as possible with v1-train leo unless it is HD layout/asset specific.
Please renom HD? if this is the case (makes HD look broken), otherwise we'll leave it on master for future releases.
blocking-b2g: hd? → ---
Comment 9•12 years ago
|
||
(In reply to Wayne Chang [:wchang] from comment #8)
> Does this fix any HD branch-specific issue?
> If not we wont take it for now as HD should align as much as possible with
> v1-train leo unless it is HD layout/asset specific.
>
> Please renom HD? if this is the case (makes HD look broken), otherwise we'll
> leave it on master for future releases.
Sam, you mentioned Pavel needed this bug to land for an HD bug? Can you let me know if this bug affects HD as well? Thanks!
Flags: needinfo?(sjochimek)
Comment 10•12 years ago
|
||
Flags: needinfo?(sjochimek) → needinfo?(epang)
Comment 11•12 years ago
|
||
(In reply to Sam Joch [:samjoch] from comment #10)
> Created attachment 793886 [details]
> How v1.1.0hd is affected
Thanks Sam! Wayne, I've renomed fot HD, see the screen Sam added. Thanks!
blocking-b2g: --- → hd?
Flags: needinfo?(epang) → needinfo?(wchang)
Updated•12 years ago
|
blocking-b2g: hd? → hd+
Flags: needinfo?(wchang)
Updated•12 years ago
|
Component: General → Gaia::Settings
Comment 12•11 years ago
|
||
(In reply to Eric Pang [:epang] from comment #11)
> (In reply to Sam Joch [:samjoch] from comment #10)
> > Created attachment 793886 [details]
> > How v1.1.0hd is affected
>
> Thanks Sam! Wayne, I've renomed fot HD, see the screen Sam added. Thanks!
Hey Sam, Wayne has made this HD+ so we can land in HD now. Thanks!
Flags: needinfo?(sjochimek)
Comment 13•11 years ago
|
||
Landed in v1.1.0hd: https://github.com/mozilla-b2g/gaia/commit/2c5b7f4333750819372b2adf0f35a7a7f4e1cb30
Still need https://bugzilla.mozilla.org/show_bug.cgi?id=854138 and https://bugzilla.mozilla.org/show_bug.cgi?id=802234 to complete fix of input in v1.1.0hd.
Flags: needinfo?(sjochimek)
![]() |
||
Comment 14•11 years ago
|
||
[2013/10/21 Helix Testing]
Gaia: c829a2042594b6c3a4899ee27979799a0f301534
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/f7c657f6d019
BuildID 20131015042201
Version 18.0
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•