EditorBase parameter of GetTextNode is unnecessary because it uses static method only. Also, we should return nsINode to reduce QI.
MozReview-Commit-ID: 3KazYFcr899
--HG--
extra : rebase_source : 092bbcc84d7c1e7174029bb90f606f3953fe8597
Update the tooltool manifests for the android builds to include
support for the i686-linux-android target.
MozReview-Commit-ID: EyALhnfG4Kz
--HG--
extra : rebase_source : a85b8c1509458e1f5a8f8eae163e38edd1c363ce
Previously for the spacing at the top and bottom of the tabs grid panel we had
the total desired vertical spacing set on the RecyclerView padding, but then
there was also an additional half spacing coming from the ItemDecoration padding
in the top and bottom rows. Here we decrease the RecyclerView vertical padding
to account for the ItemDecoration vertical padding.
The alternative route of keeping full RecyclerView padding and then having the
ItemDecoration adjust itself depending on its position turned out to not "just
work": for example, if span count is three and you have four tabs, then the
first three tabs have half padding along their bottoms (since there are two
rows), but then when you close tab 4, there's now only one row and so the three
tabs should have no padding along their bottoms (since the RecyclerView already
has its own full padding), *but only tab 3 gets its ItemDecoration updated
automatically*, so it gets 0 bottom padding, but its row still has other tabs
with half bottom padding, so a) there's still too much bottom padding in that
row coming from tabs 1 and 2, and b) tab 3 sits too far down in its space
because it doesn't have the bottom padding that tabs 1 and 2 do.
That issue could be fixed by updating all ItemDecorations after each close, but
the patch here is both simpler and leads to less runtime work.
MozReview-Commit-ID: 2WeZ6QdfIF4
--HG--
extra : rebase_source : 85aec8adfdaacac7062827e273cf697c09167d63
When we jump to fullscreen, the OS sends a WM_MOUSELEAVE, which we turn into a eMouseExitFromWidget. The eMouseEnterIntoWidget was previously only sent when the mouse moved into the widget, which required the mouse to move. When entering fullscreen, we want the eMouseEnterIntoWidget to happen right away.
This test case can be pass. Fixed in bug 1133483.
MozReview-Commit-ID: I092tEm130d
--HG--
extra : rebase_source : d541f40e723a2546d669de1a3ef1a7017264e1a8