4e8a8884e36ff65a91e732c0f5ed17dc823e565b: Bug 1181392 part 2 - Remove use of IsFinishedTransition from Animation::ComposeStyle; r=dbaron
Brian Birtles <birtles@gmail.com> - Fri, 07 Aug 2015 12:29:35 +0900 - rev 256748
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1181392 part 2 - Remove use of IsFinishedTransition from Animation::ComposeStyle; r=dbaron Animation::ComposeStyle uses IsFinishedTransition to skip doing work for transitions that have run their course. We can, however, generalize this to cover all animations that are not currently contributing to the animated style--that is animations that are not "in effect". We need to add this check *after* we update aNeedsRefreshes since an animation that is not "in effect" because it has a delay and no backwards fill (in this case it will have a play state of "running") still needs refreshes.
7fa8a6d1f67f9e3ab960de0b539100169e926727: Bug 1181392 part 1 - Remove use of IsFinishedTransition from Animation::CanThrottle; r=dbaron
Brian Birtles <birtles@gmail.com> - Fri, 07 Aug 2015 12:29:35 +0900 - rev 256747
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1181392 part 1 - Remove use of IsFinishedTransition from Animation::CanThrottle; r=dbaron Previously we used IsFinishedTransition so that if the only animations present are finished transitions we could throttle the tick. In fact, this probably shouldn't even be necessary since we shouldn't be calling CanThrottle if AnimationCollection::mNeedsRefreshes is false. However, so long as we're performing this test it turns out we can generalize this further and throttle ticks for all finished animations that are not newly finished, regardless of whether they are running on the compositor or not (although this method won't be called unless the animation property could be run on the compositor anyway). This method is somewhat confusing. For one, it is not strictly limited to animations that are running on the compositor. It appears to only return true when the animation is running on the compositor but the mIsRunningOnCompositor flag doesn't get cleared when the animation finishes (bug 1151694). As a result this method also deals with animations that are now running on the main thread. This patch makes us deal with such animations more consistently. This patch also reworks this method so that it's hopefully a little easier to follow and a little more consistent since I spent several hours trying to understand the different combinations of inputs this method could take and what question it was trying to answer.
e14cb4eb7c0bdd00b20ab6ff212e5f72158b12a9: Bug 1190735 - Remove nsITimer.TYPE_REPEATING_PRECISE. r=froydnj.
Nicholas Nethercote <nnethercote@mozilla.com> - Tue, 04 Aug 2015 17:30:53 -0700 - rev 256746
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1190735 - Remove nsITimer.TYPE_REPEATING_PRECISE. r=froydnj.
f58ce99d0d99256512a5e5f7f648a98b9d4b5da7: Bug 1191959 - Make sure that pinned tabs are still clickable after unuting a tab that is not playing; r=jaws
Ehsan Akhgari <ehsan@mozilla.com> - Thu, 06 Aug 2015 22:29:06 -0400 - rev 256745
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1191959 - Make sure that pinned tabs are still clickable after unuting a tab that is not playing; r=jaws This bug happens becuase when toggleMuteAudio() is called from the click handler for the tab, we remove the muted attribute during unmuting, which makes the element display:none. Therefore, when the mouse pointer leaves that region, there is no element to receive the mouseout event and as a result, the _overPlayingIcon variable stays true, which means we stop tab switching in the mousedown handler.
6fb2fb69fe674e2b776a427f4f3e36f235aa3a55: Bug 1191173 - Mirror MediaDecoder::mSameOriginMedia in MDSM. r=jya.
JW Wang <jwwang@mozilla.com> - Thu, 06 Aug 2015 18:05:30 +0800 - rev 256744
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1191173 - Mirror MediaDecoder::mSameOriginMedia in MDSM. r=jya.
feb18f1bdeaac7c8e3122824c307b3314747d1ee: Bug 1188131: Don't rely on MediaResource type to detect media format. r=cpearce
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 06 Aug 2015 21:06:45 +1000 - rev 256743
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1188131: Don't rely on MediaResource type to detect media format. r=cpearce This information is often wrong and non-existent with MSE. Let the PDM decides later based on the metadata. This prevent hardware acceleration to be turned on leading to extremely high CPU usage on high definition videos.
4367154a39b1afb2a0e9f573b26ee49cb5cad138: Bug 1191670 - Tweak comments in some memory reporter tests. r=erahm.
Nicholas Nethercote <nnethercote@mozilla.com> - Thu, 06 Aug 2015 19:07:50 -0700 - rev 256742
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1191670 - Tweak comments in some memory reporter tests. r=erahm. DONTBUILD because comment-only changes.
ca5ebc4c7af9d67938e94ba4c97614635c95ece4: Merge m-c to inbound, a=merge
Wes Kocher <wkocher@mozilla.com> - Thu, 06 Aug 2015 18:42:15 -0700 - rev 256741
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Merge m-c to inbound, a=merge
bd9983f167c2658d1a9f5863fc43f2c0860f0e45: Bug 983301 Add a test for FetchEvent.respondWith(5). r=bz
Ben Kelly <ben@wanderview.com> - Thu, 06 Aug 2015 18:12:14 -0700 - rev 256740
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 983301 Add a test for FetchEvent.respondWith(5). r=bz
efc97cd68267c35d255daa6c2aa2baeddc4daf94: Merge m-c to inbound, a=merge
Wes Kocher <wkocher@mozilla.com> - Thu, 06 Aug 2015 18:11:16 -0700 - rev 256739
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Merge m-c to inbound, a=merge
8fc2a69b16c0392f21eaec7fcfe9148f6c4b7872: Bug 1192070 - avoid complaining about missing override keywords in skia; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Fri, 07 Aug 2015 01:34:57 -0400 - rev 256738
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1192070 - avoid complaining about missing override keywords in skia; r=glandium
6f7075c3966fbd419a3fdeec6bfc112017df1898: Bug 1191900 - remove superfluous check for GCC force_align_arg_pointer attribute; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Thu, 06 Aug 2015 21:07:57 -0400 - rev 256737
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1191900 - remove superfluous check for GCC force_align_arg_pointer attribute; r=glandium qcms and libav use __attribute__((force_align_arg_pointer)) unconditionally; the libav use case suggests that the attribute has been around since GCC 4.2. We're well past that point with GCC, and clang supports it also. So we can simply assume the compiler has it in the appropriate places. It is, however, x86 only (x86-64 appropriately aligns the stack at all times), so we need to adjust the libpixman build code appropriately.
3b735e43f09c103e46bd460bb04548fd32e2a7bc: Bug 1191884 - remove now-unnecessary check for GCC PR49911; r=glandium
Nathan Froyd <froydnj@mozilla.com> - Thu, 06 Aug 2015 20:41:38 -0400 - rev 256736
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1191884 - remove now-unnecessary check for GCC PR49911; r=glandium This PR was fixed in the GCC 4.7 development cycle. Since we require GCC 4.7 now, we no longer have to check for this bug.
6d2e0fcded599f6185cb60ccfbdcd28c7b97eaff: Remove the backend flag to TextureClient::CreateForDrawing. (bug 1183910 part 9, r=mattwoodrow)
David Anderson <danderson@mozilla.com> - Thu, 06 Aug 2015 17:27:36 -0700 - rev 256735
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Remove the backend flag to TextureClient::CreateForDrawing. (bug 1183910 part 9, r=mattwoodrow)
f8159fd0e43c34eccbf7006bfd9df57385a25674: Bug 1191081 - Part 2: Make the crashed overlay icon for pinned tabs take priority over the muted overlay icon; r=jaws
Ehsan Akhgari <ehsan@mozilla.com> - Tue, 04 Aug 2015 17:59:39 -0400 - rev 256734
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1191081 - Part 2: Make the crashed overlay icon for pinned tabs take priority over the muted overlay icon; r=jaws
2ac09126d207b8e8d4bcad0251c5f5d57d5a7b4a: Bug 1174011, fix xulrunner-stub compile, r=gladium DONTBUILD
Nick Thomas <nthomas@mozilla.com> - Fri, 07 Aug 2015 12:20:28 +1200 - rev 256733
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1174011, fix xulrunner-stub compile, r=gladium DONTBUILD
a7054bcee797e83e8ce2359a0e572abf9fde886e: Bug 1180125 part 8 - Dispatch transition events from refresh driver; r=dbaron
Brian Birtles <birtles@gmail.com> - Wed, 29 Jul 2015 10:57:40 +0900 - rev 256732
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1180125 part 8 - Dispatch transition events from refresh driver; r=dbaron This patch causes transition events to be dispatched as a separate step after sampling the transitions. Eventually this will allow us to sample transitions from their timeline (independently of where they came from and in potentially any order) by separating the concepts of sampling and event dispatch.
c9a55501a48fa4d022403a912e0770f1a2461ac1: Bug 1180125 part 7 - Queue transition events from CSSTransition::Tick; r=dbaron
Brian Birtles <birtles@gmail.com> - Wed, 29 Jul 2015 10:57:40 +0900 - rev 256731
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1180125 part 7 - Queue transition events from CSSTransition::Tick; r=dbaron This patch moves the logic for queueing events out of the logic for flushing transitions making it a separate step. It still doesn't delay the dispatch of those events into a separate step, however. That is done in a subsequent patch. This patch also makes sure to clear any queued events when the nsPresShell that owns the transition manager is destroyed. We don't expect CSSTransition::Tick to be called anywhere except nsTransitionManger::FlushTransitions so there shouldn't be any orphaned events but for completeness it seems best to add this now. (Later, when we tick transitions from their timeline we will need this.) This patch introduces a separate flag to CSSTransition for tracking if a transition is newly-finished so we can correctly dispatch the transitionend event. Although, this may seem to be redundant with the "IsFinishedTransition" we also track, that state will soon be removed in bug 1181392 and hence this flag will be needed then. Note that Animation already has flags mIsPreviousStateFinished and mFinishedAtLastComposeStyle which would appear to be similar however, - mIsPreviousStateFinished will be removed in bug 1178665 and is updated more often than we queue events so it is not useful here. - mFinishedAtLastComposeStyle is used to determine if we can throttle a style update and is also updated more frequently than we queue events and hence can't be used here. Once we guarantee one call to Tick() per frame we may be able to simplify this by tracking "state on last tick" but for now we need this additional flag on CSSTransition. CSSAnimation has a similar flag for this (mPreviousPhaseOrIteration) which we may be able to unify at the same point.
0162e758928d832be2fab18a113d41e8e2d9ad6f: Bug 1180125 part 6 - Use DelayedEventDispatcher in nsTransitionManager; r=dbaron
Brian Birtles <birtles@gmail.com> - Wed, 29 Jul 2015 10:57:40 +0900 - rev 256730
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1180125 part 6 - Use DelayedEventDispatcher in nsTransitionManager; r=dbaron This simply uses the DelayedEventDispatcher in place of the previous array of TransitionEventInfo objects. Doing the actual delayed dispatch is performed in a separate patch.
e901b139e679c6744e2c6e5c197fda67f74fb9ef: Bug 1180125 part 5 - Move TransitionEventInfo to nsTransitionManager.h; r=dbaron
Brian Birtles <birtles@gmail.com> - Wed, 29 Jul 2015 10:57:40 +0900 - rev 256729
Push 29187 by cbook@mozilla.com at Fri, 07 Aug 2015 11:13:32 +0000
Bug 1180125 part 5 - Move TransitionEventInfo to nsTransitionManager.h; r=dbaron This is needed so we can allocate storage in nsTransitionManager for the transition events we will queue for delayed dispatch.
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip