9fc135ea3ff28578170b954bf726027c263ab82a: Bug 1304672: Group AsmJS and Wasm MIR/LIR nodes together in opcodes list; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:57:13 +0100 - rev 432760
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Group AsmJS and Wasm MIR/LIR nodes together in opcodes list; r?luke MozReview-Commit-ID: 531VPUXFnNY
b5b995dd4312d9ac5c1b86f7f103ffe43a7ccf71: Bug 1304672: Rename AsmJSParameter to WasmParameter and AsmJSPassStackArg to WasmStackArg; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:50:25 +0100 - rev 432759
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Rename AsmJSParameter to WasmParameter and AsmJSPassStackArg to WasmStackArg; r?luke MozReview-Commit-ID: KbZRJU79WvQ
a9b8e45c2677bb402c6d4ee73647dd321204fb93: Bug 1304672: Rename AsmJSReturn/AsmJSVoidReturn to WasmReturn/WasmReturnVoid; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:43:35 +0100 - rev 432758
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Rename AsmJSReturn/AsmJSVoidReturn to WasmReturn/WasmReturnVoid; r?luke MozReview-Commit-ID: 3Nc24K16JtI
717368e3d350a5fe40107347c3e60c1c03c2a972: Bug 1304672: WasmBaselineCompiler should refer to the renamed Wasm{Load,Store}GlobalVar; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:41:05 +0100 - rev 432757
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: WasmBaselineCompiler should refer to the renamed Wasm{Load,Store}GlobalVar; r?luke MozReview-Commit-ID: 79bHGrpDCXw
f8d5693e06c13090e5b31fd8d8592fc3468d8c3c: Bug 1304672: Rename AsmJSUnsignedToFloat32 to WasmUnsignedToFloat32; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:37:48 +0100 - rev 432756
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Rename AsmJSUnsignedToFloat32 to WasmUnsignedToFloat32; r?luke And LAsmJSUInt32ToFloat32 to LWasmUint32ToFloat32; MozReview-Commit-ID: EVbZZH8n0nP
00d77596bb8316f5db1adfa4efb59cf1fe204f8a: Bug 1304672: Rename AsmJSUnsignedToDouble to WasmUnsignedToDouble; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:33:46 +0100 - rev 432755
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Rename AsmJSUnsignedToDouble to WasmUnsignedToDouble; r?luke And also AsmJSUInt32ToDouble to WasmUint32ToDouble; MozReview-Commit-ID: Dz3dZmVNQLP
8e34835e5bfa790379ea1b5e43a0ac4f32e0a220: Bug 1304672: Rename AsmSelect to WasmSelect; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:24:29 +0100 - rev 432754
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Rename AsmSelect to WasmSelect; r?luke MozReview-Commit-ID: 2PJ0o69LHCx
28bd8f49db759dcc13105083b19b1296883fad6d: Bug 1304672: Rename AsmReinterpret to WasmReinterpret; r?luke draft
Benjamin Bouvier <benj@benj.me> - Wed, 02 Nov 2016 10:15:52 +0100 - rev 432753
Push 34416 by bbouvier@mozilla.com at Wed, 02 Nov 2016 18:00:01 +0000
Bug 1304672: Rename AsmReinterpret to WasmReinterpret; r?luke MozReview-Commit-ID: IykJQTtqunX
7e16a8ec76a006cd7ce0932155fc2c9dd5cb3c71: Bug 1314125 - Make PopupNotifications use tabbrowser's selectedBrowser frameloader instead of docShellIsActive to determine the currently selected tab. r?mikedeboer draft
Mike Conley <mconley@mozilla.com> - Mon, 31 Oct 2016 17:02:33 -0400 - rev 432752
Push 34415 by mconley@mozilla.com at Wed, 02 Nov 2016 17:54:28 +0000
Bug 1314125 - Make PopupNotifications use tabbrowser's selectedBrowser frameloader instead of docShellIsActive to determine the currently selected tab. r?mikedeboer See inline documentation for why I'm using the frameloader instead of just directly comparing the selectedBrowser to the browser requesting the prompt. MozReview-Commit-ID: D9ahuth6eLC
151b7ba93a46601fedbfd60e8cc3fb2170ba2d8d: Backed out changeset 30e050c04c4e draft
Mike Conley <mconley@mozilla.com> - Mon, 31 Oct 2016 16:12:51 -0400 - rev 432751
Push 34415 by mconley@mozilla.com at Wed, 02 Nov 2016 17:54:28 +0000
Backed out changeset 30e050c04c4e MozReview-Commit-ID: HLTpejFKnY9
2c6411ed035e3f9bd935c00ee916a7ca40cc81fd: Bug 1221764 - Implement simple chrome.bookmarks events, r?aswan draft
Tom Schuster <evilpies@gmail.com> - Wed, 17 Aug 2016 10:22:10 -0400 - rev 432750
Push 34414 by bmo:bob.silverberg@gmail.com at Wed, 02 Nov 2016 17:53:28 +0000
Bug 1221764 - Implement simple chrome.bookmarks events, r?aswan MozReview-Commit-ID: LWbhYf8CpZD
fc81c0ff7b25ac5cda6da2c6e1f437cbdfdb27b4: Bug 1297651 - Move toolsidebar.js into tabbar.js and make it more generic r?honza draft
Michael Ratcliffe <mratcliffe@mozilla.com> - Wed, 02 Nov 2016 16:16:54 +0000 - rev 432749
Push 34413 by bmo:mratcliffe@mozilla.com at Wed, 02 Nov 2016 17:51:06 +0000
Bug 1297651 - Move toolsidebar.js into tabbar.js and make it more generic r?honza We were previously working at cross purposes as I thought Honza wanted me to use high order functions to compose and decorate the components. Having asked and gained clarification I understand that Honza wanted me to pass the extra methods in using props. Actually, it is quite tidy this way. MozReview-Commit-ID: 58qJ6C0Lsof
6dde37479303f822bcf42fa5a07fa2a26455cd89: Bug 1020516 - Add timestamp messages when dumping buffered messages in mochitest, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 02 Nov 2016 13:42:58 -0400 - rev 432748
Push 34412 by ahalberstadt@mozilla.com at Wed, 02 Nov 2016 17:48:13 +0000
Bug 1020516 - Add timestamp messages when dumping buffered messages in mochitest, r?ted When dumping buffered messages in mochitest, this adds a new log line for every second's worth of messages. Alternatively we could print the timestamp in brackets at the end of each buffered message, but I found that in practice there tends to be many log messages generated each second. This looks better for that case, but will look much worse if logs are generated more than a second apart. I would be ok with either method. MozReview-Commit-ID: Jkd9hOlmiGZ
f92525e7529017a2101075ebdf7cc4772fb44a8e: Bug 1020516 - Only buffer mochitest log messages that happen between a TEST-START/TEST-END, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 02 Nov 2016 13:42:58 -0400 - rev 432747
Push 34412 by ahalberstadt@mozilla.com at Wed, 02 Nov 2016 17:48:13 +0000
Bug 1020516 - Only buffer mochitest log messages that happen between a TEST-START/TEST-END, r?ted I believe the current behaviour of buffering messages outside of a test is wrong. For example: 1. INFO logged -> gets buffered 2. TEST-START logged -> doesn't get buffered 3. Test fails and buffer dumped -> INFO looks like it happened after the TEST-START I think this is very confusing as developers trying to debug a test will think that INFO message is happening somewhere inside their test when in reality it isn't. MozReview-Commit-ID: Jkd9hOlmiGZ
3f9a1c9a6901d3b964568df670d598926b10e195: Bug 1020516 - Pass options.quiet into mochitest MessageLogger via constructor, r?ted draft
Andrew Halberstadt <ahalberstadt@mozilla.com> - Wed, 02 Nov 2016 13:42:57 -0400 - rev 432746
Push 34412 by ahalberstadt@mozilla.com at Wed, 02 Nov 2016 17:48:13 +0000
Bug 1020516 - Pass options.quiet into mochitest MessageLogger via constructor, r?ted For some reason we have a 'buffering' parameter in the MessageLogger constructor, but then rather than using this, the mochitest harness modifies state after instantiation. Using the constructor is easier to understand, and simplifies some of the logic in the next couple of patches. MozReview-Commit-ID: Jkd9hOlmiGZ
d8f869412f43dff35104772b52ee39e308b340a0: Bug 1306196-[P2] Provide RemoteMediaDrmBridge & corresponding stub to underlying GeckoMediaDrmBridge implementation. draft
Kilik Kuo <kikuo@mozilla.com> - Tue, 01 Nov 2016 23:46:34 +0800 - rev 432745
Push 34411 by kikuo@mozilla.com at Wed, 02 Nov 2016 17:40:05 +0000
Bug 1306196-[P2] Provide RemoteMediaDrmBridge & corresponding stub to underlying GeckoMediaDrmBridge implementation. MozReview-Commit-ID: K49zWmuJOpt
c70322bf55cbff9c656a577a04eeed5db4d03912: Bug 1306196-[P1] Provide AIDL definiion for EME functionality on Fennec MediaManager Service. draft
Kilik Kuo <kikuo@mozilla.com> - Tue, 01 Nov 2016 19:27:18 +0800 - rev 432744
Push 34411 by kikuo@mozilla.com at Wed, 02 Nov 2016 17:40:05 +0000
Bug 1306196-[P1] Provide AIDL definiion for EME functionality on Fennec MediaManager Service. MozReview-Commit-ID: IPr9WQQbGNB
b9a752914bc24f763e6e448e27d3cfaf4a1bd2da: Bug 1314343: Turn on no-unreachable in eslint. r?standard8 draft
Dave Townsend <dtownsend@oxymoronical.com> - Tue, 01 Nov 2016 10:58:35 -0700 - rev 432743
Push 34410 by dtownsend@mozilla.com at Wed, 02 Nov 2016 17:29:13 +0000
Bug 1314343: Turn on no-unreachable in eslint. r?standard8 Unreachable code can be a sign of a mistake so we should turn this rule on. MozReview-Commit-ID: LQphsNL7HBX
41f714091cb0f752eeeb9f5fcef0983654022995: Bug 1249710: calculate scrollable range using Viewport, not CompositionBounds r=botond draft
Kevin Wern <kevin.m.wern@gmail.com> - Wed, 02 Nov 2016 04:45:09 -0400 - rev 432742
Push 34409 by bmo:kevin.m.wern@gmail.com at Wed, 02 Nov 2016 17:25:31 +0000
Bug 1249710: calculate scrollable range using Viewport, not CompositionBounds r=botond Using CompositionBounds causes APZ scrolling to halt prematurely before reaching the bottom. This can be caused by two things: when the composition bounds extend past the viewport, or when the scrollable rect is zoomed (CompositionBounds is a ParentLayerRect, Viewport is a CSSRect taking this transformation into account). MozReview-Commit-ID: Ec9cOMP1cdT
d983239cffc9181e59e396eabccefc39b69494c6: Bug 1306185-[Part3] Provide LocalMediaDrmBrdige as an intermediate which is the entry to actual GeckoMediaDrmBridge implementation. draft
Kilik Kuo <kikuo@mozilla.com> - Tue, 01 Nov 2016 19:16:17 +0800 - rev 432741
Push 34408 by kikuo@mozilla.com at Wed, 02 Nov 2016 16:56:41 +0000
Bug 1306185-[Part3] Provide LocalMediaDrmBrdige as an intermediate which is the entry to actual GeckoMediaDrmBridge implementation. MozReview-Commit-ID: I9NH0ibGdEn
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip