5c148323ff77d13366337adf2ae343c573624354: Bug 1396205 - Show the Go button only when the user started typing in the location bar. ui-r=shorlander r=daleharvey
Dão Gottwald <dao@mozilla.com> - Fri, 08 Sep 2017 12:28:19 +0200 - rev 379706
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1396205 - Show the Go button only when the user started typing in the location bar. ui-r=shorlander r=daleharvey MozReview-Commit-ID: JZu0GiwMySP
5a0fd0db0fb0188b7fe8a0db79138b72f977ebc0: Bug 1390336 - Disable panelview keyboard navigation using arrow keys in the overflow panel, because input boxes can be in there. r=Gijs
Mike de Boer <mdeboer@mozilla.com> - Fri, 08 Sep 2017 11:53:11 +0200 - rev 379705
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1390336 - Disable panelview keyboard navigation using arrow keys in the overflow panel, because input boxes can be in there. r=Gijs MozReview-Commit-ID: DxZv8JDp2Q2
9b99855c32cac452f6e6ded85e6b96769f9d6318: Bug 1392143 - P6. Use constants in coordinate calculations. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 07 Sep 2017 19:36:20 +0200 - rev 379704
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1392143 - P6. Use constants in coordinate calculations. r=mattwoodrow This shows how the coordinates were actually calculated. and will make it easier should the video size needs to ever be changed again. MozReview-Commit-ID: KkQNqz00Aw0
0e76e3df87497dd708ea3affc7e7dafb532d71c0: Bug 1392143 - P5. Improve rendering test. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 07 Sep 2017 19:19:35 +0200 - rev 379703
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1392143 - P5. Improve rendering test. r=mattwoodrow We now check that the canvas is properly scaled by checking if the color immediately on the right of the canvas is correct. If the rendering failed, we do not bother testing the H264 video decoder. MozReview-Commit-ID: IwBwKnceLBg
6714fb98a7f25b857dab3f276e5b85871e5792a0: Bug 1392143 - P4. Change test expectations now that it passes. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 07 Sep 2017 17:52:49 +0200 - rev 379702
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1392143 - P4. Change test expectations now that it passes. r=mattwoodrow MozReview-Commit-ID: moLdQoJnQw
83c640edfe509971e39ad7d10d1b7994664d7bba: Bug 1392143 - P3. Resize window after moving it. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 07 Sep 2017 17:49:05 +0200 - rev 379701
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1392143 - P3. Resize window after moving it. r=mattwoodrow This ensure that the window still has the intended size if it had been resized due to different DPI setup. MozReview-Commit-ID: 9oeXbTKQqhe
bdd70cdbf8f118e1001b2e534c213c17c1fe8240: Bug 1392143 - P2. Disable hardware decoding for small videos. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 06 Sep 2017 17:02:21 +0200 - rev 379700
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1392143 - P2. Disable hardware decoding for small videos. r=mattwoodrow As the H264 SanityTest uses a 132x132 videos to determine if the hardware decoder is working, we always use the software decoder for smaller videos. MozReview-Commit-ID: 8VbZTiJO9mA
503df830e5947469778fe8fbc3e10efc29ccde98: Bug 1392143 - P1. Change video size used for testing if h264 decoder is working. r=mattwoodrow
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 06 Sep 2017 15:42:46 +0200 - rev 379699
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1392143 - P1. Change video size used for testing if h264 decoder is working. r=mattwoodrow AMD incorrectly decode videos with a resolution that is less than 128x128, as such with the test failing we disable hardware decoding on those machines, even though other resolutions work well. So we use a 132x132 video instead. MozReview-Commit-ID: 80mk11CNsil
f4d56d495aa65fd99cf89f5922180a3c01b65308: Bug 1395065 - Move the notification to the top-center of the window r=gasolin
Ricky Chien <ricky060709@gmail.com> - Thu, 07 Sep 2017 18:23:27 +0800 - rev 379698
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1395065 - Move the notification to the top-center of the window r=gasolin MozReview-Commit-ID: L4OSbt3hJ4q
cd88f7fba8bdc30c1b1d885e6065a81a2960c3cd: Backed out changeset 34db5bec9cad (bug 1371543) for failing browser-chrome's browser/components/uitour/test/browser_UITour_availableTargets.js. r=backout
Sebastian Hengst <archaeopteryx@coole-files.de> - Fri, 08 Sep 2017 11:49:54 +0200 - rev 379697
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Backed out changeset 34db5bec9cad (bug 1371543) for failing browser-chrome's browser/components/uitour/test/browser_UITour_availableTargets.js. r=backout
f7364d8ab9d4a7e6c2dd445d92ca3b86c225210a: Bug 1397457 - Update mach to download clang-format 5.0 r=andi
Sylvestre Ledru <sledru@mozilla.com> - Wed, 06 Sep 2017 23:56:34 +0200 - rev 379696
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1397457 - Update mach to download clang-format 5.0 r=andi MozReview-Commit-ID: EF3thvpxg6G
0c4fb7fef02acd521d430455253f239e7b38e274: Bug 1396324 - [robocop] Configure bookmarks panel as default panel before loading URLs. r=JanH
Jing-wei Wu <topwu.tw@gmail.com> - Fri, 08 Sep 2017 16:02:37 +0800 - rev 379695
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1396324 - [robocop] Configure bookmarks panel as default panel before loading URLs. r=JanH We found sometimes Robocop operates wrong UI components when it deals with a complex layout. Since default panel shows Activity Stream which contains complex UI components, we configure bookmarks panel as default panel to keep the layout as simple as possible. MozReview-Commit-ID: 12xhVOdlIRK
5534f9aff56be5ff944631f028951378bbbfaaf1: Bug 1390874 - Add a hidpi test directory to emulate high screen resolution for browser_startup_images.js. r=florian
Johann Hofmann <jhofmann@mozilla.com> - Wed, 16 Aug 2017 15:33:14 +0200 - rev 379694
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1390874 - Add a hidpi test directory to emulate high screen resolution for browser_startup_images.js. r=florian Also adds a warning that the test should only be used in debug mode. MozReview-Commit-ID: 6X8jSz5O2ue
ef1641e40903ff5e6cff94f2a1d1a3188598e563: Bug 1369072 - part3: nsXBLPrototypeHandler::DispatchXBLCommand() should use controller of visible window r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 07 Sep 2017 22:54:49 +0900 - rev 379693
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1369072 - part3: nsXBLPrototypeHandler::DispatchXBLCommand() should use controller of visible window r=smaug With previous change, KeyboardEvent is dispatched even when invisible window has focus. However, nsRootWindow::GetControllerForCommand() returns controller for focused window even when the window is invisible because it uses nsFocusManager::GetFocusedDescendant() to retrieve focused window. Perhaps, we can assume that users won't expect to do something with invisible window when they type some keys. Then, nsRootWindow::GetControllerForCommand() should return controller for visible ancestor window if focused window is invisible. This patch makes nsFocusManager::GetFocusedDescendant() can return only visible descendants. However, it already has a bool argument. Therefore, it should have a flag instead of adding new flag. Most changes of this patch is replacing its callers. Then, nsRootWindow::GetControllerForCommand() and nsRootWindow::GetControllers() should have a bool flag if it should return controller(s) for visible window. This patch adds a bool flag for it. Fortunately, the interface isn't scriptable. Finally, this patch makes nsXBLPrototypeHandler::DispatchXBLCommand() and EventStateManager::DoContentCommandEvent() retrieve controller for visible window since they are always handles user input. MozReview-Commit-ID: GygttTHuKRm
1c3ac6cb53ea9c76c89d8e5d1cb1ee19703e1180: Bug 1369072 - part2: PresShell::HandleEvent() should retarget KeyboardEvent if focused document is invisible r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 05 Sep 2017 19:39:33 +0900 - rev 379692
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1369072 - part2: PresShell::HandleEvent() should retarget KeyboardEvent if focused document is invisible r=smaug When focused document is invisible, PresShell::HandleEvent() won't dispatch any events. However, if it's KeyboardEvent, user cannot do anything only with keyboard. So, in this case, PresShell should retarget keyboard events to first visible ancestor. MozReview-Commit-ID: CvCBcYwvfbe
19f8a5d3da39cc4f2313f2dac2c4dbb04a6329e8: Bug 1369072 - part1: PresShell should climb up scrollable frames when there is no selection, no focused content and root scrollable frame isn't scrollable r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 05 Sep 2017 17:17:21 +0900 - rev 379691
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1369072 - part1: PresShell should climb up scrollable frames when there is no selection, no focused content and root scrollable frame isn't scrollable r=smaug When there is no selection and no focused content, aContent of nsIPresShell::GetScrollableFrameToScrollForContent() is nullptr. Then, it'll use root scrollable frame to scroll. However, the root scrollable frame may be not scrollable. In such case, ancestor document's scrollable frame should be scrolled instead. MozReview-Commit-ID: 1kOPtDX6G5L
2e507cfef60d45641908a36a977d2497d77e4c84: Bug 1369072 - part0: Add automated test for testing key event handlers to scroll parent document when an iframe element has or had focus r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 05 Sep 2017 15:18:02 +0900 - rev 379690
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1369072 - part0: Add automated test for testing key event handlers to scroll parent document when an iframe element has or had focus r=smaug When an <iframe> element has focus and its sub document isn't scrollable, the parent document should be scrolled instead. MozReview-Commit-ID: 5LSVDHDQGtI
5ead094a4792105cbdc4ced7424230e8e345a13b: Bug 1377006 - Part 2: Add disableHighlight option in formautofill doorhanger. r=lchang,MattN
steveck-chung <schung@mozilla.com> - Thu, 27 Jul 2017 18:11:12 +0800 - rev 379689
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1377006 - Part 2: Add disableHighlight option in formautofill doorhanger. r=lchang,MattN MozReview-Commit-ID: 3UkSIUeM0oK
735a60b17ee4342b41529f581b87fe36a013e1aa: Bug 1377006 - Part 1: Add disable highlight option in main action button. r=johannh
steveck-chung <schung@mozilla.com> - Thu, 27 Jul 2017 16:34:52 +0800 - rev 379688
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
Bug 1377006 - Part 1: Add disable highlight option in main action button. r=johannh MozReview-Commit-ID: 5WgQzdxmsNp
2af9cfda0d5c1a8821d1640d8185ae0985383fd3: merge mozilla-central to autoland. r=merge a=merge
Sebastian Hengst <archaeopteryx@coole-files.de> - Fri, 08 Sep 2017 11:03:59 +0200 - rev 379687
Push 32461 by kwierso@gmail.com at Fri, 08 Sep 2017 20:15:32 +0000
merge mozilla-central to autoland. r=merge a=merge
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip