Bug 1416316 - 1. Move overscroll to LayerSession; r?rbarker There is some overscroll handling code in NativePanZoomController that should be moved, along with other overscroll code in LayerView, to LayerSession. LayerSession now provides a getter for OverscrollEdgeEffect, which is cleaned up to have a public API with documentation. MozReview-Commit-ID: LkKHFS8OkR7

Bug 1406936 - Add unittests for re-configuring VideoConduit; r?pehrsons This adds new tests that are a subset of the existing tests for configuration. Another option would be to use parameterized tests to get coverage of all existing tests during reconfiguration, but I don't think the additional complexity is justified at this point. MozReview-Commit-ID: F28KRYaVe1B

Bug 1406936 - Copy state when reusing SendStream in ConfigureSendMediaCodecs; r?pehrsons This is necessary for changes to encoding constraints and simulcast encodings to be picked up. MozReview-Commit-ID: JpVN0ST70Cn

Bug 1406936 - Reset FEC payloads in ConfigureRecvMediaCodecs; r?mjf MozReview-Commit-ID: CAyDUry0Ekr

Bug 1406936 - Clean up unused variables; r?pehrsons MozReview-Commit-ID: DZtmnViblGS

Bug 1417827: Convert internal char* to nsCString in DNS.h MozReview-Commit-ID: Js1mXiKaKnt

Bug 1391044 - Add wpt reftests for multiline placeholders in <textarea> and <input>. r? MozReview-Commit-ID: IXjqOQAGQU5

Bug 1241131 - Remove DevTools reload addon histograms;r=francois MozReview-Commit-ID: oq7SVGPI2t

Bug 1241131 - Remove DevTools reload addon;r=ochameau In the end I prefer to remove the addon completely, if we need it for go faster we can simply reintroduce it. MozReview-Commit-ID: GCS4ZRvwUcs

Bug 1376044 - Remove dead code left over from layers-full WR implementation. r?jrmuizel MozReview-Commit-ID: FBTm1EgJ70T

Bug 1422063 - Cannot start snap on Wayland r=rail MozReview-Commit-ID: 1GyQUqJZFra

Bug 1415665 - Very long domain names overflow from the Highlight borders. r=r1cky MozReview-Commit-ID: 5C1tHZm4gJ

Bug 1418466 - Add Connect Another Device button to relevant Sync UI. r?markh, dao MozReview-Commit-ID: 5vBKH9NejVV

Bug 1412265 - Font issues in the messages displayed for empty Highlights and Top Stories sections. r=ursula MozReview-Commit-ID: B3t1wrXPTvG

Bug 1411867 - Linux repacks detected as unofficial builds. r=k88hudson MozReview-Commit-ID: 7itcGkDxKZx

Bug 1419538 - Marionette log entries should show object details. By missing to convert a Javascript object to a packet and serializing it, no details were printed eg for session capabilities for the call to "start_session()". MozReview-Commit-ID: HdcehGpBvdA

Bug 1408227 - part 6: WSRunObject::CheckTrailingNBSP() should take |const EditorRawDOMPoint&| instead of a set of container node and offset in it r?m_kato The name, WSRunObject::CheckTrailingNBSP(), is unclear what it does. It replaces previous character of specified point with ASCII space if it is NBSP and it's not necessary. So, it should be renamed to ReplacePreviousNBSPIfUnncessary(). Additionally, it should take |const EditorRawDOMPoint&| instead of a set of container node and offset in it. MozReview-Commit-ID: 2vq46OiAzo6

Bug 1408227 - part 5: Redesign GetCharAfter(), GetCharBefore(), GetWSPointAfter() and GetWSPointBefore() of WSRunObject r?m_kato WSRunObject::GetChar(After|Before)(nsINode*, int32_t) returns next/previous character's DOM point as WSPoint. If the container node is a text node in mNodeArray, it calls WSRunObject::GetChar(After|Before)(const WSPoint&) which returns next/previous offset if the point isn't end/start of the text node. If the point is at end/start of the text node, it returns start/end of next/previous text node in mNodeArray. If the container node is not a text node in mNodeArray, it calls WSRunObject::GetWSPoint(After|Before)(). It looks for next/previous text node in mNodeArray from the point. Then, it calls WSRunObject::GetChar(After|Before)(const WSPoint&) and returns the result. So, we should rename GetCharAfter() to GetNextCharPoint(), GetCharBefore() to GetPreviousCharPoint(), GetWSPointAfter() to GetNextCharPointInternal() and GetWSPointBefore() to GetPreviousCharPointInternal(). Then, they should take |const EditorRawDOMPoint&| instead of a set of container node and offset in it. So, looks like that "WS"RunObject is not good name for this class, perhaps, AutoTextRunManager or something? But I'm still not sure. MozReview-Commit-ID: 85cX3MdlFwz

Bug 1408227 - part 4: WSRunObject::DeleteChars() should take two |const EditorRawDOMPoint&| arguments to specify a range to remove r?m_kato WSRunObject::DeleteChars() should take two |const EditorRawDOMPoint&| arguments to represent a range to remove. Additionally, this renames it to DeleteRange() because it also removes any nodes in the range. So, "Chars" isn't good word for this method's name. MozReview-Commit-ID: 5Dmxnia1JPO

Bug 1408227 - part 3: Redesign WSRunObject::FindRun() with EditorRawDOMPoint r?m_kato WSRunObject::FindRun() finds the nearest run from aPoint to specified direction. So, it uses nsContentUtils::ComparePoints() a lot. Therefore, it should use an overload which takes RawRangeBoundary. Although, it's not optimized for RawRangeBoundary, but if it'd be optimized, this method becomes faster. And this patch renames it to FindNearestRun(). MozReview-Commit-ID: 2NkR5E1st6d