635153e1dcdc442f8d72727b6fe504842b4ffa31: Bug 1306529 - OmxDataDecoder: Fix a stall issue on shutting down draft
Takuro Ashie <ashie@clear-code.com> - Tue, 27 Mar 2018 16:37:21 +0900 - rev 775966
Push 104768 by bmo:ashie@clear-code.com at Mon, 02 Apr 2018 04:38:20 +0000
Bug 1306529 - OmxDataDecoder: Fix a stall issue on shutting down Because the shutdown closure awaits finishing itself by TaskQueue::AwaitShutdownAndIdle(), the function blocks infinitely. The code is wrongly introduced at the following commit: * https://bugzilla.mozilla.org/show_bug.cgi?id=1319987 * https://hg.mozilla.org/mozilla-central/rev/b2171e3e8b69 This patch calls it on mTaskQueue intead of mOmxTaskQueue to avoid the issue. MozReview-Commit-ID: 4qmX2QlniEG
ca603ba98c9efbb9766728a62876869445924f29: Bug 1443027 - Fix the merging algorithm to pass the new tests correctly. r?mstange draft
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 23 Mar 2018 16:47:37 +1300 - rev 775965
Push 104767 by mwoodrow@mozilla.com at Mon, 02 Apr 2018 04:35:18 +0000
Bug 1443027 - Fix the merging algorithm to pass the new tests correctly. r?mstange MozReview-Commit-ID: JnglCbdhZzE * * * [mq]: update-test
5d986e41cef1f496c76c204cdf8a963a816247d3: Bug 1443027 - Add two new tests for merging behaviour. r?mstange draft
Matt Woodrow <mwoodrow@mozilla.com> - Fri, 23 Mar 2018 12:20:40 +1300 - rev 775964
Push 104767 by mwoodrow@mozilla.com at Mon, 02 Apr 2018 04:35:18 +0000
Bug 1443027 - Add two new tests for merging behaviour. r?mstange MozReview-Commit-ID: G5vgtSCdRZP
b8c671a02a4fce085433b16db998c9b04ace87db: Bug 1306529 - Add initial implementation of PureOmxPlatformLayer draft
Takuro Ashie <ashie@clear-code.com> - Wed, 28 Mar 2018 18:21:04 +0900 - rev 775963
Push 104766 by bmo:ashie@clear-code.com at Mon, 02 Apr 2018 04:30:11 +0000
Bug 1306529 - Add initial implementation of PureOmxPlatformLayer It's a concrete class of OmxPlatformLayer for accessing OpenMAX IL libraries directly. It will be usable on various embedded linux systems. Note that it's not enabled by default yet. Add the following config to your mozconfig. ac_add_options --enable-openmax TODO: Implement zero-copy mode MozReview-Commit-ID: EMEXAKzzR64
1acebeb60147f3db88515c5ca7219cf2aca873e4: Bug 1450017 - Follow-up, Move resizer style rules to minimal-xml.css draft
Timothy Guan-tin Chien <timdream@gmail.com> - Fri, 30 Mar 2018 18:32:20 +0800 - rev 775962
Push 104765 by timdream@gmail.com at Mon, 02 Apr 2018 04:27:53 +0000
Bug 1450017 - Follow-up, Move resizer style rules to minimal-xml.css Also, remove rtl resizer images and simply flip the element with CSS MozReview-Commit-ID: LEodr0aTPkM
ade9d58b9676aed8e1adf558083b595bebb1e201: Bug 1450017 - Remove the resizer binding, set resizer style in ScrollFrameHelper::CreateAnonymousContent() draft
Timothy Guan-tin Chien <timdream@gmail.com> - Fri, 30 Mar 2018 17:20:27 +0800 - rev 775961
Push 104765 by timdream@gmail.com at Mon, 02 Apr 2018 04:27:53 +0000
Bug 1450017 - Remove the resizer binding, set resizer style in ScrollFrameHelper::CreateAnonymousContent() - Figure out whether or not to apply the flipped style from ScrollFrameHelper::IsScrollbarOnRight() (specifically, ScrollFrameHelper::IsPhysicalLTR()) as it already considers Bidi and writing modes. - Remove the rtl attribute, given that we can use dir=bottomleft and dir=buttomright to explicitly apply style to the corner resizer. - Moving the reference of the platform-specific stylesheet to minimal-xul.css. MozReview-Commit-ID: 80P3hTtQD14
28b49039cde3d17921f41a9a998fc3c1318acd7c: Bug 1306529 - Add initial implementation of PureOmxPlatformLayer draft
Takuro Ashie <ashie@clear-code.com> - Wed, 28 Mar 2018 18:21:04 +0900 - rev 775960
Push 104764 by bmo:ashie@clear-code.com at Mon, 02 Apr 2018 04:06:09 +0000
Bug 1306529 - Add initial implementation of PureOmxPlatformLayer It's a concrete class of OmxPlatformLayer for accessing OpenMAX IL libraries directly. It will be usable on various embedded linux systems. Note that it's not enabled by default yet. Add the following config to your mozconfig. ac_add_options --enable-openmax TODO: Implement zero-copy mode MozReview-Commit-ID: EMEXAKzzR64
a64a0f3c1662e8b17b1062f12243dadbce6f9032: No bug, Automated HPKP preload list update from host bld-linux64-spot-303 - a=hpkp-update
ffxbld - Sun, 01 Apr 2018 19:11:09 -0700 - rev 775959
Push 104764 by bmo:ashie@clear-code.com at Mon, 02 Apr 2018 04:06:09 +0000
No bug, Automated HPKP preload list update from host bld-linux64-spot-303 - a=hpkp-update
0350fba4d89f9c6ee7c08367585ba109ad391c9f: No bug, Automated HSTS preload list update from host bld-linux64-spot-303 - a=hsts-update
ffxbld - Sun, 01 Apr 2018 19:11:05 -0700 - rev 775958
Push 104764 by bmo:ashie@clear-code.com at Mon, 02 Apr 2018 04:06:09 +0000
No bug, Automated HSTS preload list update from host bld-linux64-spot-303 - a=hsts-update
f4115882bd2b090d597174c52ac49ca7d126b6ea: Bug 1450619: Remove useless extends= from the browser bindings. r?dao draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 02 Apr 2018 05:59:51 +0200 - rev 775957
Push 104763 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 04:01:03 +0000
Bug 1450619: Remove useless extends= from the browser bindings. r?dao MozReview-Commit-ID: 9amwVpbneQl
ed72f49bc8136a28f0718cc9ffd073e875d04072: Bug 1450617: No need to ResolveTag to disable first-line on fieldsets. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 02 Apr 2018 05:52:57 +0200 - rev 775956
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 1450617: No need to ResolveTag to disable first-line on fieldsets. r?bz We don't extend HTML fieldsets with XBL, and I don't think we want to start doing that now. MozReview-Commit-ID: GiltTWXUBzZ
c3591a65807d9e23f14e56b5b26ccb7bb1b83236: Remove unused special-case in nsCSSFrameConstructor. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 02 Apr 2018 05:33:27 +0200 - rev 775955
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Remove unused special-case in nsCSSFrameConstructor. I don't feel bad making that code depend on the UA rule: https://searchfox.org/mozilla-central/rev/b80994a43e5d92c2f79160ece176127eed85dcc9/toolkit/content/xul.css#63 Chances are quite high it's broken already if we style them with other display value anyway. MozReview-Commit-ID: DBBo8jBpqFc
ef8fbe0aba97506f89f6077282859671ea006597: try: -b d -p linux64 -u all -t none draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 02 Apr 2018 05:31:46 +0200 - rev 775954
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
try: -b d -p linux64 -u all -t none Pushed via `mach try syntax` MozReview-Commit-ID: 20IrsOUnrUo
00f709ee7f284cb74a58a347dd9c9a83899eb7b3: Remove unneeded arguments from nsCSSFrameConstructor. draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 02 Apr 2018 05:30:51 +0200 - rev 775953
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Remove unneeded arguments from nsCSSFrameConstructor. They're not only unneeded, but also we call them inconsistently with the light DOM and flattened tree parent, so they're really confusing. MozReview-Commit-ID: 9u3Kp8Kpp5i
f8e1ea252c909917f751dfc41a4b959e7dc58219: Bug 509958: Move the tests for bug 1449010 to css-pseudo/ instead of selectors/. r?xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 02 Apr 2018 03:31:57 +0200 - rev 775952
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 509958: Move the tests for bug 1449010 to css-pseudo/ instead of selectors/. r?xidorn Looks like a more appropriate place. MozReview-Commit-ID: FYiyTTnAMGc
b2c94ff9d3f35c325452682d808f39b0dad0feee: Bug 509958: Unprefix :-moz-selection. r?dbaron,xidorn draft
Emilio Cobos Álvarez <emilio@crisal.io> - Sun, 25 Mar 2018 17:31:55 +0200 - rev 775951
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 509958: Unprefix :-moz-selection. r?dbaron,xidorn Our implementation is totally not what the spec says, but totally what other UAs do, see https://github.com/w3c/csswg-drafts/issues/2474. So given this is causing webcompat pain, I think we should be pragmatic and just unprefix this. We could keep serialization and getComputedStyle with ::selection working with a bit more effort, like we do for :-moz-placeholder, but I'd prefer not doing at least the serialization bit, and just alias in nsCSSPseudoElements :-moz-selection to selection too. MozReview-Commit-ID: 6lxctozRDqv
40f1d6b8def5561e696f8d7d4101d2fc4f1c9769: Bug 1339656: [css-align] Another pass of fixing align shorthand serialization. r?mats draft
Emilio Cobos Álvarez <emilio@crisal.io> - Sat, 31 Mar 2018 02:37:39 +0200 - rev 775950
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 1339656: [css-align] Another pass of fixing align shorthand serialization. r?mats Hopefully the last one. This makes us serialize correctly when one of the longhands contains "unsafe", since we can indeed represent the value using the shorthand. It also fixes the test so that it tests something due to <overflow-position> was fixed to be first in bug 1430817. MozReview-Commit-ID: AnYBt6zwnPl
c1c50627d70eb97d57be56af984e7a5164a33a65: Bug 1303605: Make LazyFC assertions actually hold. r?bz draft
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 29 Mar 2018 14:04:40 +0200 - rev 775949
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 1303605: Make LazyFC assertions actually hold. r?bz So while removing that wallpaper I started hitting the !noPrimaryFrame assertions on XBL + HMTL stuff in display-contents-xbl-3.xbl. The code was trying to assert that we had frames constructed for all the nodes in the parent chain, but we don't bail out in the !GetContentInsertionFrameFor(aContainer) in the case that it's a children element, because they actually have no insertion frame, though their children do. Move the LazyFC check after the insertion point check. That makes the previous check work on the insertion point of the child, which makes it sound. This also fixes bug 1410020, and with it a Shadow DOM test-case that was failing because the content other slot wasn't getting properly flagged, and thus the slotted content never got a frame. The other two test failures in this test are an event dispatch failure, where the position of the target is not what the test expects (we don't account for margin and padding). Filed that as bug 1450027. Also, added a test for which we have wrong layout without these patches, and that crashes with "Called Servo_Element_IsDisplayNone" with the first applied but not this one, due to the bogus check mentioned above. MozReview-Commit-ID: 6OeaVrZhTDv
fd33bfa6bab482db4cd942481f21b7eb84fad6e4: Bug 1303605: Remove the undisplayed maps. r?bz,mats draft
Emilio Cobos Álvarez <emilio@crisal.io> - Thu, 29 Mar 2018 03:49:26 +0200 - rev 775948
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 1303605: Remove the undisplayed maps. r?bz,mats This is mostly code removal, changing GetDisplayContentsStyle(..) checks by an FFI call to Servo. The tricky parts are: * MaybeCreateLazily, which I fixed to avoid setting bits under display: none stuff. This was a pre-existing problem, which was wallpapered by the sc->IsInDisplayNoneSubtree() check, which effectively made the whole assertion useless. * ContentRemoved, where we can no longer know for sure whether the element is actually display: contents if we're removing it as a response to a style change. See the comment there. That kinda sucks, but that case is relatively weird, and it's better than adding tons of complexity to handle that. * GetParentComputedStyle, which also has a comment there. Also, this function has only one caller now, so we should maybe try to remove it. The different assertions after DestroyFramesForAndRestyle are changed for a single assertion in the function itself, and the node bit used as an optimization to avoid hashtable lookups is taken back. MozReview-Commit-ID: AZm822QnhF9
a12a879089ce5722f6af658fbcd8c0a9294fc173: Bug 1420680: Remove the user font cache generation, which is also unused now. r?jfkthame draft
Emilio Cobos Álvarez <emilio@crisal.io> - Fri, 23 Mar 2018 18:09:09 +0100 - rev 775947
Push 104762 by bmo:emilio@crisal.io at Mon, 02 Apr 2018 03:56:19 +0000
Bug 1420680: Remove the user font cache generation, which is also unused now. r?jfkthame MozReview-Commit-ID: HuQg4RopOmX
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip