Bugzilla – Bug 13484
Slider templates are not to spec.
Last modified: 2010-02-18 13:19:08 UTC
Created attachment 5631 [details] Ref artwork - correct slider template Please see corresponding guidelines/ref.
this is a dup, but I'll just leave it open because I can't find the number right now. P1 though. FYI, will have exactly the same asset issue that the volume bar in Fab4 does, which I alone cannot fix.
== Auto-comment from SVN commit #7226 to the jive repo by bklaas == == https://svn.slimdevices.com/jive?view=revision&revision=7226 == Bug: 13484 Description: as a temporary workaround use volume slider assets for all sliders in QVGA skins (scanner and volume popups, sliders in menus like bass/treble). This is not the spec, but keeps it from looking very broken for now. We have an outstanding issue that it's not possible to render a slider with four assets (left, middle, right, and end "button"). UI spec for sliders will look broken until that is fixed. This is the same problem that affects the slider rendering on the Fab4 volume slider.
Created attachment 5665 [details] how sliders look after last checkin we're going to be making compromises for 7.4 release, and this is probably one of them. I'm going to move this to a P2 bug. If there's a strong desire for a change before initial release, please comment here.
Thx Ben. FWIW this should be totally acceptable for 7.4 release. My only issues are with obvious misalignment's and where any assets appear 'broken.'
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
*** Bug 13453 has been marked as a duplicate of this bug. ***
re-estimating for real fix
moving current p2 bugs to p3 to make room for moving p1.5 bugs to p2
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
ben, dupe of bug 12402?
i'll just make one dependent on the other for now
this is most of the way there, but we can't do a 4-part slider tile (left, center, right, "button") I don't see any work being done on fixing that, so this is a WONTFIX