5fb87d2312ea4881026ecaac6488fbdc2e4a7725: Bug 1504237 - Ensure partial animated frames always use BGRA instead of BGRX. r=tnikkel
Andrew Osmond <aosmond@mozilla.com> - Fri, 02 Nov 2018 15:28:17 -0400 - rev 500768
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504237 - Ensure partial animated frames always use BGRA instead of BGRX. r=tnikkel For decoders which produce unpaletted partial frames (APNG, WebP), the surface format should always be BGRA. These frames while partial, are the same size as the output size of the animated image. When FrameAnimator performs the blend with the compositing frame, it expects all pixels we don't care about to be set to fully transparent. If it is BGRX, they will be set to solid white instead. Differential Revision: https://phabricator.services.mozilla.com/D10753
719fa010f362459aa154651d44d9b452a494f330: Merge mozilla-central to mozilla-inbound. CLOSED TREE
Csoregi Natalia <ncsoregi@mozilla.com> - Sat, 03 Nov 2018 23:47:49 +0200 - rev 500767
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Merge mozilla-central to mozilla-inbound. CLOSED TREE
86ab0cd2855c06099abce0a68700127dcbd26193: Bug 1504447 - Grant runtime permissions to test app before running geckoview-junit; r=bc
Geoff Brown <gbrown@mozilla.com> - Sat, 03 Nov 2018 14:22:50 -0600 - rev 500766
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1504447 - Grant runtime permissions to test app before running geckoview-junit; r=bc
cfdbecb2e2305dba0ccac931aa91423135039d2f: Merge autoland to mozilla-central. a=merge
Csoregi Natalia <ncsoregi@mozilla.com> - Sat, 03 Nov 2018 23:44:05 +0200 - rev 500765
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Merge autoland to mozilla-central. a=merge
3eff39403c8c53f2a0871be7740e1957f2f45ff9: Bug 1426492 - Add an assertion to limit XBL bindings in the content process r=NeilDeakin
Timothy Guan-tin Chien <timdream@gmail.com> - Sat, 03 Nov 2018 11:11:31 +0000 - rev 500764
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1426492 - Add an assertion to limit XBL bindings in the content process r=NeilDeakin Differential Revision: https://phabricator.services.mozilla.com/D8907
c2c30e650d6996d09d94fec5ea2da80b02054724: bug 1502864: marionette: enable strict file interactability in Python client; r=whimboo
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:30:48 +0000 - rev 500763
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: marionette: enable strict file interactability in Python client; r=whimboo Depends on D10275 Depends on D10275 Differential Revision: https://phabricator.services.mozilla.com/D10574
fcbcfe24b192e480832aeb65704de5ec6ab4fdff: bug 1502864: marionette: support strictFileInteractability; r=whimboo
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:31:00 +0000 - rev 500762
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: marionette: support strictFileInteractability; r=whimboo This patch changes Marionette to only run the interactability test on <input type=file> when the strictFileInteractability capability is set. strictFileInteractability is not set by default which means this changes WebDriver:SendElementKeys' behaviour to not run interactability checks on <input type=file>. This aligns our WebDriver implementation with the current behaviour in Chrome. To make it legible what the input to interaction.sendKeysToElement is, its API has changed to take an options dictionary instead of three boolean arguments at the end. Depends on D10274 Depends on D10274 Differential Revision: https://phabricator.services.mozilla.com/D10275
5dfaec47ee3ffab3f7648ce0309118cdd5e15565: bug 1502864: geckodriver: support strictFileInteractability; r=jgraham
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:31:18 +0000 - rev 500761
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: geckodriver: support strictFileInteractability; r=jgraham The strictFileInteractability capability is always supported by geckodriver. Depends on D10273 Depends on D10273 Differential Revision: https://phabricator.services.mozilla.com/D10274
a46ac8b5864d82c6780f6cd8bc0805696ba58bfd: bug 1502864: webdriver: add strictFileInteractability capability; r=jgraham
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:32:34 +0000 - rev 500760
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: webdriver: add strictFileInteractability capability; r=jgraham Depends on D10272 Depends on D10272 Differential Revision: https://phabricator.services.mozilla.com/D10273
7a89ca7dca2d3df428a4a8d94c31cd5c48af3162: bug 1502864: webdriver: sort invalid_extensions list; r=jgraham
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:32:36 +0000 - rev 500759
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: webdriver: sort invalid_extensions list; r=jgraham Depends on D10271 Depends on D10271 Differential Revision: https://phabricator.services.mozilla.com/D10272
dc69c736701f2b7b405e50ed92e3384e44e233c7: bug 1502864: webdriver: add strictFileInteractability capability tests; r=jgraham
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:32:38 +0000 - rev 500758
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: webdriver: add strictFileInteractability capability tests; r=jgraham The new strictFileInteractabilityTests capability takes a boolean and can unconditionally be set to both true and false. It is permitted to be undefined. Depends on D10270 Depends on D10270 Differential Revision: https://phabricator.services.mozilla.com/D10271
6fb763dc8e9b832ddd4aa24179b74db94a229c35: bug 1502864: webdriver: add tests for hidden <input type=file>; r=jgraham,whimboo
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:32:40 +0000 - rev 500757
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: webdriver: add tests for hidden <input type=file>; r=jgraham,whimboo The WebDriver standard changed in https://github.com/w3c/webdriver/pull/1325 to align with chromedriver's behaviour of permitting interaction with hidden <input type=file> elements. DOM elements can be hidden, i.e. not rendered, in two ways: through applying the "hidden" DOM attribute or by setting the "display: none" CSS style. Depends on D10269 Depends on D10269 Differential Revision: https://phabricator.services.mozilla.com/D10270
301c1d1d5e14f001e373b329de611460a177dec8: bug 1502864: webdriver: add tests for keyboard interactability for <input type=file>; r=jgraham
Andreas Tolfsen <ato@sny.no> - Sat, 03 Nov 2018 16:32:42 +0000 - rev 500756
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
bug 1502864: webdriver: add tests for keyboard interactability for <input type=file>; r=jgraham Normally all interactability tests are centralised in interactability.py, but the WebDriver standard recently changed to apply a special set of interactability checks specifically for <input type=file>. These tests ensure the special code paths are invoked for form controls. Differential Revision: https://phabricator.services.mozilla.com/D10269
d29131a841689c606dc2ced3be4298fa748ee59b: Bug 1501502 - Assertion failure: IsObjectValueInCompartment(v, compartment()) with bogus queuing strategy object. r=tcampbell
Jason Orendorff <jorendorff@mozilla.com> - Sat, 03 Nov 2018 13:13:55 +0000 - rev 500755
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1501502 - Assertion failure: IsObjectValueInCompartment(v, compartment()) with bogus queuing strategy object. r=tcampbell Differential Revision: https://phabricator.services.mozilla.com/D10773
e6860806fc1fc0f4e8144af6e7fa7cfae8eb88f3: Backed out 2 changesets (bug 1501503) as requested by bradwerth on the ticket.
Brindusan Cristian <cbrindusan@mozilla.com> - Sat, 03 Nov 2018 15:03:29 +0200 - rev 500754
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Backed out 2 changesets (bug 1501503) as requested by bradwerth on the ticket. Backed out changeset 814414676c25 (bug 1501503) Backed out changeset c2d9f82adf43 (bug 1501503)
bb81f74e232ad6a145f7ebf526bd066a228d01ec: Bug 1503473 - part 5: Move InsertParagraphSeparator*() into HTMLEditor r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 03 Nov 2018 04:19:22 +0000 - rev 500753
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503473 - part 5: Move InsertParagraphSeparator*() into HTMLEditor r=m_kato Now, TextEditor needs only InsertLineBreak*() so that InsertParagraphSeparator*() is necessary only in HTMLEditor. With overriding nsIPlaintextEditor::InsertLineBreak() in HTMLEditor, we can do it simply. Differential Revision: https://phabricator.services.mozilla.com/D10525
dffafc01a94d0455fc4b44e42548d36b573fdbf5: Bug 1503473 - part 4: Create a new path to handle Enter key press in TextEditor r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 03 Nov 2018 11:22:13 +0000 - rev 500752
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503473 - part 4: Create a new path to handle Enter key press in TextEditor r=m_kato This patch creates new path to insert a line break in TextEditor. Declares new EditSubAction::eInsertLineBreak and makes the path use EditAction::eInsertLineBreak instead of EditAction::eInsertParagraphSeparator. Unfortunately, this patch makes TextEditor::InsertLineBreakAsAction() as a virtual method for keeping this change as small as possible. Differential Revision: https://phabricator.services.mozilla.com/D10524
952458a5da30ad6f6542c8899755c8c6ef16db79: Bug 1503473 - part 3: Move inserting a line break code in TextEditor::InsertParagraphSeparatorAsSubAction() to TextEditRules::WillInsertLineBreak() r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 03 Nov 2018 11:21:15 +0000 - rev 500751
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503473 - part 3: Move inserting a line break code in TextEditor::InsertParagraphSeparatorAsSubAction() to TextEditRules::WillInsertLineBreak() r=m_kato When TextEditRules::WillDoAction() and HTMLEditRules::WillDoAction() didn't return error, didn't handle it, and didn't cancel it, TextEditor::InsertParagraphSeparatorAsSubAction() inserts a line breaker. However, this case is only when the instance is TextEditRules and TextEditRules::WillInsertLineBreak() prepares to insert a line break without any errors. So, we can move the part into TextEditRules::WillInsertLineBreak() simply. Differential Revision: https://phabricator.services.mozilla.com/D10523
45bc2423e812560a8cd69b0639e70096cbac83b5: Bug 1503473 - part 2: Make TextEditRules::WillInsertBreak() and HTMLEditRules::WillInsertBreak() return EditActionResult r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 03 Nov 2018 11:20:06 +0000 - rev 500750
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503473 - part 2: Make TextEditRules::WillInsertBreak() and HTMLEditRules::WillInsertBreak() return EditActionResult r=m_kato With this cleaning up, we can know when they return NS_OK with both aCanceled is false and aHandled is false. (Look for EditActionIgnored().) Additionally, this patch renames HTMLEditRules::WillInsertBreak() to WillInsertParagraphSeparator() and TextEditRules::WillInsertBreak() to TextEditRules::WillInsertLineBreak(). Differential Revision: https://phabricator.services.mozilla.com/D10522
3f5d390db0faf52000531b31b579b27fb73c04b1: Bug 1503473 - part 1: Rename TextEditor::OnInputParagraphSeparator() and HTMLEditor::OnInputLineBreak() r=m_kato
Masayuki Nakano <masayuki@d-toybox.com> - Sat, 03 Nov 2018 11:19:07 +0000 - rev 500749
Push 10290 by ffxbld-merge at Mon, 03 Dec 2018 16:23:23 +0000
Bug 1503473 - part 1: Rename TextEditor::OnInputParagraphSeparator() and HTMLEditor::OnInputLineBreak() r=m_kato TextEditor::OnInputParagraphSeparator() and HTMLEditor::OnInputLineBreak() are also used by command handlers. Therefore, they should be renamed to TextEditor::InsertParagraphSeparatorAsAction() and HTMLEditor::InsertLineBreakAsAction(). Then, current TextEditor::InsertParagraphSeparatorAsAction() should be renamed to AsSubAction() and each caller of it should create AutoPlaceholderBatch by themselves. Differential Revision: https://phabricator.services.mozilla.com/D10521
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip