2e9066bbee39b7a88c0e75327980d92f73b7e3b4: Bug 1341215 - Remove the dependency on the mozregression module for mach artifact. r?chmanchester draft
Mike Hommey <mh+mozilla@glandium.org> - Tue, 21 Feb 2017 16:10:54 +0900 - rev 488503
Push 46545 by bmo:mh+mozilla@glandium.org at Thu, 23 Feb 2017 06:42:32 +0000
Bug 1341215 - Remove the dependency on the mozregression module for mach artifact. r?chmanchester This imports two modules from mozregression in the tree to do so. They are imported from current trunk on github, rather than the version we were getting from pypi. Note we take six from testing/web-platform/tests/tools/six) instead of moving it to python/six because it's there by coming from a copy of https://github.com/w3c/wpt-tools, which contains it as a submodule, and moving it would make updates there harder.
c8a831212ea4d06da4105ff1186a67ffb5d9d96d: Bug 1340446 - check the rounding error smaller or euqal to one. r=kinetik draft
Alfredo.Yang <ayang@mozilla.com> - Wed, 22 Feb 2017 11:38:16 +0800 - rev 488502
Push 46544 by bmo:ayang@mozilla.com at Thu, 23 Feb 2017 06:37:35 +0000
Bug 1340446 - check the rounding error smaller or euqal to one. r=kinetik MozReview-Commit-ID: 5LYzYlZzmEB
8314727cbf31f5ab1bebbf97e0784afa4e84a3b5: Bug 1337235 - Mouseover Interactions for Grid Outline component. r?gl draft
Micah Tigley <tigleym@gmail.com> - Wed, 22 Feb 2017 23:25:31 -0700 - rev 488501
Push 46543 by bmo:tigleym@gmail.com at Thu, 23 Feb 2017 06:28:15 +0000
Bug 1337235 - Mouseover Interactions for Grid Outline component. r?gl MozReview-Commit-ID: I8RxOA5m0Ff
7b774c8eea2ca2272914b6c89c72962b0a90c235: Bug 1192818 - part4 : only mute media element if there is alive track. draft
Alastor Wu <alwu@mozilla.com> - Thu, 23 Feb 2017 14:16:44 +0800 - rev 488500
Push 46542 by alwu@mozilla.com at Thu, 23 Feb 2017 06:14:15 +0000
Bug 1192818 - part4 : only mute media element if there is alive track. If we don't have any alive track in MediaTrackList, we don't need to mute MediaElement. MozReview-Commit-ID: 9vY692O7N0e
994446cbbf5961ba8ef4ec4ea1c7d646a5ffcf47: Bug 1192818 - part3 : modify test. draft
Alastor Wu <alwu@mozilla.com> - Thu, 23 Feb 2017 14:15:49 +0800 - rev 488499
Push 46542 by alwu@mozilla.com at Thu, 23 Feb 2017 06:14:15 +0000
Bug 1192818 - part3 : modify test. MozReview-Commit-ID: HNXcbFbYfor
8d766bd30bf97815079d7e18aaf0996d080d152d: Bug 1192818 - part2 : only dispatch DOMAudioPlaybackStarted when there is audible sound. draft
Alastor Wu <alwu@mozilla.com> - Thu, 23 Feb 2017 14:15:47 +0800 - rev 488498
Push 46542 by alwu@mozilla.com at Thu, 23 Feb 2017 06:14:15 +0000
Bug 1192818 - part2 : only dispatch DOMAudioPlaybackStarted when there is audible sound. The DOMAudioPlaybackStarted event would affect the tabbrowser's attribute, "soundPlaying", and this attribute should indicate whether the tab is audible or not. However, in present codebase, even the tab has "soundplaying", it doens't mean the tab has audible sound, you need to check extra attribute, "muted". After applying this patch, tabbrowser can only own one of the attributes ("soundplaying" or "mute"). These attributes won't exist at the same time, so we can easily know whether the tab is audible by checking "soundPlaying". Let's see an example, step1. playing a playing audio - tab owns "soundPlaying" step2. mute the tab - tab owns "muted" step3. stop audio - tab owns "muted" step4. replay the audio - tab owns "muted" step5. unmute the tab - tab owns "soundPlaying" step6. stop audio - tab owns "" MozReview-Commit-ID: EEKEbAVzsVm
89b9ac41cd4dd0615a98f9d131b9b00c3301e763: Bug 1192818 - part1 : dispatch DOMAudioPlaybackStopped when mute the tab. draft
Alastor Wu <alwu@mozilla.com> - Thu, 23 Feb 2017 14:15:45 +0800 - rev 488497
Push 46542 by alwu@mozilla.com at Thu, 23 Feb 2017 06:14:15 +0000
Bug 1192818 - part1 : dispatch DOMAudioPlaybackStopped when mute the tab. The root cause of the intermittent fail is because "DOMAudioPlaybackStopped" has no directly relationship with browser.mute()/unmute(). In [1], the "DOMAudioPlaybackStopped" is caused by audio stop playing, not by calling the browser.mute(). If the audio stops playing before calling the wait_for_event(), the test would be time-out. I guess the bug 1302280 is also caused by same reason. So this patch would do two thinngs, 1. dispatch "DOMAudioPlaybackStopped" when we mute tab 2. loop the audio in test file, to make sure the "DOMAudioPlaybackStopped" is dispatched when muting the audio, not the file ended. [1] https://goo.gl/ymUv8P MozReview-Commit-ID: 5RnyBRE73lQ
5d9bf8d63cd3a88306ea8fec10f68f4a043196dd: Bug 713680 - Part 2: Fix editor tests to accommodate narrower Consolas monospace font. r?masayuki draft
Chris Peterson <cpeterson@mozilla.com> - Wed, 22 Feb 2017 22:08:19 -0800 - rev 488496
Push 46541 by cpeterson@mozilla.com at Thu, 23 Feb 2017 06:11:11 +0000
Bug 713680 - Part 2: Fix editor tests to accommodate narrower Consolas monospace font. r?masayuki Consolas is narrower than Courier New, so we must adjust some editor tests to accommodate: * browser_inplace-editor_maxwidth.js needs a longer LONG_TEXT to wrap three lines of text. * test_continuous_wheel_events.html needs shorter horizontal mouse wheel increments so three mouse wheel increments fire just one DOMMouseScroll event. Reduce increment from 5.3 pixels to 4.3 for these horizontal scrolling test cases. * queryCaretRectWin.html can now use the same expected min.left values as queryCaretRectUnix.html. The only difference between these two files now is the line endings (plus the comment warning about the line endings). * selectAtPoint.html no longer needs a Windows-only code path because Firefox on Windows now selects the same text as it does on Mac and Linux. MozReview-Commit-ID: J3Cr92CRDDr
3de0b4f5cdbfc1b98f3bccc83894b018667dbd6f: Bug 713680 - Part 1: Change default Windows monospace font from Courier New to Consolas. r?jfkthame draft
Chris Peterson <cpeterson@mozilla.com> - Mon, 20 Feb 2017 12:35:04 -0800 - rev 488495
Push 46541 by cpeterson@mozilla.com at Thu, 23 Feb 2017 06:11:11 +0000
Bug 713680 - Part 1: Change default Windows monospace font from Courier New to Consolas. r?jfkthame Consolas is narrower than Courier New, so we must adjust some layout tests to accommodate: * 323386-1.html's intermittent assertion failure (bug 718883) now appears to be 100% reliable on Windows, joining Linux and Android. * size-1-ref.html reftest needs a little fuzz because the horizontal line of the test image's '4' character is ~1 pixel shorter than the reference image's. MozReview-Commit-ID: Dhjnj8S04SB
e1e1531c39d1caf0d5e680a82819a0fffea39f53: Bug 1341960 TextInputHandler shouldn't ignore InsertText() calls even if TextInputHandler has already dispatched keypress events and/or composition events for the key down but InsertText() is called again for inserting printable text r?m_kato draft
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 23 Feb 2017 11:45:13 +0900 - rev 488494
Push 46540 by masayuki@d-toybox.com at Thu, 23 Feb 2017 05:52:10 +0000
Bug 1341960 TextInputHandler shouldn't ignore InsertText() calls even if TextInputHandler has already dispatched keypress events and/or composition events for the key down but InsertText() is called again for inserting printable text r?m_kato Korean IME and some other simple IME may not use marked text at composing text. Such IME modifies composing character with InsertText() with aReplacementRange. Then, when user types new character, such IME may replace the previous character with a call of InsertText() with aReplacementRange and insert the next character with additional call of InsertText() without aReplacementRange. In this case, InsertText() ignores the call when the native keydown event is already caused composition events. However, we need to allow to dispatch keypress event for supporting to insert text even in such case. This patch checks if inserting text is printable. If it's not a printable character such as U+000A at pressing Enter, keeping current behavior. Otherwise, dispatching keypress event instead. MozReview-Commit-ID: 5NcCgXfvniO
9a544b17ace6016aea1a8a725317d874fdf96b45: [WIP] Bug 1232439 (972193) - Add dialog for selecting folder in which to place new bookmarks folder. draft
Tom Klein <twointofive@gmail.com> - Fri, 23 Dec 2016 16:35:31 -0600 - rev 488493
Push 46539 by bmo:twointofive@gmail.com at Thu, 23 Feb 2017 05:43:30 +0000
[WIP] Bug 1232439 (972193) - Add dialog for selecting folder in which to place new bookmarks folder. MozReview-Commit-ID: C9ohxgMoZlC
7715f5b60cecaac07c1dae8f3cc8131295f2d3dd: [WIP] Bug 1232439 (972193) - Add "Create folder" bookmark edit dialog option. draft
Tom Klein <twointofive@gmail.com> - Fri, 23 Dec 2016 17:24:18 -0600 - rev 488492
Push 46539 by bmo:twointofive@gmail.com at Thu, 23 Feb 2017 05:43:30 +0000
[WIP] Bug 1232439 (972193) - Add "Create folder" bookmark edit dialog option. MozReview-Commit-ID: 1Rrx4UgBUM3
4393520db85526c586aa7352feae6ffc5c01a96f: [WIP] Bug 1232439 (972193) - Add "Choose Folder" bookmark edit dialog option. draft
Tom Klein <twointofive@gmail.com> - Thu, 08 Dec 2016 09:52:19 -0600 - rev 488491
Push 46539 by bmo:twointofive@gmail.com at Thu, 23 Feb 2017 05:43:30 +0000
[WIP] Bug 1232439 (972193) - Add "Choose Folder" bookmark edit dialog option. MozReview-Commit-ID: L152bg4QH4Q
8695b2122b597edc2bd3af815832706fcd5b9095: [WIP] Bug 1232439 (972193) - Create base classes for use in bookmark edit dialogs. draft
Tom Klein <twointofive@gmail.com> - Sun, 25 Dec 2016 19:00:56 -0600 - rev 488490
Push 46539 by bmo:twointofive@gmail.com at Thu, 23 Feb 2017 05:43:30 +0000
[WIP] Bug 1232439 (972193) - Create base classes for use in bookmark edit dialogs. BookmarkToolbarDialog creates just the toolbar; its subclass BookmarkFolderTreeDialog additionally includes a FolderTreeView for displaying a list of folders. MozReview-Commit-ID: HxYcd9AB9OY
55d19fc7fca36022bbe519e01e0da79ceaab81a0: [WIP] Bug 1232439 (972193) - Add FolderTreeView for choosing a folder from a list. draft
Tom Klein <twointofive@gmail.com> - Sun, 25 Dec 2016 17:47:29 -0600 - rev 488489
Push 46539 by bmo:twointofive@gmail.com at Thu, 23 Feb 2017 05:43:30 +0000
[WIP] Bug 1232439 (972193) - Add FolderTreeView for choosing a folder from a list. MozReview-Commit-ID: 2Hbjfok6tqd
b22dc0a401d333431cfdb7304d172329f0d6198c: [WIP] Bug 1232439 (972193) - Add more database folder methods for bookmark edit dialogs. draft
Tom Klein <twointofive@gmail.com> - Tue, 27 Dec 2016 11:23:46 -0600 - rev 488488
Push 46539 by bmo:twointofive@gmail.com at Thu, 23 Feb 2017 05:43:30 +0000
[WIP] Bug 1232439 (972193) - Add more database folder methods for bookmark edit dialogs. MozReview-Commit-ID: 83QDxrMd6SP
3c88fa63d87d97ddc0b4578865362d4fc3e2b5c9: Bug 775624 Part 24 - Implement operator<< for nsReflowStatus to use mozilla::ToString. r?dholbert draft
Ting-Yu Lin <tlin@mozilla.com> - Tue, 14 Feb 2017 18:41:41 +0800 - rev 488487
Push 46538 by bmo:tlin@mozilla.com at Thu, 23 Feb 2017 05:39:06 +0000
Bug 775624 Part 24 - Implement operator<< for nsReflowStatus to use mozilla::ToString. r?dholbert To print log in nsBlockFrame, run "GECKO_BLOCK_DEBUG_FLAGS=reflow ./mach run". Here is a sample nsReflowStatus string: [Complete=Y,NIF=N,Truncated=N,Break=N,FirstLetter=Y]. MozReview-Commit-ID: 4voGcXfJlN7
bac256786aa44181a5df0f42daac9f63d5d836b6: Bug 775624 Part 23 - Remove constructor and all operators related to uint32_t. r?dholbert draft
Ting-Yu Lin <tlin@mozilla.com> - Tue, 14 Feb 2017 18:01:11 +0800 - rev 488486
Push 46538 by bmo:tlin@mozilla.com at Thu, 23 Feb 2017 05:39:06 +0000
Bug 775624 Part 23 - Remove constructor and all operators related to uint32_t. r?dholbert MozReview-Commit-ID: FEVYMhcpPS0
cdb6aa3cd5d61946c4a4678486d2f2e8356fd514: Bug 775624 Part 22 - Remove NS_FRAME_COMPLETE. r?dholbert draft
Ting-Yu Lin <tlin@mozilla.com> - Tue, 14 Feb 2017 17:55:48 +0800 - rev 488485
Push 46538 by bmo:tlin@mozilla.com at Thu, 23 Feb 2017 05:39:06 +0000
Bug 775624 Part 22 - Remove NS_FRAME_COMPLETE. r?dholbert This patch is written by the following script with some manual adjustment to the comment in nsRubyTextContainerFrame.cpp and nsRubyFrame.cpp, and nsColumnSetFrame's constructor. function rename() { find layout\ -type f\ \( -name "*.cpp" -or\ -name "*.h" \)\ -exec sed -i -r "s/$1/$2/g" "{}" \; } rename "nsReflowStatus *([a-zA-Z0-9]*) = NS_FRAME_COMPLETE" "nsReflowStatus \1" rename "([a-zA-Z0-9.*]*) *= NS_FRAME_COMPLETE;" "\1.Reset();" rename "([a-zA-Z0-9.*]*) == NS_FRAME_COMPLETE" "\1.IsEmpty()" MozReview-Commit-ID: 9tqQAHvdQex
efe44850d7f1e82f160333c5052283985ce6d337: Bug 775624 Part 21 - Remove NS_FRAME_NOT_COMPLETE. r?dholbert draft
Ting-Yu Lin <tlin@mozilla.com> - Tue, 14 Feb 2017 17:30:56 +0800 - rev 488484
Push 46538 by bmo:tlin@mozilla.com at Thu, 23 Feb 2017 05:39:06 +0000
Bug 775624 Part 21 - Remove NS_FRAME_NOT_COMPLETE. r?dholbert To preserve the semantics, Reset() is called to clear other bits in the status prior to set the incomplete bit. Though some of them might not be necessary. MozReview-Commit-ID: InNDwcpp28A
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip