Closed Bug 977643 Opened 10 years ago Closed 10 years ago

Now that android has a colorpicker, it shouldn't have a special pref("dom.forms.color", true) line in its prefs file

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox28 fixed, firefox29 fixed, firefox30 fixed, b2g-v1.3 fixed)

RESOLVED FIXED
Firefox 30
Tracking Status
firefox28 --- fixed
firefox29 --- fixed
firefox30 --- fixed
b2g-v1.3 --- fixed

People

(Reporter: dholbert, Assigned: arnaud.bienner)

References

Details

Attachments

(1 file, 1 obsolete file)

Bug 875750 added a color picker implementation for Android, bringing it up to parity with Windows / Mac / Linux.

It toggled the line
 pref("dom.forms.color", false);
in mobile/android/app/mobile.js to "true", when really it should have just deleted the line (so that we can take the default value from all.js).
Indeed, we decided to have this pref on by default, then overridden for platforms where is was missing. So, this line isn't needed.
Moreover, the comment was wrong indeed.
Assignee: nobody → arnaud.bienner
Status: NEW → ASSIGNED
Attachment #8383085 - Flags: review?(dholbert)
Attached patch fix (obsolete) — Splinter Review
Attachment #8383088 - Flags: review?(wjohnston)
Comment on attachment 8383088 [details] [diff] [review]
fix

Oh, you beat me to it :)

(Darned attachment-creation page, not showing midair patches)
Attachment #8383088 - Attachment is obsolete: true
Attachment #8383088 - Flags: review?(wjohnston)
Attachment #8383085 - Flags: review?(dholbert) → review+
Comment on attachment 8383085 [details] [diff] [review]
android_input_type_color_pref.patch

Requesting beta/aurora approval.

On Aurora, this has no effect, since we'll just get the same value from libpref's all.js.

On Beta, this is required in order for bug 977301 (which is disabling this feature) to take effect on Android.  So this is sort of a helper-bug for that bug. (just split out into this bug because it's a logically-separate [though prerequisite] change)

(Side note: a part of me thinks that maaaaybe we should just leave it enabled on Android, but I'm leaning towards thinking we should just disable it everywhere, because several of the bugs that are making us disable it (listed in bug 977301 comment 0) are non-platform-specific (bug 977038, bug 977029, and bug 949403))
Attachment #8383085 - Flags: approval-mozilla-aurora?
Blocks: 977301
Daniel, this patch should land in m-c first, right ?
Flags: needinfo?(dholbert)
Yes, and I intend to land them in the correct order.

I'm just preemptively requesting approval since I'm told the schedule for getting things into beta is tight, and this is required as part of bug 977301 (on beta).
Flags: needinfo?(dholbert)
https://hg.mozilla.org/mozilla-central/rev/b4826a1c1a27
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 30
Attachment #8383085 - Flags: approval-mozilla-beta?
Comment on attachment 8383085 [details] [diff] [review]
android_input_type_color_pref.patch

From my read on the comments in but 977301 it looks like the best plan is to not ship this at all in FF28 and try to get it together on FF29 with longer bake time on Beta.
Attachment #8383085 - Flags: approval-mozilla-beta?
Attachment #8383085 - Flags: approval-mozilla-beta+
Attachment #8383085 - Flags: approval-mozilla-aurora?
Attachment #8383085 - Flags: approval-mozilla-aurora+
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: