Bug 1408944 - Rewrite and enable browser_webconsole_network_requests_from_chrome.js; r=nchevobbe MozReview-Commit-ID: EPzTQhqhVFE

Bug 1410210 - Remove talos pageloader command line options; r=jmaher MozReview-Commit-ID: BS22DU6Pmxk

Bug 1409133 - Avoid shrinking tabs through ::before elements when moving them. r=dao As mentioned in the comment: Note that this doesn't perfectly solve the issue (dragged tabs may still resize very slightly) on some DPI settings with uneven scaling factors on Windows, because of bug 477157. We consider the fix in this patch good enough for now. MozReview-Commit-ID: BbpxLVq8AEb

Bug 1416465 - Regression tests for process_install_manifest.py. r=mshal MozReview-Commit-ID: LTqTddybtrr

Bug 1417017 - Check for content. usage at global and within add_task for no-cpows-in-tests. r=standard8 MozReview-Commit-ID: Asz6dM29uRJ

Bug 1416284: Have Wait allow expected exceptions when polling. r=maja_zf MozReview-Commit-ID: BPHVGOOjUaQ

Bug 1416284: Update WDSpec tests expectations. r=ato MozReview-Commit-ID: HrikhmLgamY

Bug 1416284: Dismiss alerts when we hit an UnexpectedAlertOpen error. r=ato The Browser Testing and Tools group agreed that the webdriver endpoint, when asserting for a modal, that it clears the modal on the screen and raises an an Unexpected Alert Open error. See https://github.com/w3c/webdriver/pull/1145 MozReview-Commit-ID: 1OnT1AMM0tY

servo: Merge #19335 - Unbreak docs build (from servo:jdm-patch-5); r=nox Running rustdoc on gecko-media is broken right now. Source-Repo: https://github.com/servo/servo Source-Revision: 3a08f87ec89456900da4cffda1356c02b6a9b8c8

Bug 1405252 - Enable browser_webconsole_console_logging_workers_api.js in the new frontend; r=Honza. MozReview-Commit-ID: I7b45uLfNkw

Bug 1409691 - Fix initialisation of doneReason in Capture (BackgroundPageThumbs.jsm). r=Mardak MozReview-Commit-ID: G30XiYMScHr

Bug 1415908 - Intermittent failure (nsIAutoCompleteController.getCommentAt) in browser_ext_omnibox.js. r=adw Fixes a timing bug where in certain moments matchCount may not be in sync with the current search status, due to previous results not being cleared immediately. Still delays tree updates to avoid UI flickering. Fixes a theorical timing issue in unifiedComplete where a stopped search could notify a result. Removes the no more used OnUpdateSearchResult API. MozReview-Commit-ID: COoIN4oQT4v

Bug 1405832 - part 4: ContentCacheInParent::OnEventNeedingAckHandled() shouldn't crash in release build r=m_kato For protecting main process, we should stop crashing main process in release build even when we detect our bug. However, we should keep crashing with MOZ_DIAGNOSTIC_ASSER which is enabled only on Night and Developer Edition. MozReview-Commit-ID: 5BQ46IFzXXj

Bug 1405832 - part 3: ContentCacheInParent::RequestIMEToCommitComposition() should call nsIWidget::NotifyIME() via TextComposition::RequestToCommit() r=m_kato Now, TextComposition::RequestToCommit() manages if it has already requested IME to commit or cancel composition and this is important for redundant requests. Therefore, ContentCacheInParent::RequestIMEToCommitComposition() shouldn't call nsIWidget::NotifyIME() directly. MozReview-Commit-ID: 69VpgyK9Jk5

Bug 1405832 - part 2: TextComposition::RequestToCommit() should request IME to commit or cancel composition only when it hasn't been request it yet and hasn't received commit event yet r=m_kato According to the log in crash reports, eCompositionCommitRequestHandled is sent to ContentCacheInParent twice or more for a composition. This causes breaking mPendingCompositionCount and mPendingEventsNeedingAck management. Currently, nsIWidget::NotifyIME() should be called only by TextComposition::RequestToCommit(). Therefore, the method should manage if it should request it actually. If the composition has already received eCompositionCommit(AsIs) event, it shouldn't request it because parent process may have already stated new composition and it shouldn't be broken by request for old composition. MozReview-Commit-ID: 2ekSa6EIeRP

Bug 1405832 - part 1: ContentCacheInParent::RequestIMEToCommitComposition() should increment mPendingEventsNeedingAck itself if it treat the request handled synchronously without actually requesting IME to commit composition r=m_kato This is a simple bug of ContentCacheInParent. When ContentCacheInParent::RequestIMEToCommitComposition() returns true, PuppetWidget::RequestIMEToCommitComposition() will send eCompositionCommitRequestHandled pseudo event message back to the main process. This causes counting down mPendingEventsNeedingAck in ContentCacheInParent::OnEventNeedingAckHandled(). Therefore, in the normal path, ContentCacheInParent::OnCompositionEvent() increments it for receiving the pseudo event message. However, if the tab parent has already lost focus, RequestIMEToCommitComposition() returns true without requesting native IME to commit composition. So, ContentCacheInParent::OnCompositionEvent() cannot increment mPendingEventsNeedingAck for coming eCompositionCommitRequestHandled. Therefore, RequestIMEToCommitComposition() needs to increment mPendingEventsNeedingAck by itself when it won't request IME to commit composition but it returns true. MozReview-Commit-ID: 4Alwfy8avB

Bug 1381648 - Add non blocking time to the statistics panel of netmonitor; r=Honza MozReview-Commit-ID: Anw4hTlpPjH

Bug 1408401 - Release: Bump up devtools-reps bundle to 0.15.0; r=miker MozReview-Commit-ID: ISudQK3C20A

servo: Merge #19332 - moving :dir() param serialization FIXME (from wilsoniya:moving-fixme); r=emilio <!-- Please describe your changes on the following line: --> Per emilio's comment, https://github.com/servo/servo/pull/19195#discussion_r152205644, a `FIXME` regarding `:dir()` parameter serialization has been moved. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [x] `./mach build -d` does not report any errors - [x] `./mach test-tidy` does not report any errors - [x] These changes do not require tests because they only modify comment lines <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> Source-Repo: https://github.com/servo/servo Source-Revision: 3ecd0174cc7817cdd2007850c29b8b069a845b46

Bug 1419456 - Disable full CSD support for XFCE as it does not support GDK_DECOR_BORDER, r=jhorak MozReview-Commit-ID: BFOgxJ3abrT