5b00328e3e7ed516f7c71a96ed447499f3937f6a: Bug 1315598 - Part 2: Add test for short duration animation. r?pbro draft
Daisuke Akatsuka <daisuke@mozilla-japan.org> - Thu, 17 Nov 2016 12:18:18 +0900 - rev 440209
Push 36174 by bmo:daisuke@mozilla-japan.org at Thu, 17 Nov 2016 04:14:52 +0000
Bug 1315598 - Part 2: Add test for short duration animation. r?pbro MozReview-Commit-ID: IGyhXoPKehI
1c77ed5618ec95f3a21627c4bc8a778f48b38b59: Bug 1315598 - Part 1: Edge of animation graph is diagonal sometimes. r=pbro draft
Daisuke Akatsuka <daisuke@mozilla-japan.org> - Thu, 17 Nov 2016 09:28:05 +0900 - rev 440208
Push 36174 by bmo:daisuke@mozilla-japan.org at Thu, 17 Nov 2016 04:14:52 +0000
Bug 1315598 - Part 1: Edge of animation graph is diagonal sometimes. r=pbro MozReview-Commit-ID: 6HmsFklqzyK
f14294a76dbb99d6e15b0d4acf6287d4b91be76a: Bug 1317906 When a key press causes a call of InsertText(), it shouldn't mark keypress as consumed but instead, should mark InsertText() caused composition r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 16 Nov 2016 19:51:00 +0900 - rev 440207
Push 36173 by masayuki@d-toybox.com at Thu, 17 Nov 2016 04:10:40 +0000
Bug 1317906 When a key press causes a call of InsertText(), it shouldn't mark keypress as consumed but instead, should mark InsertText() caused composition r?m_kato Currently, when InsertText() which is caused by a key press causes committing composition, it consumes keypress event. However, Korean 2-set IME calls InsertText() two times when there is composition and key press causes inserting another character next to the composition. In this case, current design ignores second InsertText() becuase keypress event is already consumed by the first InsertText() call. For solving this issue safely, InsertText() should mark current key event as "dispatched composition event". Then, following InsertText() calls should cause composition events instead of keypress events since following event order is too odd: 1. keydown (currently not dispatched by TextEventDisaptcher) 2. compositionupdate 3. compositionend 4. keypress 5. keyup with the new design this becomes: 1. keydown (currently not dispatched by TextEventDispatcher) 2. compositionupdate 3. compositionend 4. compositionstart 5. compositionupdate 6. compositionend 7. keyup This is similar to Chromium, although, Chromium includes the second InsertText() call into the first composition, we need to fix it later due to risky. MozReview-Commit-ID: GL42cU2WIL0
2d1363eefced1e88ee9ae487dab18a14af5f2b6e: Bug 1315386 - Make Safe Browsing code more shutdown-aware draft
Thomas Nguyen <tnguyen@mozilla.com> - Thu, 17 Nov 2016 11:57:13 +0800 - rev 440206
Push 36172 by tnguyen@mozilla.com at Thu, 17 Nov 2016 03:57:36 +0000
Bug 1315386 - Make Safe Browsing code more shutdown-aware * * * [mq]: 1315386_review MozReview-Commit-ID: J6pFlnAprJP * * * [mq]: 1315386_1_review MozReview-Commit-ID: LqomxZBVcTb
fb42ab90e055a894427eee595bf737b04e9fab89: Bug 1286151 - Part 7: Make ComputeShapeDistance and ComputeFilterListDistance return status. draft
Boris Chiou <boris.chiou@gmail.com> - Thu, 17 Nov 2016 11:52:41 +0800 - rev 440205
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 7: Make ComputeShapeDistance and ComputeFilterListDistance return status. We should follow the rules used by other types if computing the distance is failed, so make ComputeShapeDistance and ComputeFilterListDistance return the status and the output distance is the last argument. MozReview-Commit-ID: CFoQhgyqILB
a9c59441f5279dbe58824a4a801cf60134b021df: Bug 1286151 - Part 6: Move tests of spacing on transform into wpt. draft
Boris Chiou <boris.chiou@gmail.com> - Tue, 15 Nov 2016 16:50:47 +0800 - rev 440204
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 6: Move tests of spacing on transform into wpt. Only replace addDiv with createDiv in spacing-keyframes-transform.html. Others are the same. MozReview-Commit-ID: JNSpyc6WNtP
ec098d5bfaffd9817aa34f7ff04eca43df731b06: Bug 1286151 - Part 5: Test. draft
Boris Chiou <boris.chiou@gmail.com> - Mon, 14 Nov 2016 11:42:15 +0800 - rev 440203
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 5: Test. MozReview-Commit-ID: wORyuqtfj
08a41cb13ba87fd04cd027d030ddef6f8c126e6a: Bug 1286151 - Part 4: Factor out ComputeShadowDistance. draft
Boris Chiou <boris.chiou@gmail.com> - Tue, 15 Nov 2016 11:58:16 +0800 - rev 440202
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 4: Factor out ComputeShadowDistance. Both eUnit_Shadow and the drop-shadow of eUnit_Filter needs to compute the distance of two shadows, so we can factor out the implementation. However, there is a little bit different in these two places. If one shadow have color, another one doesn't have color value: 1. In eUnit_Shadow, we skip the current shadow pair, and then continue to compute the distance of the next pair. 2. In eUnit_Filter, we return zero distance of the current filter list pair directly. MozReview-Commit-ID: IGdxQWMXdE1
404a93efb37fae82dea79278d583cf95424886ea: Bug 1286151 - Part 3: Implement filter distance for the rest. draft
Boris Chiou <boris.chiou@gmail.com> - Thu, 10 Nov 2016 17:25:10 +0800 - rev 440201
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 3: Implement filter distance for the rest. MozReview-Commit-ID: EXBzvJ7PIwQ
101e335f7ecad1d6c14fffc9dbcf65be252dbf91: Bug 1286151 - Part 2: Implement filter distance for drop-shadow. draft
Boris Chiou <boris.chiou@gmail.com> - Thu, 10 Nov 2016 17:46:35 +0800 - rev 440200
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 2: Implement filter distance for drop-shadow. MozReview-Commit-ID: 5Ad0GiWGkJg
f582b76b0eddba0931df9e2e290ad8d0dfa4823d: Bug 1286151 - Part 1: Implement filter distance for blur. draft
Boris Chiou <boris.chiou@gmail.com> - Thu, 10 Nov 2016 15:15:52 +0800 - rev 440199
Push 36171 by bmo:boris.chiou@gmail.com at Thu, 17 Nov 2016 03:56:27 +0000
Bug 1286151 - Part 1: Implement filter distance for blur. MozReview-Commit-ID: 44EP55V8ldg
8b0c9f5e59fd416f8a8960acc49edbec7c3b3c84: bug 1303964 draw only background and frame of separator menuitems in GTK versions > 3.20 r?stransky draft
Karl Tomlinson <karlt+@karlt.net> - Thu, 17 Nov 2016 11:08:33 +1300 - rev 440198
Push 36170 by ktomlinson@mozilla.com at Thu, 17 Nov 2016 03:46:33 +0000
bug 1303964 draw only background and frame of separator menuitems in GTK versions > 3.20 r?stransky In GTK 3.20, gtk_menu_item_draw() just draws the root widget gadget, depending on the theme to style menu items with CSS name "separator" appropriately. MozReview-Commit-ID: 6AIxPzFe0Rg
f47148172a1bdebc0404e08bdb22a3ffcc894a93: Bug 1315386 - Make Safe Browsing code more shutdown-aware draft
Thomas Nguyen <tnguyen@mozilla.com> - Thu, 17 Nov 2016 11:40:25 +0800 - rev 440197
Push 36169 by tnguyen@mozilla.com at Thu, 17 Nov 2016 03:40:49 +0000
Bug 1315386 - Make Safe Browsing code more shutdown-aware * * * [mq]: 1315386_review MozReview-Commit-ID: J6pFlnAprJP * * * [mq]: 1315386_1_review MozReview-Commit-ID: LqomxZBVcTb
f3155dbec2aba7f5910844598f8c2f21836bd932: bug 1303964 draw only background and frame of separator menuitems in GTK versions > 3.20 r?stransky draft
Karl Tomlinson <karlt+@karlt.net> - Thu, 17 Nov 2016 11:08:33 +1300 - rev 440196
Push 36168 by ktomlinson@mozilla.com at Thu, 17 Nov 2016 03:39:50 +0000
bug 1303964 draw only background and frame of separator menuitems in GTK versions > 3.20 r?stransky MozReview-Commit-ID: 6AIxPzFe0Rg
19a2047755769bc1b9a718a74397038ab6249510: Bug 1315386 - Make Safe Browsing code more shutdown-aware draft
Thomas Nguyen <tnguyen@mozilla.com> - Thu, 17 Nov 2016 09:38:55 +0800 - rev 440195
Push 36167 by tnguyen@mozilla.com at Thu, 17 Nov 2016 03:39:40 +0000
Bug 1315386 - Make Safe Browsing code more shutdown-aware * * * [mq]: 1315386_review MozReview-Commit-ID: J6pFlnAprJP
f124ff2a7d2d96dba3d8767102bc10a21b0ac4b0: Bug 1313497 - Use InvokeAsync with Storages in GMPServiceParent - r?jya draft
Gerald Squelart <gsquelart@mozilla.com> - Sun, 13 Nov 2016 17:03:35 +1100 - rev 440194
Push 36166 by gsquelart@mozilla.com at Thu, 17 Nov 2016 03:37:59 +0000
Bug 1313497 - Use InvokeAsync with Storages in GMPServiceParent - r?jya MozReview-Commit-ID: LnbzlqQIWco
d47d2d11cb0fa452f11a4c6ccc45310dcbf35e27: Bug 1313497 - Use InvokeAsync with Storages in GMPParent - r?jya draft
Gerald Squelart <gsquelart@mozilla.com> - Sun, 13 Nov 2016 16:53:05 +1100 - rev 440193
Push 36166 by gsquelart@mozilla.com at Thu, 17 Nov 2016 03:37:59 +0000
Bug 1313497 - Use InvokeAsync with Storages in GMPParent - r?jya MozReview-Commit-ID: EQQFDzvAs8O
2ea6db40590615d6a9f23d1b539d42f0b352d98d: Bug 1313497 - AppendBufferTask can take SourceBufferAttributes by const& - r?jya draft
Gerald Squelart <gsquelart@mozilla.com> - Sun, 13 Nov 2016 16:39:47 +1100 - rev 440192
Push 36166 by gsquelart@mozilla.com at Thu, 17 Nov 2016 03:37:59 +0000
Bug 1313497 - AppendBufferTask can take SourceBufferAttributes by const& - r?jya A small optimization found while working on the previous patch. MozReview-Commit-ID: 4w2LI5mqUvS
c9ca4800f9746057e5c9e1c63b253f23149e70eb: Bug 1313497 - Use InvokeAsync with Storages in TrackBuffersManager - r?jya draft
Gerald Squelart <gsquelart@mozilla.com> - Sun, 13 Nov 2016 16:37:24 +1100 - rev 440191
Push 36166 by gsquelart@mozilla.com at Thu, 17 Nov 2016 03:37:59 +0000
Bug 1313497 - Use InvokeAsync with Storages in TrackBuffersManager - r?jya MozReview-Commit-ID: IkpuSyFgPbP
5450464def910309128d5fff18a5df349a6ddb4f: Bug 1313497 - Use InvokeAsync with Storages in MediaDecoderStateMachine - r?jya draft
Gerald Squelart <gsquelart@mozilla.com> - Sun, 13 Nov 2016 16:23:39 +1100 - rev 440190
Push 36166 by gsquelart@mozilla.com at Thu, 17 Nov 2016 03:37:59 +0000
Bug 1313497 - Use InvokeAsync with Storages in MediaDecoderStateMachine - r?jya Thanks to this, MediaDecoderStateMachine::Seek can take SeekTarget by const&. MozReview-Commit-ID: 97mLndCosQc
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip