Unprefix transition styles

RESOLVED FIXED in Firefox 24

Status

()

Firefox for Android
General
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: Margaret, Assigned: nickecarlo)

Tracking

Trunk
Firefox 24
ARM
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [mentor=margaret][lang=css][good first bug])

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Transitions were unprefixed in Fx16:
https://developer.mozilla.org/en-US/docs/Web/CSS/transition#Browser_compatibility

Let's update our CSS accordingly.
(Reporter)

Comment 1

4 years ago
Here's a quick search of all the places we use -moz-transition:
http://mxr.mozilla.org/mozilla-central/search?find=/mobile/android/&string=moz-transition
(Assignee)

Comment 2

4 years ago
Hey Margaret,

Can I work on this? As far as I understand, I would just need to replace transitions prefixed as "-moz-transitions" to "transitions" as per the first link, is that correct?
(Reporter)

Comment 3

4 years ago
(In reply to Nicolas Carlo from comment #2)
> Hey Margaret,
> 
> Can I work on this? As far as I understand, I would just need to replace
> transitions prefixed as "-moz-transitions" to "transitions" as per the first
> link, is that correct?

Yep, that's right, you should just strip the "-moz-" from the transition property declarations. To make sure nothing's gone awry, you should make a build and play around with the places where we use these transitions, which are HTML5 video controls (touchcontrols.css) and reader mode (aboutReader.css).
Assignee: nobody → nickecarlo
(Assignee)

Comment 4

4 years ago
Thanks for giving me a shot Margaret. I apologize for not starting on this sooner. I had been having a lot of trouble just building and deploying Fennec as is. I just got it working on my phone so I will start refactoring the code, as per the documentation suggested, tomorrow.

I will probably have a lot of questions still (especially about how to make patches and how to attach them to bugs) so I'll ask them, as they come, in the room (#mobile).
Then, what about the compatibility for pages that implemented "moz-transition" earlier?
(Reporter)

Comment 6

4 years ago
(In reply to shashank16392 from comment #5)
> Then, what about the compatibility for pages that implemented
> "moz-transition" earlier?

I'm afraid I don't understand this question. This change is for CSS styles that are part of the Firefox frontend code, so they only need to work with the version of gecko they're shipped with.
(Assignee)

Comment 7

4 years ago
Created attachment 753222 [details] [diff] [review]
Unprefixed the transitions in CSS
Attachment #753222 - Flags: review?(margaret.leibovic)
(Reporter)

Comment 8

4 years ago
Comment on attachment 753222 [details] [diff] [review]
Unprefixed the transitions in CSS

Looks great, thanks!
Attachment #753222 - Flags: review?(margaret.leibovic) → review+
(Reporter)

Comment 9

4 years ago
I'm marking this bug as checkin-needed, so someone will come along and land your patch for you.

If you're looking for another bug to tackle, you may want to try out bug 872003, since it deals with the same code.
Keywords: checkin-needed
(Assignee)

Comment 10

4 years ago
(In reply to :Margaret Leibovic from comment #9)
> I'm marking this bug as checkin-needed, so someone will come along and land
> your patch for you.
> 
> If you're looking for another bug to tackle, you may want to try out bug
> 872003, since it deals with the same code.

Awesome. Thank you very much. I'll leave a comment about bug 872003 on its page.
(Reporter)

Comment 11

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/4ac719409352
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/4ac719409352
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 24
You need to log in before you can comment on or make changes to this bug.