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

Bug 1390396 - Reenable mochitests for custom elements lifecycle callbacks; r=smaug Attribute changed callback now is fired only when the attribute is in observedAttributes list which is introduced in latest spec, so in this patch, we change the tests for attribute changed callback to use customElements.define() to register customElements definition instead. MozReview-Commit-ID: 2s1qj3UsFUS

Bug 1419665 - Support babel object-rest-spread syntax for launchpad r=Honza MozReview-Commit-ID: JC6vWNMp3a7

Bug 1418652: Migrate comm-central configure options to moz.configure; r=chmanchester,Fallen MozReview-Commit-ID: JBRsgBnB9oF

Bug 1418652: Remove non-existant comm-centrall configure option; r=chmanchester,Fallen It was removed in Bug 1318966. MozReview-Commit-ID: 6fckjVDubTT

Bug 1413270 - Document how to interpret use counter data. r=chutten This patch adds a new section to the use counters Telemetry docs that explains how one should think of the data gathered using them. MozReview-Commit-ID: 5mYIYubWxaz

Bug 1417498 - Account for aRequest being null in onLocationChange. r=JanH According to the documentation, aRequest may be null in some cases, and one such case is when the location change was caused by a page using the history API. MozReview-Commit-ID: AUlHBgzaKDX

Bug 1417658 - Move export_suffixes into GeneratedFile; r=nalexander I believe all backends will need to know which GeneratedFiles are needed before compilation can start, so we should make that an attribute of the object. Each backend can then make its own decision about what to do with the different types of GeneratedFiles. MozReview-Commit-ID: ByburRx540b

Bug 1415739 - Use type/autocomplete properties, instead of attributes, to decide whether to save FormData. r=mikedeboer The property values are already normalized according to the spec. MozReview-Commit-ID: DbKZf9KXCji

Bug 1419792 - Shapes highlighter drawn inaccurately for shape-outside with margins. r=gl MozReview-Commit-ID: 1MGCvsDXJ6O

Bug 1407423 - Part 3: Update Puppet Device Implementation,r=daoshengmu - Update prefs to accomodate tests, disabling enumeration throttling - Updated Puppet display and controller implementation to act more like the actual devices. - Updated tests to ensure that they explicitly create a VR mock display and don't create duplicate mock displays. MozReview-Commit-ID: 6RPVqekG2je

Bug 1407423 - Part 2: Update gfxVRGVR to match refactoring,r=rbarker MozReview-Commit-ID: DmKnEZanQ3f

Bug 1407423 - Ensure that any time we have loaded the Oculus runtime libary, we are polling ShouldQuit,r=daoshengmu - Ensure ovr_GetSessionStatus is polled even when a VR presentation is not active. - When we fail to initialize an Oculus Session or detect VR hardware, immediately unload the Oculus Library as we can't poll for ShouldQuit without a valid Oculus session. - When we poll ovr_GetSessionStatus, we are now updating the mounted state in VRDisplayInfo::mIsMounted. - Added prefs to control enumeration throttling and timeout to release VR hardware when inactive. - Some refactoring to make frame loop more understandable and less brittle. - When throttling enumeration, we ensure that all other VR apis also throttle enumeration so that they don't pick up the same device during throttling. - Some long functions in VRManager have been broken up and had their inner-workings documented in more detail. MozReview-Commit-ID: CEYwwQ9mYd0