The flex-workshop URL is 404, I think you meant this one instead:
http://fantasai.inkedblade.net/style/events/flexbox-workshop
On Wed, Jan 13, 2016 at 3:01 AM, fantasai
wrote:
> I've started doing a series of workshops inviting web authors
> to get together and do an in-depth study of some of t
Please see https://github.com/whatwg/html/issues/512
Right now this is in the "does anyone have an objection to the basic
idea?" stage. So if someone does, please speak up!
I've already noted a possible concern about abuse, but Promise and
MutationObserver kinda allow that already; it just t
In principle, I don't see any reason not to do this.
- Kyle
On Wed, Jan 13, 2016 at 1:59 PM, Boris Zbarsky wrote:
> Please see https://github.com/whatwg/html/issues/512
>
> Right now this is in the "does anyone have an objection to the basic
> idea?" stage. So if someone does, please speak up!
Sounds good to me as well. As long as it's very clearly defined that
this doesn't return to the event loop and so UI events, timers,
network events, etc MUST NOT be processed between the tasks under any
circumstances.
I.e. something like:
function spinner() {
window.enqueueMicrotask(spinner)
}
s
GTests are now run from their own job on Treeherder instead of during the
build in "make check'. They can be found under the "GTest" symbol on
treeherder on all integration branches, and can be added to try pushes with
"-u gtest" (they will run with "-u all").
As an effect of this change we're now
I think this makes sense.
On 2016-01-13 4:59 PM, Boris Zbarsky wrote:
Please see https://github.com/whatwg/html/issues/512
Right now this is in the "does anyone have an objection to the basic
idea?" stage. So if someone does, please speak up!
I've already noted a possible concern about abuse,
On Thu, Jan 14, 2016 at 10:22 AM, Christopher Manchester
wrote:
> GTests are now run from their own job on Treeherder instead of during the
> build in "make check'. They can be found under the "GTest" symbol on
> treeherder on all integration branches, and can be added to try pushes with
> "-u gte
> Are C++ units tests that don't use GTest still run as part of the build job?
Chris told me that non-GTest C++ unit tests run in the "Cpp" job, and
that one-off test programs in make check targets will continue to run
as part of the build job.
Nick
___
8 matches
Mail list logo
