searching for reviewer(smaug)
80a34446b74a: Bug 1510985 - Remove Event.returnValue temporarily in 64. r=smaug a=jcristau FIREFOX_64_0_BUILD1
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 03 Dec 2018 15:24:39 -0500 - rev 501449
Push 1867 by jcristau@mozilla.com at Mon, 03 Dec 2018 20:26:53 +0000
Bug 1510985 - Remove Event.returnValue temporarily in 64. r=smaug a=jcristau Event.returnValue causes breaking a bank application. The reason of the breakage is, the web app assumes that Event.returnValue is available only on IE and it hits same incompatibility issue with window.event (bug 1479964). Additionally, the app may be used in various domains including in intranet. Therefore, we cannot disable it with blacklist of domains like other similar changes. Fortunately, we can ship new keypress event behaviors which is tracked by bug 1479964 in 65. So, for backward compatibility with 62 or earlier, we should temporarily disable Event.returnValue in 64. But unfortunately, this was introduced in 63. So, if some web apps have started to use this legacy attribute, we need to contact their vendors, though.
5856e2411504: Bug 1510985 - Remove Event.returnValue temporarily in 64. r=smaug a=jcristau
Masayuki Nakano <masayuki@d-toybox.com> - Mon, 03 Dec 2018 11:23:38 -0500 - rev 501441
Push 1865 by jcristau@mozilla.com at Mon, 03 Dec 2018 16:48:50 +0000
Bug 1510985 - Remove Event.returnValue temporarily in 64. r=smaug a=jcristau Event.returnValue causes breaking a bank application. The reason of the breakage is, the web app assumes that Event.returnValue is available only on IE and it hits same incompatibility issue with window.event (bug 1479964). Additionally, the app may be used in various domains including in intranet. Therefore, we cannot disable it with blacklist of domains like other similar changes. Fortunately, we can ship new keypress event behaviors which is tracked by bug 1479964 in 65. So, for backward compatibility with 62 or earlier, we should temporarily disable Event.returnValue in 64. But unfortunately, this was introduced in 63. So, if some web apps have started to use this legacy attribute, we need to contact their vendors, though.
3bf260797a32: Bug 1504179 - Trigger first spell-checking by moving focus to contenteditable element. r=smaug, a=test-only
Edgar Chen <echen@mozilla.com> - Wed, 14 Nov 2018 12:38:46 +0000 - rev 501267
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1504179 - Trigger first spell-checking by moving focus to contenteditable element. r=smaug, a=test-only The current test has an incorrect expectation for the first full spell-checking, it actually happens when first-time focus moves to contenteditable element (which trigger dictionary updating), not right after document loaded. Differential Revision: https://phabricator.services.mozilla.com/D11463
f9639e65bc99: Bug 1497480 - Part 3: Add tests for spell-checking in ShadowDOM; r=smaug a=jcristau
Edgar Chen <echen@mozilla.com> - Fri, 02 Nov 2018 00:07:30 +0000 - rev 501043
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497480 - Part 3: Add tests for spell-checking in ShadowDOM; r=smaug a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D9802
ad24ecd2dd39: Bug 1497480 - Part 2: Make spellchecking to work in ShadowDOM after anchor navigates away from it; r=smaug a=jcristau
Edgar Chen <echen@mozilla.com> - Fri, 02 Nov 2018 00:07:30 +0000 - rev 501042
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497480 - Part 2: Make spellchecking to work in ShadowDOM after anchor navigates away from it; r=smaug a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D9543
fa8dfa3aef26: Bug 1497480 - Part 1: Set the root for spelling checker to shadow root if the contenteditable nodes are in the shadow DOM; r=smaug a=jcristau
Edgar Chen <echen@mozilla.com> - Fri, 02 Nov 2018 00:07:30 +0000 - rev 501041
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497480 - Part 1: Set the root for spelling checker to shadow root if the contenteditable nodes are in the shadow DOM; r=smaug a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D9542
4c7bbc4c6fbc: Bug 1478171 - [1.0] Forward channel redirect to nsILoadURIDelegate to allow external handling. r=snorp,smaug, a=RyanVM
Eugen Sawin <esawin@mozilla.com> - Wed, 31 Oct 2018 16:16:28 -0500 - rev 501032
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1478171 - [1.0] Forward channel redirect to nsILoadURIDelegate to allow external handling. r=snorp,smaug, a=RyanVM
640c972a31a3: Bug 1500011 - Use CheckedInt more in CalculateBufferSizeForImage. r=smaug, a=RyanVM
Nika Layzell <nika@thelayzells.com> - Thu, 18 Oct 2018 16:20:03 -0400 - rev 500822
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1500011 - Use CheckedInt more in CalculateBufferSizeForImage. r=smaug, a=RyanVM Differential Revision: https://phabricator.services.mozilla.com/D9145
e8cd0248b93c: Bug 1499996 - Wait to run tests until new window gets focus. r=smaug, a=test-only
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 23 Oct 2018 07:34:55 +0000 - rev 500810
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1499996 - Wait to run tests until new window gets focus. r=smaug, a=test-only test_expanding_selection_per_page.html creates another window and requires focus event on each case which creates editing host because EditorEventListener::Focus() sets ancestor limit of Selection as the editing host. Therefore, if the window itself does not have focus, focus event won't be fired on editing hosts. So, the reason why the orange occurs almost all with opt build is, debug build is enough slow to wait focus of new window before running test. Differential Revision: https://phabricator.services.mozilla.com/D9473
140a56e90594: Bug 1499792: Remove unneeded 'ThrottledEventQueue' forward declarations. r=smaug
Jim Blandy <jimb@mozilla.com> - Thu, 18 Oct 2018 12:20:14 +0000 - rev 500685
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1499792: Remove unneeded 'ThrottledEventQueue' forward declarations. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D9008
394a1e5544f6: Bug 1486888 - Support XUL broadcasters in non-XUL documents. r=smaug
Brendan Dahl <bdahl@mozilla.com> - Fri, 19 Oct 2018 01:22:46 +0000 - rev 500479
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1486888 - Support XUL broadcasters in non-XUL documents. r=smaug The majority of the XUL broadcaster logic is moved out of XULDocument and into a separate class (XULBroadcastManager). The hookup points for when listeners need to be created and listeners need to be notified is now handled by the XULElement itself and nsDocument. To avoid any overhead, the XULBroadcastManager is only ever created when a document uses a listener. The new approach does have the disadvantage that broadcasting can now only work with XULElements, but going forward we'd like to discontinue this feature and rely on MutationObservers to implement similar things. One test had to be modified to use XUL elements instead of HTML elements because of the reason noted above. Differential Revision: https://phabricator.services.mozilla.com/D8888
02a07fe87808: Bug 1482425 - PresShell::PageMove() should use different rules to look for a container element for aExtend value r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 18 Oct 2018 04:42:53 +0000 - rev 500313
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1482425 - PresShell::PageMove() should use different rules to look for a container element for aExtend value r=smaug PresShell::PageMove() climbs up to parent document when there is no scrollable parent in current document. However, if aExtend is true, it should expand Selection in the document itself. Therefore, it needs different rules to look for container of expanding Selection from scrollable element to scroll. Additionally, old rules (i.e., before the fix of bug 1369072 which caused this regression) were also buggy. It used parent scrollable element or root scrollable element simply. Therefore, if found scrollable element is ancestor of selection limiter, it didn't work as expected. This patch creates nsFrameSelection::GetFrameToPageSelect() to retrieve per-page selection container element with the following rules: - look for a scrollable element in selection limiter. - if there is no scrollable element, use selection limiter. - if there is no selection limiter, use the root frame. So, nsFrameSelection::CommonPageMove() should take nsIFrame rather than nsIScrollableFrame since container of per-page selection may be used in non-scrollable contenteditable element. If it's called with non-scrollable frame, it needs to compute the expanding range with the frame size. Differential Revision: https://phabricator.services.mozilla.com/D8954
1249680014b0: Bug 1499473: Simplify TabGroup a bit, now that ThrottledEventQueue::Create is infallible. r=smaug
Jim Blandy <jimb@mozilla.com> - Wed, 17 Oct 2018 20:41:59 +0000 - rev 500276
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1499473: Simplify TabGroup a bit, now that ThrottledEventQueue::Create is infallible. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D8915
7b427b166742: Bug 1498860 - Add window.screenLeft / window.screenTop as aliases of screenX / screenY. r=smaug
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 17 Oct 2018 02:20:15 +0000 - rev 500038
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1498860 - Add window.screenLeft / window.screenTop as aliases of screenX / screenY. r=smaug Tests are at https://github.com/web-platform-tests/wpt/pull/13543. Spec is waiting on those, but this matches all other browsers. Differential Revision: https://phabricator.services.mozilla.com/D8917
f2e35ed6a692: Bug 1497601 - Use a xul:description instead of a xul:label for tooltips;r=smaug
Brian Grinstead <bgrinstead@mozilla.com> - Tue, 16 Oct 2018 13:54:07 +0000 - rev 499916
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497601 - Use a xul:description instead of a xul:label for tooltips;r=smaug We'd like to be able to implement label features with a Custom Element, and we don't want to run CE reactions inside of NAC. Differential Revision: https://phabricator.services.mozilla.com/D8241
9508a03be7c2: Bug 1258143 - Remove LocalMediaStream. r=jib,smaug
Andreas Pehrson <apehrson@mozilla.com> - Mon, 15 Oct 2018 08:17:07 +0000 - rev 499755
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1258143 - Remove LocalMediaStream. r=jib,smaug Differential Revision: https://phabricator.services.mozilla.com/D8064
b32ff85f2224: Bug 1435789: implement relayProtocol for localcandidate stats r=smaug,ng
Philipp Hancke <fippo@appear.in> - Sun, 07 Oct 2018 07:42:48 +0000 - rev 499604
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1435789: implement relayProtocol for localcandidate stats r=smaug,ng relayProtocol is the standardized variant of mozLocalTransport. Spec: https://w3c.github.io/webrtc-stats/#dom-rtcicecandidatestats-relayprotocol IDL: https://w3c.github.io/webrtc-stats/#icecandidate-dict* Differential Revision: https://phabricator.services.mozilla.com/D3428
905c871bcf03: Bug 1258143 - Remove LocalMediaStream. r=jib,smaug
Andreas Pehrson <apehrson@mozilla.com> - Thu, 11 Oct 2018 12:43:34 +0000 - rev 499322
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1258143 - Remove LocalMediaStream. r=jib,smaug Differential Revision: https://phabricator.services.mozilla.com/D8064
bb32faa290f0: Bug 1377146 - Remove AudioStreamTrack and VideoStreamTrack from js. r=jib,smaug
Andreas Pehrson <apehrson@mozilla.com> - Thu, 11 Oct 2018 15:36:11 +0000 - rev 499305
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1377146 - Remove AudioStreamTrack and VideoStreamTrack from js. r=jib,smaug Differential Revision: https://phabricator.services.mozilla.com/D8063
ccdfe4ca1f88: Bug 1498445 - Stop creating a style attribute for invalid property values. r=smaug
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 12 Oct 2018 09:07:00 +0000 - rev 499300
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1498445 - Stop creating a style attribute for invalid property values. r=smaug This matches all other browsers, and the spec. Added an explicit test for this, and a test that tests what cssstyledeclaration-mutationrecord-002.html wanted to test, which is that changing an existing declaration doesn't generate a mutation record. Differential Revision: https://phabricator.services.mozilla.com/D8500
8aef0f43b2d8: Bug 934425 - Add SinkId in webidl for HTMLMediaElement. r=smaug
Alex Chronopoulos <achronop@gmail.com> - Fri, 12 Oct 2018 08:44:55 +0000 - rev 499290
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 934425 - Add SinkId in webidl for HTMLMediaElement. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D5873
858b41d7b9ed: Bug 1484849 - history.go(0) should reload the current page and not involve the entire session history r=smaug
Perry Jiang <perry@mozilla.com> - Thu, 11 Oct 2018 15:43:25 +0000 - rev 499212
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1484849 - history.go(0) should reload the current page and not involve the entire session history r=smaug Differential Revision: https://phabricator.services.mozilla.com/D8322
cecf523a14b1: Bug 1263734: Implement ServiceWorkerContainer.startMessages() r=asuth,smaug
Yaron Tausky <ytausky@mozilla.com> - Thu, 11 Oct 2018 12:37:37 +0000 - rev 499144
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1263734: Implement ServiceWorkerContainer.startMessages() r=asuth,smaug Differential Revision: https://phabricator.services.mozilla.com/D4237
55588bdd2ee8: Bug 1497831 - Use nsTArray instead of nsIArray for nsIFormatConverter. r=smaug
Tom Schuster <evilpies@gmail.com> - Wed, 10 Oct 2018 20:26:06 +0000 - rev 499071
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497831 - Use nsTArray instead of nsIArray for nsIFormatConverter. r=smaug Depends on D8194 Differential Revision: https://phabricator.services.mozilla.com/D8195
2852663b840e: Bug 1497831 - Use nsTArray instead of nsIArray for nsITransferable. r=smaug
Tom Schuster <evilpies@gmail.com> - Wed, 10 Oct 2018 20:25:54 +0000 - rev 499070
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497831 - Use nsTArray instead of nsIArray for nsITransferable. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D8194
2c01f22661fa: Bug 1263734: Implement ServiceWorkerContainer.startMessages() r=asuth,smaug
Yaron Tausky <ytausky@mozilla.com> - Wed, 10 Oct 2018 13:55:23 +0000 - rev 498978
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1263734: Implement ServiceWorkerContainer.startMessages() r=asuth,smaug Differential Revision: https://phabricator.services.mozilla.com/D4237
d56cf859abf7: Bug 1363508 - Part 3: Spoofing navigator.maxTouchPoints into 0 if fingerprinting resistance is enabled r=arthuredelstein,masayuki,smaug
Tim Huang <tihuang@mozilla.com> - Tue, 09 Oct 2018 11:50:03 +0000 - rev 498972
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1363508 - Part 3: Spoofing navigator.maxTouchPoints into 0 if fingerprinting resistance is enabled r=arthuredelstein,masayuki,smaug The maxTouchPoints is going to review the detail of users' hardware. So, we will spoof it into 0 if fingerprinting resistance is on. Depends on D6004 Differential Revision: https://phabricator.services.mozilla.com/D6005
3e9933f36e45: Bug 1363508 - Part 1: Spoofing pen/touch pointer events into mouse pointer events when fingerprinting resistance is on r=arthuredelstein,masayuki,smaug
Tim Huang <tihuang@mozilla.com> - Tue, 09 Oct 2018 11:55:43 +0000 - rev 498970
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1363508 - Part 1: Spoofing pen/touch pointer events into mouse pointer events when fingerprinting resistance is on r=arthuredelstein,masayuki,smaug The pointerType field in the pointer event will reveal the details of users' hardware; this is a fingerprinting vector. So, we would spoof all types of pointer events into mouse type pointer events for protecting users from browser fingerprinting when fingerprinting resistance is on. In this patch, we would spoof the pointerType as well as other fields that mouse pointer events don't support, like pressure, tiltX/Y and so on when fingerprinting resistance is on. Differential Revision: https://phabricator.services.mozilla.com/D6003
9e84f8d5b086: Bug 1461708 - part 8: Make EventStateManager handle middle click paste as a default action of mouseup event r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:06:17 +0000 - rev 498899
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 8: Make EventStateManager handle middle click paste as a default action of mouseup event r=smaug This patch makes EventStateManager handle middle click paste as a default action. Unfortunately, we cannot remove the call of HandleMiddleClickPaste() in EditorEventListener because it's important to consume middle click event before any elements in the editor. For example, if clicked HTMLEditor has non-editable <a href> element, middle click event needs to be handled by the editor rather than contentAreaUtils which handles click events of <a href> elements. The cause of this kind of issues is, any click event handlers which handle non-primary button events still listen to "click" events. Therefore, this patch makes HandleMiddleClickPaste() do nothing if the mouseup event is fired on an editor. Differential Revision: https://phabricator.services.mozilla.com/D7855
0f2549de4e47: Bug 1461708 - part 7: Make EventStateManager::HandleMiddleClickPaste() dispatch ePaste event by itself r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:05:39 +0000 - rev 498898
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 7: Make EventStateManager::HandleMiddleClickPaste() dispatch ePaste event by itself r=smaug This is preparation of the last patch. Even if no editor is clicked with middle button, we need to do: - collapse Selection at the clicked point. - dispatch "paste" event. Therefore, HandleMiddleClickPaste() should dispatch ePaste event by itself and each editor methods should have a bool argument which the caller wants ePaste event automatically. Note that Chromium dispatches "paste" event and pastes clipboard content into clicked editor even if preceding "auxclick" event is consumed. However, our traditional behavior is not dispatching "paste" event nor pasting clipboard content. Unless Chromium developer keeps their odd behavior, we should keep our traditional behavior since our behavior is conforming to DOM event model. Differential Revision: https://phabricator.services.mozilla.com/D7854
95d15775e123: Bug 1461708 - part 5: Move EditorEventListener::HandleMiddleClickPaste() to EventStateManager r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:04:17 +0000 - rev 498896
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 5: Move EditorEventListener::HandleMiddleClickPaste() to EventStateManager r=smaug EventStateManager needs to handle middle click paste without editor. Therefore, the handler should be in EventStateManager. Differential Revision: https://phabricator.services.mozilla.com/D7852
219527f4c312: Bug 1461708 - part 4: Move implementation of UIEvent::GetRangeParent() and UIEvent::RangeOffset() to nsLayoutUtils r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:03:34 +0000 - rev 498895
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 4: Move implementation of UIEvent::GetRangeParent() and UIEvent::RangeOffset() to nsLayoutUtils r=smaug We need to move EditorEventListener::HandleMiddleClickPaste() into EventStateManager to handle middle click paste after all click events are dispatched. This is preparation of the change. HandleMiddleClickPaste() uses UIEvent::GetRangeParent() and UIEvent::RangeOffset() to collapse Selection at clicked point. However, EventStateManager cannot access them since EventStateManager can handle it with WidgetMouseEvent. Fortunately, only WidgetMouseEvent is necessary for implementing them. Therefore, we can move the implementation into nsLayoutUtils and merge them. Differential Revision: https://phabricator.services.mozilla.com/D7851
d61721276fcc: Bug 1461708 - part 3: EventStateManager::InitAndDispatchClickEvent() shouldn't overwrite nsEventStatus with nsEventStatus_eIgnore r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:02:50 +0000 - rev 498894
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 3: EventStateManager::InitAndDispatchClickEvent() shouldn't overwrite nsEventStatus with nsEventStatus_eIgnore r=smaug EventStateManager::InitAndDispatchClickEvent() sends given nsEventStatus to nsIPresShell::HandleEventWithTarget(). Then, it sends the status to EventStateManager::PreHandleEvent() before dispatching the event. At this time, EventStateManager::PreHandleEvent() resets the state to nsEventStatus_eIgnore. Therefore, for example, if eMouseClick event is consumed but eMouseAuxClick is ignored, the event status result is nsEventStatus_eIgnore. So, neither DispatchClickEvents() nor PostMouseUpEventHandler() cannot check whether at least one click event is consumed. This patch makes EventStateManager::InitAndDispatchClickEvent() sends local variable of nsEventStatus to nsIPresShell::HandleEventWithTarget(). Then, merge the result with current status. If we'd change nsEventStatus to enum class, we could make this change as custom "operator|=" or something. Differential Revision: https://phabricator.services.mozilla.com/D7850
588859b2d5cc: Bug 1461708 - part 2: Split EventStateManager::CheckForAndDispatchClick() r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:01:57 +0000 - rev 498893
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 2: Split EventStateManager::CheckForAndDispatchClick() r=smaug This patch splits EventStateManager::CheckForAndDispatchClick(). One is for handling default action of eMouseUp, the other is for dispatching click events. This makes it easier to add other default actions after dispatching click events. Differential Revision: https://phabricator.services.mozilla.com/D7849
973ea1694606: Bug 1461708 - part 1: Clean up EventStateManager::CheckForAndDispatchClick() with early-return style r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Wed, 10 Oct 2018 12:01:18 +0000 - rev 498892
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1461708 - part 1: Clean up EventStateManager::CheckForAndDispatchClick() with early-return style r=smaug Differential Revision: https://phabricator.services.mozilla.com/D7848
18d88d24495a: Bug 1491403 - Part 3: Propagate the user input event handling state to the promise resolve handlers in case the promise creator requests it r=smaug,arai,baku
Ehsan Akhgari <ehsan@mozilla.com> - Tue, 09 Oct 2018 21:42:22 +0000 - rev 498784
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1491403 - Part 3: Propagate the user input event handling state to the promise resolve handlers in case the promise creator requests it r=smaug,arai,baku Depends on D7004 Differential Revision: https://phabricator.services.mozilla.com/D7005
ecce651fad51: Bug 1473108 - Part 2: Make PresShell not point to unbound NAC in event content stack; r=smaug
Edgar Chen <echen@mozilla.com> - Tue, 09 Oct 2018 12:16:15 +0000 - rev 498692
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1473108 - Part 2: Make PresShell not point to unbound NAC in event content stack; r=smaug Differential Revision: https://phabricator.services.mozilla.com/D8042
b38223cb4fd1: Bug 1473108 - Part 1: Devirtualize nsIPresShell::GetCurrentEventFrame/GetEventTargetContent; r=smaug
Edgar Chen <echen@mozilla.com> - Tue, 09 Oct 2018 09:47:58 +0000 - rev 498691
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1473108 - Part 1: Devirtualize nsIPresShell::GetCurrentEventFrame/GetEventTargetContent; r=smaug Differential Revision: https://phabricator.services.mozilla.com/D8041
550aa5330baf: Bug 1497546 - Disable new behavior of keyCode and charCode of keypress event r=smaug a=Aryx
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 09 Oct 2018 21:04:37 +0300 - rev 498690
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497546 - Disable new behavior of keyCode and charCode of keypress event r=smaug a=Aryx Summary: The fix of bug 1479964 breaks some web apps using Google Closure including Google's apps. So, for Nightly testers, we should disable the new behavior until Google Closure fixes it or we can disable the new behavior per web apps. Reviewers: smaug Reviewed By: smaug Bug #: 1497546 Differential Revision: https://phabricator.services.mozilla.com/D8090
a9db3033d9cb: Bug 1479964 - Set KeyboardEvent.keyCode and KeyboardEvent.charCode to same value if the event is "keypress" event r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 09 Oct 2018 04:43:37 +0000 - rev 498570
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1479964 - Set KeyboardEvent.keyCode and KeyboardEvent.charCode to same value if the event is "keypress" event r=smaug Chrome sets both KeyboardEvent.keyCode and KeyboardEvent.charCode of "keypress" event to same value. On the other hand, our traditional behavior is, sets one of them to 0. Therefore, we need to set keyCode value to charCode value if the keypress event is caused by a non-function key, i.e., it may be a printable key with specific modifier state and/or different keyboard layout for compatibility with Chrome. Similarly, we need to set charCode value to keyCode value if the keypress event is caused by a function key which is not mapped to producing a character. Note that this hack is for compatibility with Chrome. So, for now, it's enough to change the behavior only for "keypress" event handlers in web content. If we completely change the behavior, we need to fix a lot of default handlers and mochitests too. However, it's really difficult because default handlers check whether keypress events are printable or not with following code: > if (event.charCode && > !event.altKey && !event.ctrlKey && !event.metaKey) { or > if (!event.keyCode && > !event.altKey && !event.ctrlKey && !event.metaKey) { So, until we stop dispatching "keypress" events for non-printable keys, we need complicated check in each of them. And also note that this patch changes the behavior of KeyboardEvent::KeyCode() when spoofing is enabled and the instance is initialized by initKeyEvent() or initKeyboardEvent(). That was changed by bug 1222285 unexpectedly and keeping the behavior makes patched code really ugly. Therefore, this takes back the old behavior even if spoofing is enabled. Differential Revision: https://phabricator.services.mozilla.com/D7974
70f63648a0f6: Bug 1497126 - Fix WPTs for 1 level of recursion when loading nested iframes with same URL, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Mon, 08 Oct 2018 16:04:57 +0200 - rev 498438
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497126 - Fix WPTs for 1 level of recursion when loading nested iframes with same URL, r=smaug
dc46a5f43a47: Bug 1497126 - Allow 1 level of recursion when loading nested iframes with same URL, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Mon, 08 Oct 2018 16:04:56 +0200 - rev 498437
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1497126 - Allow 1 level of recursion when loading nested iframes with same URL, r=smaug
15fe5851f113: Bug 1310193 - Remove wrapping of nsISupports as nsISupportsInterfacePointer in transferables. r=smaug
Neil Deakin <enndeakin@gmail.com> - Sun, 07 Oct 2018 16:33:07 +0200 - rev 498408
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1310193 - Remove wrapping of nsISupports as nsISupportsInterfacePointer in transferables. r=smaug
fd12d054f76c: Bug 1495364 - FeaturePolicy: geolocation, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Sat, 06 Oct 2018 13:10:30 +0200 - rev 498353
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495364 - FeaturePolicy: geolocation, r=smaug
de02c78c82b7: Bug 1495272 Part 2 - Use DeferredFinalize in SweepTearOffs when recording/replaying, r=smaug.
Brian Hackett <bhackett1024@gmail.com> - Wed, 03 Oct 2018 15:03:37 -1000 - rev 498150
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495272 Part 2 - Use DeferredFinalize in SweepTearOffs when recording/replaying, r=smaug.
cafd172dc48a: Bug 1495362 - FeaturePolicy: fullscreen, r=smaug
Andrea Marchesini <amarchesini@mozilla.com> - Thu, 04 Oct 2018 14:34:37 +0200 - rev 498112
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495362 - FeaturePolicy: fullscreen, r=smaug
e6cfd555f0d1: Bug 1290420 Part 4: Make the PresShell create a MobileViewportManager on demand. r=botond,smaug
Brad Werth <bwerth@mozilla.com> - Thu, 04 Oct 2018 03:28:40 +0000 - rev 498091
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1290420 Part 4: Make the PresShell create a MobileViewportManager on demand. r=botond,smaug Depends on D3376 Differential Revision: https://phabricator.services.mozilla.com/D3377
ec06f75313de: Bug 1290420 Part 1: Add a docshell flag for overriding meta viewport handling. r=smaug
Botond Ballo <botond@mozilla.com>, Brad Werth <bwerth@mozilla.com> - Thu, 04 Oct 2018 00:19:40 +0000 - rev 498088
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1290420 Part 1: Add a docshell flag for overriding meta viewport handling. r=smaug Differential Revision: https://phabricator.services.mozilla.com/D3373
37fcdbb6756c: Bug 1495983: Assert system privileged about: pages have CSP. r=smaug
Christoph Kerschbaumer <ckerschb@christophkerschbaumer.com> - Wed, 03 Oct 2018 09:47:08 +0200 - rev 498062
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1495983: Assert system privileged about: pages have CSP. r=smaug
1873f93e51a6: Bug 1496284 - Drop Etherpad instances from "dom.keyboardevent.keypress.hack.dispatch_non_printable_keys" r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 04 Oct 2018 09:19:49 +0000 - rev 498006
Push 1864 by ffxbld-merge at Mon, 03 Dec 2018 15:51:40 +0000
Bug 1496284 - Drop Etherpad instances from "dom.keyboardevent.keypress.hack.dispatch_non_printable_keys" r=smaug Etherpad fixed the bug with new Gecko behavior and has already released it in this August. So, even if some instances still use older versions, we can request them to update the version. This patch removes all Etherpad instances we know from the blacklist of strict keypress dispatching. So, Nightly testers can find old instances easier. Differential Revision: https://phabricator.services.mozilla.com/D7694