444fb7b29a2eaa650bfd7a2aadac0cf5973ce892: Bug 1464647 - Add web platform tests affected by the smarter interpolation of transform list. r=birtles
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 29 May 2018 12:33:14 +0900 - rev 420173
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1464647 - Add web platform tests affected by the smarter interpolation of transform list. r=birtles MozReview-Commit-ID: 4nYK6UROK6f
f79ea1a6633dc7a3716b8a9f4716fc7ba3fe0e2e: Bug 1464947 - Fix ReflowInput::DisplayInitFrameTypeExit display type logging. r=gerald
Cameron McCormack <cam@mcc.id.au> - Tue, 29 May 2018 12:39:22 +1000 - rev 420172
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1464947 - Fix ReflowInput::DisplayInitFrameTypeExit display type logging. r=gerald MozReview-Commit-ID: 4xPXJkys1so
60a74d5d7904c7c3cbd4a703a8b0553fa35fdfa1: Bug 1462703 - Additional setElementCreationCallback tests in XUL document r=smaug
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 14:13:22 +0800 - rev 420171
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1462703 - Additional setElementCreationCallback tests in XUL document r=smaug These tests ensures the feature interacts well with our setup in XUL. They work when bug 1460815 was implemented so they sits in its own changeset. MozReview-Commit-ID: Ia08tAewZyN
af3d1bc9c49295366b224a3f84c214e23f4bbb4e: Bug 1462703 - Upgrade the created element after callback runs r=smaug
Timothy Guan-tin Chien <timdream@gmail.com> - Wed, 23 May 2018 13:04:18 +0800 - rev 420170
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1462703 - Upgrade the created element after callback runs r=smaug nsContentUtils::NS_NewXULOrHTMLElement will call into CustomElementRegisty::RegisterCallbackUpgradeElement, which keeps the newly created element, allowing RunCustomElementCreationCallback to upgrade them after the callback runs. It is unclear if this changes the order of constructor executions, but even so it should not affact our use case. MozReview-Commit-ID: LWTn7B35aBv
034c16b7efa2790fcd915fa551be266121cca8a3: Bug 1462703 - Set returned CustomElementDefinition again after script runner is set r=smaug
Timothy Guan-tin Chien <timdream@gmail.com> - Tue, 22 May 2018 07:30:07 +0800 - rev 420169
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1462703 - Set returned CustomElementDefinition again after script runner is set r=smaug This would help in the case where it is safe to run script in-place and the CustomElementDefinition is available before the function exits. This fixes the tests changed. MozReview-Commit-ID: Ays91W94WZm
8ecc66673444ad381cff10f7de70ae93d15e0a8e: Bug 1457373 - Remove text-combine-upright digits option - r=xidorn
Gerald Squelart <gsquelart@mozilla.com> - Thu, 17 May 2018 15:29:17 +1000 - rev 420168
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1457373 - Remove text-combine-upright digits option - r=xidorn MozReview-Commit-ID: Ehzsd2rmBER
d6ea05eb01acf069053ef0dd242757ff8be81ff3: Bug 1417784 - Properly implement SyncWithCompositor for WebRender. r=froydnj,sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 28 May 2018 11:29:52 -0400 - rev 420167
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1417784 - Properly implement SyncWithCompositor for WebRender. r=froydnj,sotaro This defines three flushing functions that flush different parts of the WR pipeline. Using all three guarantees that everything sent to WR will have been flushed. This is what we need to do in SyncWithCompositor to ensure that it meets the API contract. In addition, this patch updates the existing FlushRendering function to use the new functions (no functional changes intended here). MozReview-Commit-ID: GzxwpF4JT04
6a1252b68f4f6dadc9b7ee5698cc4067f43e9368: Bug 1417784 - Shift how the AsyncImagePipelineManager is notified of updates. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 28 May 2018 11:29:41 -0400 - rev 420166
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1417784 - Shift how the AsyncImagePipelineManager is notified of updates. r=sotaro Instead of notifying the AsyncImagePipelineManager on the compositor thread via the CompositorBridgeParent, we can send it the new pipeline info directly from the RenderThread after the update happens. This effectively splits the AsyncImagePipelineManager update-processing into two parts: one that takes in the new pipeline info and one that process it. This allows us to invoke the processing step from other code running on the compositor thread, which we will need to do in the next patch. MozReview-Commit-ID: 7xhm8I7bY4C
d6fd83af52c313c06791a7d83a2a88d1fb9c1e72: Bug 1417784 - Use a CompositorBridgeParent* instead of a base class pointer. r=sotaro
Kartikaya Gupta <kgupta@mozilla.com> - Mon, 28 May 2018 11:29:41 -0400 - rev 420165
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1417784 - Use a CompositorBridgeParent* instead of a base class pointer. r=sotaro We do a silent upcast from CompositorBridgeParent* to the base class and pass it around as a CompositorBridgeParentBase* for no reason. Avoiding this simplifies the code slightly and avoids virtual function overhead. We do need to move a couple of functions in CompositorBridgeParent from protected scope to public scope. MozReview-Commit-ID: 9Zq3GwxEXpr
f620bf59c952171ad45d9b4ccca3fe7231ebf818: Bug 1461118 - Null-check mGeckoChild after calling DispatchInputEvent. r=spohl
Markus Stange <mstange@themasta.com> - Mon, 28 May 2018 18:00:35 -0400 - rev 420164
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1461118 - Null-check mGeckoChild after calling DispatchInputEvent. r=spohl MozReview-Commit-ID: 4bfe8TM4GuS
d29d89978c45cb879cba002eb8b4d80cd62bd92f: Bug 1455300 - Part 2: Include hidden tabs in the History menu r=mak
Mark Striemer <mstriemer@mozilla.com> - Thu, 10 May 2018 16:01:36 -0500 - rev 420163
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1455300 - Part 2: Include hidden tabs in the History menu r=mak MozReview-Commit-ID: 8sKrAJVIAD5
db492c0538daad7be70857c9fdd9a88f5034476d: Bug 1455300 - Part 1: Extract tab menuitem code from tabbrowser.xml r=dao
Mark Striemer <mstriemer@mozilla.com> - Mon, 14 May 2018 15:10:01 -0500 - rev 420162
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1455300 - Part 1: Extract tab menuitem code from tabbrowser.xml r=dao MozReview-Commit-ID: LP0EZxe5cJ9
f53afd7c76808e464c0ddcba48f26368a644e4ee: Merge mozilla-central to autoland. a=merge CLOSED TREE
Ciure Andrei <aciure@mozilla.com> - Tue, 29 May 2018 00:56:16 +0300 - rev 420161
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Merge mozilla-central to autoland. a=merge CLOSED TREE
0c2627e0a4de5cc82f58510cf40395f4f960faf1: Bug 1462783 - Artifact raptor test results in treeherder; r=ahal
Rob Wood <rwood@mozilla.com> - Thu, 24 May 2018 10:50:39 -0400 - rev 420160
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1462783 - Artifact raptor test results in treeherder; r=ahal MozReview-Commit-ID: FYXU2nVhn3n
c88026f3d867a833f41021953e928d896a021489: Bug 1449232 - Sort listeners by event name in the listener list r=pbro
Michael Ratcliffe <mratcliffe@mozilla.com> - Fri, 25 May 2018 16:03:13 +0100 - rev 420159
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1449232 - Sort listeners by event name in the listener list r=pbro The only real change is the sorting inside `devtools/server/actors/inspector/node.js`. The rest is just shuffling tests around to handle the sorted listeners. MozReview-Commit-ID: 8ql1bRbr4Pl
73aef553df3ddcf1942cd2795787a47b58c8917e: Bug 1454232 - Use toolbarbutton-attention-fill for syncing animation. r=dao
Tim Nguyen <ntim.bugs@gmail.com> - Sun, 27 May 2018 20:32:19 +0200 - rev 420158
Push 34066 by shindli@mozilla.com at Tue, 29 May 2018 09:51:43 +0000
Bug 1454232 - Use toolbarbutton-attention-fill for syncing animation. r=dao MozReview-Commit-ID: 87V68Vud2ep
35aa0dde259f5f51c0aaf86935a54b8087c2e8c6: Merge inbound to mozilla-central. a=merge
Ciure Andrei <aciure@mozilla.com> - Tue, 29 May 2018 00:53:52 +0300 - rev 420157
Push 34065 by aciure@mozilla.com at Mon, 28 May 2018 21:54:18 +0000
Merge inbound to mozilla-central. a=merge
2ee8bb4a4b7c9c7d4b6b2d7589b302807c39bedc: Bug 1464866 - Fix a typo in Android time-out message; r=me,a=test-only
Geoff Brown <gbrown@mozilla.com> - Mon, 28 May 2018 11:29:34 -0600 - rev 420156
Push 34065 by aciure@mozilla.com at Mon, 28 May 2018 21:54:18 +0000
Bug 1464866 - Fix a typo in Android time-out message; r=me,a=test-only
f0a6c51844657701662886c0102f6a4ef9d56835: Backed out changeset 188dc519bc48 (bug 1464635) r=backout
Kris Maglione <maglione.k@gmail.com> - Mon, 28 May 2018 07:47:30 -0700 - rev 420155
Push 34065 by aciure@mozilla.com at Mon, 28 May 2018 21:54:18 +0000
Backed out changeset 188dc519bc48 (bug 1464635) r=backout MozReview-Commit-ID: JrR4q5Rwyqi
91a5de2fb8caaca309135530395590ffdbfdcd71: Bug 1464656 - Enable WebAssembly.Global by default. r=lth.
Julian Seward <jseward@acm.org> - Mon, 28 May 2018 14:51:04 +0200 - rev 420154
Push 34065 by aciure@mozilla.com at Mon, 28 May 2018 21:54:18 +0000
Bug 1464656 - Enable WebAssembly.Global by default. r=lth. WebAssembly.Global is currently nightly- and early-beta-only, gated by ENABLE_WASM_GLOBAL and EARLY_BETA_OR_EARLIER respectively. This bug is to enable it by default. * js/src/moz.build: js/src/shell/moz.build: js/src/jsapi-tests/moz.build: Don't define ENABLE_WASM_GLOBAL. * js/src/wasm/WasmJS.cpp: js/src/wasm/WasmModule.cpp: js/src/wasm/WasmValidate.cpp: Un-guard code guarded by #if defined(ENABLE_WASM_GLOBAL) && defined(EARLY_BETA_OR_EARLIER) and remove code guarded by its negation. Inside js/src, the two symbols are only ever used together, so there's no need to consider them separately. * js/src/jit-test/tests/wasm/globals.js: js/src/jit-test/tests/wasm/spec/harness/index.js: Remove code guarded by (typeof WebAssembly.Global === "undefined") and un-guard code guarded by (typeof WebAssembly.Global === "function") * js/src/jit-test/tests/wasm/spec/globals.wast.js: js/src/jit-test/tests/wasm/spec/linking.wast.js: Make these be the same as spec/proposal_mutable_global/globals.wast.js and spec/proposal_mutable_global/linking.wast.js respectively. * js/src/jit-test/tests/wasm/spec/proposal_mutable_global/globals.wast.js: js/src/jit-test/tests/wasm/spec/proposal_mutable_global/linking.wast.js: js/src/jit-test/tests/wasm/spec/proposal_mutable_global/directives.txt: js/src/jit-test/tests/wasm/spec/proposal_mutable_global (directory): Deleted.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip