Closed Bug 859868 Opened 11 years ago Closed 11 years ago

Turn off <input type=range> on v22

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox22 + disabled
firefox23 - ---

People

(Reporter: jwatt, Assigned: jwatt)

Details

(Keywords: dev-doc-needed)

Attachments

(1 file, 2 obsolete files)

There are still a few bits and pieces that need to be finished off before we can ship <input type=range>. I don't think it's worth the effort or risk to port those to aurora, so we should turn off <input type=range> for v22.

This will involve flipping the dom.experimental_forms_range to false, and removing a bunch of forms.css styling that we couldn't put behind the pref.
Attached patch Patch (obsolete) — Splinter Review
This patch makes sure we enable <input type='range'> only for Aurora and Nightly builds. It will automatically be disabled for other builds.
Assignee: jwatt → mounir
Status: NEW → ASSIGNED
Attachment #735424 - Flags: review?(jwatt)
Comment on attachment 735424 [details] [diff] [review]
Patch

I'm afraid this isn't enough, Mounir. See comment 0 - there are forms.css changes that need to be removed at the same time as the pref. If the pref is off, then we want the input to display like a text field, but currently it won't render anything due to the styling that removes the background, etc.
Attachment #735424 - Flags: review?(jwatt) → review-
Good point Jonathan. I guess I can leave that to you then.
Assignee: mounir → jwatt
Attached patch patch (obsolete) — Splinter Review
Attachment #735424 - Attachment is obsolete: true
Attachment #736780 - Flags: review?(mounir)
Attached patch patchSplinter Review
Actually this requires quite a lot of manual test disabling too.
Attachment #736780 - Attachment is obsolete: true
Attachment #736780 - Flags: review?(mounir)
Attachment #737308 - Flags: review?(mounir)
Comment on attachment 737308 [details] [diff] [review]
patch

Review of attachment 737308 [details] [diff] [review]:
-----------------------------------------------------------------

You could also disable the pseudo-elements because those are web-facing features somehow. In another hand, it seems unlikely that any website depends on those if the input type doesn't actually work. Let say that it would be good to remove them if it isn't too hard to do so.
Attachment #737308 - Flags: review?(mounir) → review+
Comment on attachment 737308 [details] [diff] [review]
patch

[Approval Request Comment]
Bug caused by (feature/regressing bug #): disabling the many bugs implementing the feature
User impact if declined: a poor implementation of <input type=range>
Testing completed (on m-c, etc.): none - branch only disabling patch
Risk to taking this patch (and alternatives if risky): should be low
String or IDL/UUID changes made by this patch: none
Attachment #737308 - Flags: approval-mozilla-aurora?
Comment on attachment 737308 [details] [diff] [review]
patch

Approving the low risk patch which disables the feature on aurora(Fx22).
Attachment #737308 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Adding verifyme for QA to make sure the pref is false by default once the patch lands.
Keywords: verifyme
https://hg.mozilla.org/releases/mozilla-aurora/rev/9766b6026f60

(In reply to Mounir Lamouri (:mounir) from comment #6)
> You could also disable the pseudo-elements because those are web-facing
> features somehow. In another hand, it seems unlikely that any website
> depends on those if the input type doesn't actually work. Let say that it
> would be good to remove them if it isn't too hard to do so.

It turned out to be pretty messy, so I didn't do that.
This is already documented as implemented in Fx22 here:
https://developer.mozilla.org/en/docs/HTML/Element/Input
and here:
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/22
and needs to change
Keywords: dev-doc-needed
Attachment #737308 - Flags: checkin+
Forgot to close this.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
This is shipping with FF23, no need to track turning it off.
mass remove verifyme requests greater than 4 months old
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: