6909c7487def14b559d00c5181c403e36d09ee62: Bug 1368406 Use non-Windows Printf Format Specifiers in MinGW r=froydnj
Tom Ritter <tom@mozilla.com> - Mon, 29 May 2017 00:38:57 -0500 - rev 361298
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1368406 Use non-Windows Printf Format Specifiers in MinGW r=froydnj MinGW applies the gnu_printf format attribute, which expects non-Windows format specifiers. These macros were not designed to handle MinGW. MozReview-Commit-ID: HuJrK43Bg1A
c6fb400017f150d652c0b2b01f8d619f58c82931: Bug 1368589: handle the case where a RebuildAllStyleData event is posted and stylesheets are added at the same time. r=heycam
Emilio Cobos Álvarez <emilio@crisal.io> - Tue, 30 May 2017 02:46:33 +0200 - rev 361297
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1368589: handle the case where a RebuildAllStyleData event is posted and stylesheets are added at the same time. r=heycam MozReview-Commit-ID: IWiTCCo55cg
0c4c63d70d4290205431d3ac7f23ce7e12749b66: Bug 1368341 - Fixup handling of file urls in mozharness, r=ahal
James Graham <james@hoppipolla.co.uk> - Thu, 25 May 2017 14:08:03 +0100 - rev 361296
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1368341 - Fixup handling of file urls in mozharness, r=ahal MozReview-Commit-ID: 7BpUFLZttsh
c9d839d793c61078b9c953ad6bee96df8269bde8: Bug 1368342 - Add mozlog logger that goes via a queue, r=ahal
James Graham <james@hoppipolla.co.uk> - Fri, 26 May 2017 12:53:00 +0100 - rev 361295
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1368342 - Add mozlog logger that goes via a queue, r=ahal This allows subprocesses to log to a shared stream via a queue, so that we avoid the overhead of a multiprocessing Lock around all log access, but still avoid races where two processes try to log simultaneously. It's mostly useful where one process is responsible for the majority of logging, but some messages will be generated in child processes. MozReview-Commit-ID: ABl6cvpb6qI
45ed06524ff0d53dbaf58d5a5f279379d7019bb3: Bug 1368371: Address background color of animations for any theme. r=pbro
Daisuke Akatsuka <dakatsuka@mozilla.com> - Tue, 30 May 2017 16:04:33 +0900 - rev 361294
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1368371: Address background color of animations for any theme. r=pbro MozReview-Commit-ID: FKrprWzclzr
29177506860daae357a7ce2627937ade8b46760c: Bug 1368376 - Update reftest expectations. r=xidorn
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 30 May 2017 16:53:05 +0900 - rev 361293
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1368376 - Update reftest expectations. r=xidorn MozReview-Commit-ID: AD9a6P4I21s
db2635a42c74dd3dede8de90b8ed2c250d63ec16: Bug 1367740 Selection::Collapse() should reuse old nsRange instance if it's not referred by anybody r=mats
Masayuki Nakano <masayuki@d-toybox.com> - Thu, 25 May 2017 18:04:55 +0900 - rev 361292
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1367740 Selection::Collapse() should reuse old nsRange instance if it's not referred by anybody r=mats Selection::Collapse() removes all ranges first, then, adds a collapsed range which is a new instance of nsRange. However, new nsRange's initialize cost isn't cheap. It needs to add itself to mutation observer and computes common ancestor. However, Selection::Collapse() doesn't move the range to different document. If old range is reusable, we can avoid to remove old range from mutation observer and add new range to mutation observer, and also we can avoid to recompute common ancestor if the node is not changed, e.g., only offset is changed in selected node. MozReview-Commit-ID: BoCBod7WVr5
6736d54ffd89b3fe3f28b3e59a8b558517894caf: Bug 1367683 Optimize initializing nsRange r=smaug
Masayuki Nakano <masayuki@d-toybox.com> - Tue, 30 May 2017 13:18:25 +0900 - rev 361291
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1367683 Optimize initializing nsRange r=smaug nsRange::DoSetRange() adds/remove its root to/from mutation observer, initializes common ancestor, registers itself to the common ancestor, unregisters itself from old common ancestor, and notifies selection listeners of selection change. However, those runtime cost is expensive but on the other hand, a lot of callers set both start and end of the range and that causes calling DoSetRange() twice. This patch renames Set() to SetStartAndEnd() for easier to understand the meaning and make it call DoSetRange() only once. MozReview-Commit-ID: FRV55tuBAgg
ee035e1480b0c216099a39d491bf2a5974e54a02: servo: Merge #17089 - Support currentColor for fill and stroke (from hiikezoe:current-color-for-fill-and-stroke); r=xidorn.
Hiroyuki Ikezoe <hikezoe@mozilla.com> - Tue, 30 May 2017 01:47:44 -0500 - rev 361290
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
servo: Merge #17089 - Support currentColor for fill and stroke (from hiikezoe:current-color-for-fill-and-stroke); r=xidorn. <!-- Please describe your changes on the following line: --> This is a PR for https://bugzilla.mozilla.org/show_bug.cgi?id=1368376 --- <!-- 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 it's for stylo Source-Repo: https://github.com/servo/servo Source-Revision: 9e89b0a2293596f970b60307fff42f955083ca84
53c2fb33f93151ee43fae606585098daa27dd895: Bug 1345898: P2. Flush rather than drain decoder. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 30 May 2017 00:30:54 +0200 - rev 361289
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1345898: P2. Flush rather than drain decoder. r=gerald When encountering a change of stream ID while performing an internal seek to resume from the last playback position (following WAITING_FOR_DATA), we may as well perform a flush rather than a drain as the decoded data won't be used anyway. MozReview-Commit-ID: E7wgTndTThs
7121a08a9c2a4cb7574583d87e754ac2907aa89b: Bug 1345898: P1. Add debugging info. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Mon, 29 May 2017 10:41:36 +0200 - rev 361288
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1345898: P1. Add debugging info. r=gerald MozReview-Commit-ID: GkURaX9bCDZ
1e51fbdefff879e7ce0258dfac8df1456ab3487a: Bug 1362165: P12. Updated wpt expectation. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 26 May 2017 23:26:15 +0200 - rev 361287
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P12. Updated wpt expectation. r=gerald New test will error until bug 1367993 is fixed. MozReview-Commit-ID: KgyquX6klE8
138425350cc671dc20e26b2b2ba019bb2ae85c1f: Bug 1362165: Correct test. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 26 May 2017 23:15:38 +0200 - rev 361286
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: Correct test. r=gerald the durationchange event will be queued during the initialization segment received algorithm. Only once the init segment has been fully processed will update/updateend be queued. As such, the updateend event must be fired before being able to call appendBuffer once again. MozReview-Commit-ID: GYQNOwWZ7DH
3329385fcf2d39197bb9aae5794c5429d1ccfde4: Bug 1362165: Add web platform test. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 11 May 2017 10:43:25 +0200 - rev 361285
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: Add web platform test. r=gerald readyState is supposed to be updated during MSE's Initialization Segment Received and Coded Frame Processing algorithm. Only then would the appendBuffer operation terminates by queueing the update/updateend events. These tests ensure that loadedmetadata and loadeddata are fired first. MozReview-Commit-ID: BJ5gISQRA7B
2ba56b296e40a529b1b58f27b36e68248cf9500a: Bug 1362165: P9. Update mochitests. r=jwwang
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 26 May 2017 20:54:36 +0200 - rev 361284
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P9. Update mochitests. r=jwwang I'm not sure what this mochitest was supposed to test, but it was doing it wrong anyway. MozReview-Commit-ID: BexSN7YgXwj
be4b872ba9092c86378faacc94c19c93ad8a5c84: Bug 1362165: P8. Fix mochitests. r=jwwang
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 26 May 2017 10:36:23 +0200 - rev 361283
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P8. Fix mochitests. r=jwwang Per spec loadedmetadata should be fired before updateend. fetchAndLoad want on the updateend event. So we can't wait for the loadedmetadata event only after updateend has been fired. MozReview-Commit-ID: BprzynZ8t1U
846a4761d0cde831bffe4301827fd566e9bf5caf: Bug 1362165: P7. Only complete appendBuffer once readyState has changed. r=jwwang
Jean-Yves Avenard <jyavenard@mozilla.com> - Tue, 09 May 2017 12:23:11 +0200 - rev 361282
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P7. Only complete appendBuffer once readyState has changed. r=jwwang MSE specs require that the readyState be modified during either the Initialization Segment Received or the Coded Frame Processing algorithms. At this stage, we only handle the Initialization Segment part (readyState moving from HAVE_NOTHING to HAVE_METADATA) MozReview-Commit-ID: KBnnWuHJ6Om
55f7558b7c52281d3d8fc5e1cea26963b0cb2585: Bug 1362165: P6. Only use sourcebuffer again once previous operation completed. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Wed, 03 May 2017 11:50:33 +0200 - rev 361281
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P6. Only use sourcebuffer again once previous operation completed. r=gerald It was incorrect to assume that once "loadeddata" event fired the sourcebuffer would be usable again. Only the "updateend" event guarantees such condition. MozReview-Commit-ID: HcyaLWjjBlp
bb63055aef6c9842e8fa7370071eb22c9d2ecbc3: Bug 1362165: P5. Don't assume that when stalling all data has been loaded. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 28 Apr 2017 17:18:43 +0200 - rev 361280
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P5. Don't assume that when stalling all data has been loaded. r=gerald The stalled event can be fired as playback is starting and data has yet to be processed. So instead we wait for playback to reach the end. MozReview-Commit-ID: 4W3M5tee2HD
5334cc6d0ea9b47325f4d6fcf4dab59307d12d55: Bug 1362165: P4. Don't assume the duration found when reading metadata will be the final one. r=gerald
Jean-Yves Avenard <jyavenard@mozilla.com> - Fri, 28 Apr 2017 16:16:51 +0200 - rev 361279
Push 31924 by ryanvm@gmail.com at Tue, 30 May 2017 20:08:50 +0000
Bug 1362165: P4. Don't assume the duration found when reading metadata will be the final one. r=gerald When endOfStream() is called, the duration is changed to that of the last buffered frame's end time. The ended event will only be fired if currentTime is equal to the duration. So if the duration has changed following a call to endOfStream, then playback won't be considered as ended. MozReview-Commit-ID: DBu3LorwFTI
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip