853808 - Firefox OS work for native <input type=range> support

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect)

Description

[Jonathan Watt [:jwatt]]

The native <input type=range> implementation has now been enabled (bug 841948) on mozilla-inbound. It's not exactly clear to me when this will filter through and affect B2G, but once it does there is definitely some work than needs to be done. Specifically we need to:

 * Remove the polyfill code
 * Ensure that the default styling is correct for B2G

Comment 1

[Mounir Lamouri (:mounir)]

AFAIK, the polyfill in B2G will automatically use the native implementation when <input type='range'> will be detected as working. Though, we should remove it to save space.

Comment 2

[Jonathan Watt [:jwatt]]

It does not. There are JS errors that break settings screens, at least due to calling .refresh() on the element without checking whether that function exists. Unfortunately while trying to work through those issues I've run into:

https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.gaia/zz-H0gBSHQY

Comment 3

[Jonathan Watt [:jwatt]]

Right now I can't build B2G with the native <input type=range> support for an actual device because m-c (git 'origin') seems to have grown to big to link libxul. I filed bug 854535 and am marking that as a blocker of this bug because it's hurting my progress here.

Comment 4

[Jonathan Watt [:jwatt]]

I believe we're all done here.