72d8e7693a5dc66acfd7aa4d5fd0c0c19beba9c9: Bug 1213517 - Only restart camera if net settings actually change. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Sat, 18 Jun 2016 14:16:47 -0400 - rev 379972
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Only restart camera if net settings actually change. MozReview-Commit-ID: h01gJ3uCom
8f13d0ab7b4228a26d2f49d2bcfbccc1946e0981: Bug 1213517 - Lift correct constraint out of lower-level code for OverconstrainedError. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Fri, 17 Jun 2016 21:42:39 -0400 - rev 379971
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Lift correct constraint out of lower-level code for OverconstrainedError. MozReview-Commit-ID: EWUjVBUrAps
0c2721f7e6c9439ab46620d7d7adceed9da201df: Bug 1213517 - Normalize even more of the constraints code. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Fri, 17 Jun 2016 15:20:10 -0400 - rev 379970
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Normalize even more of the constraints code. MozReview-Commit-ID: 1XjdHXKYOmP
a01130be1d84b02745702ddd053783d5b435b93e: Bug 1213517 - Report correct constraint in OverconstrainedError when constraints conflict directly. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Wed, 15 Jun 2016 19:25:07 -0400 - rev 379969
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Report correct constraint in OverconstrainedError when constraints conflict directly. MozReview-Commit-ID: 2bVaSvntc8g
5daad3bb3a0d382f02d9de54cc180d3780432467: Bug 1213517 - Consider competing required constraints with OverconstrainedError. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Tue, 14 Jun 2016 14:42:46 -0400 - rev 379968
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Consider competing required constraints with OverconstrainedError. MozReview-Commit-ID: EHIY1hpaEQn
1fd624234bc42273b869e1aa76e2eec1a7e9b7f2: Bug 1213517 - Consider competing constraints in getUserMedia+applyConstraints. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Mon, 06 Jun 2016 13:15:50 -0400 - rev 379967
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Consider competing constraints in getUserMedia+applyConstraints. MozReview-Commit-ID: 9jzjNrJVUMX
4256cad5b7b937790a7ff1218d9165c6ed828cbe: Bug 1213517 - Add a way to merge multiple NormalizedConstraints. draft
Jan-Ivar Bruaroey <jib@mozilla.com> - Fri, 27 May 2016 19:46:56 -0400 - rev 379966
Push 21102 by jbruaroey@mozilla.com at Mon, 20 Jun 2016 07:17:37 +0000
Bug 1213517 - Add a way to merge multiple NormalizedConstraints. MozReview-Commit-ID: LfB9QviCNxU
b897aecd13489aaee78d1c966f3b2c07c22ef33b: Bug 1279403 - Part 2: Set NS_FRAME_MAY_BE_TRANSFORMED bit if the target nsIFrame has transform when setting target or keyframes. r? draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 15:32:51 +0900 - rev 379965
Push 21101 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 06:33:26 +0000
Bug 1279403 - Part 2: Set NS_FRAME_MAY_BE_TRANSFORMED bit if the target nsIFrame has transform when setting target or keyframes. r? MozReview-Commit-ID: 23lr8gZY7TH
9787bc23019dc7c540704065acddfdea3baa0d52: Bug 1279403 - Part 1: Force to apply corresponding change hint if there is no corresponding layer to generate display item even if animation's segment is transform:none or 100% opacity. r? draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 15:32:51 +0900 - rev 379964
Push 21101 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 06:33:26 +0000
Bug 1279403 - Part 1: Force to apply corresponding change hint if there is no corresponding layer to generate display item even if animation's segment is transform:none or 100% opacity. r? To create a stacking context for animations on transform:none segment, we need to set NS_FRAME_MAY_BE_TRANSFORMED. The fix is comming in part 2. Note that in case of animations which has properties preventing running on the compositor, e.g., width or height, corresponding layer is not created at all, but even in such cases, we normally set valid change hint for such animations in each tick, i.e. restyles in each tick. For example: div.animate([{ opacity: 1, width: '100px' }, { opacity: 0, width: '200px' }], 1000); This animation causes restyles in every ticks without this patch, this patch does not affect such animations at all. The only animations which will be affected by this patch is that animations which has opacity/transform but did not have those properies. e.g, setting transform by setKeyframes or changing target element from other target which prevents running on the compositor, etc. MozReview-Commit-ID: 78fYqyX8uDX
310d8c17b3667cd123419b9a3f2f48e5cfbcae46: Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 15:00:45 +0900 - rev 379963
Push 21101 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 06:33:26 +0000
Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow We have to create stacking context for transform or opacity animations no matter what the animation state is, e.g. paused, unabled to run on the compositor or has fill:forwards. MozReview-Commit-ID: 8RyLJNPtoKI
2398bff33d947407f032bac98f447a6b6a188d94: Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:56:15 +0900 - rev 379962
Push 21100 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:56:38 +0000
Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow We have to create stacking context for transform or opacity animations no matter what the animation state is, e.g. paused, unabled to run on the compositor or has fill:forwards. MozReview-Commit-ID: 8RyLJNPtoKI
ed10219ff483c49a0bc7660993474abfdc405454: Bug 1278136 - Part 1: Add nsLayoutUtils::HasInEffectAnimationOfProperty. r? draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:56:15 +0900 - rev 379961
Push 21100 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:56:38 +0000
Bug 1278136 - Part 1: Add nsLayoutUtils::HasInEffectAnimationOfProperty. r? We want to know that an nsIFrame has a transform or opacity animations regardless of its state, e.g., running on the main-thead, paused or finished but in fill:forwards state, to create a stacking context for the animation. MozReview-Commit-ID: mNYsd5RO3u
f132e91f63611eb0c0febb14aab92b4e2ec3dd80: Bug 1278136 - Part 0: Clean up frame->StyleDisplay()->BackfaceIsHidden() usage. r?mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:56:12 +0900 - rev 379960
Push 21100 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:56:38 +0000
Bug 1278136 - Part 0: Clean up frame->StyleDisplay()->BackfaceIsHidden() usage. r?mattwoodrow We already have a wrapper named nsIFrame::BackfaceIsHidden(). MozReview-Commit-ID: 5L49W6wtXs1
8655addc357b20824c8eb85406525fa7cbbbcafe: Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:51:20 +0900 - rev 379959
Push 21099 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:51:49 +0000
Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow We have to create stacking context for transform or opacity animations no matter what the animation state is, e.g. paused, unabled to run on the compositor or has fill:forwards. MozReview-Commit-ID: 8RyLJNPtoKI
21f7bdad7277f39df27e36d2611432566e577b34: Bug 1278136 - Part 1: Add nsLayoutUtils::HasInEffectAnimationOfProperty. r? draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:51:20 +0900 - rev 379958
Push 21099 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:51:49 +0000
Bug 1278136 - Part 1: Add nsLayoutUtils::HasInEffectAnimationOfProperty. r? We want to know that an nsIFrame has a transform or opacity animations regardless of its state, e.g., running on the main-thead, paused or finished but in fill:forwards state, to create a stacking context for the animation. MozReview-Commit-ID: mNYsd5RO3u
9e737e6581b3df0769dc96056ff7b4ccf3c88976: Bug 1278136 - Part 0: Clean up frame->StyleDisplay()->BackfaceIsHidden() usage. r?mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:51:19 +0900 - rev 379957
Push 21099 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:51:49 +0000
Bug 1278136 - Part 0: Clean up frame->StyleDisplay()->BackfaceIsHidden() usage. r?mattwoodrow We already have a wrapper named nsIFrame::BackfaceIsHidden(). MozReview-Commit-ID: 5L49W6wtXs1
e6cce5898723f1110afcaeb43ee5b3f9c0a02001: Bug 1280053 TextInputHandler should initialize WidgetKeyboardEvent without already handled characters r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Sun, 19 Jun 2016 01:13:16 +0900 - rev 379956
Push 21098 by masayuki@d-toybox.com at Mon, 20 Jun 2016 05:50:42 +0000
Bug 1280053 TextInputHandler should initialize WidgetKeyboardEvent without already handled characters r?m_kato TextInputHandler may dispatch keypress events after InsertText() is called if there was composition and it's committed by "current" keydown event. In that case, [NSEvent characters] may have the committing string. For example, when Opt+e of US keyboard layout started composition, Cmd+v causes committing the "`" character and pasting the clipboard text. Then, the "v" key's keydown event's |characters| is "`v". So, after InsertText() is called with "`", TextInputHandler shouldn't dispatch keypress event for "`" again. I.e., the KeyboardEvent.key value should be "v" rather than "`v". For solving this issue, TextInputHandlerBase::AutoInsertStringClearer which is created at every InsertText() call should store the inserted string to TextInputHandlerBase::KeyEventState. However, for making the implemntation simpler, it should recode only when the inserting string is actually a part of [mKeyEvent characters]. Then, TextInputHandlerBase::KeyEventState can compute unhandled insert string at initializing WidgetKeyboardEvent. So, finally, TextInputHandlerBase::InitKeyEvent() should be called via TextInputHandlerBase::KeyEventState::InitKeyEvent(). This ensures that all key events which may cause InsertText() calls are always initialized with unhandled string. MozReview-Commit-ID: A9o8o9pV2XV
dfbe274cbaa5adcc5bdc6c11071bb5b4cf77741b: Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:49:34 +0900 - rev 379955
Push 21097 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:50:03 +0000
Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?mattwoodrow We have to create stacking context for transform or opacity animations no matter what the animation state is, e.g. paused, unabled to run on the compositor or has fill:forwards. MozReview-Commit-ID: 8RyLJNPtoKI
7147eb364847eb82bf21f043ea487e1ea87a8eb6: Bug 1279991 - Use [Func=] for EventTarget.mozSystemGroup. r?bz draft
Xidorn Quan <me@upsuper.org> - Mon, 20 Jun 2016 15:49:11 +1000 - rev 379954
Push 21096 by xquan@mozilla.com at Mon, 20 Jun 2016 05:49:20 +0000
Bug 1279991 - Use [Func=] for EventTarget.mozSystemGroup. r?bz MozReview-Commit-ID: B5pMVCUuss9
31b4a3262d2a151dccd98dd58ea5b4ff78e513ff: Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?birtles,mattwoodrow draft
Hiroyuki Ikezoe <hiikezoe@mozilla-japan.org> - Mon, 20 Jun 2016 14:45:02 +0900 - rev 379953
Push 21095 by hiikezoe@mozilla-japan.org at Mon, 20 Jun 2016 05:46:07 +0000
Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused. r?birtles,mattwoodrow We have to create stacking context for transform or opacity animations no matter what the animation state is, e.g. paused, unabled to run on the compositor or has fill:forwards. MozReview-Commit-ID: 8RyLJNPtoKI
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip