I can write an example of a script that would produce such a situation, if
desired.
Yes, please. I would love to have a concrete example.
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
One of this year's wonderful Servo interns, Tim Kuehn, will be
presenting his project this Thursday, August 1st at 2:30pm Pacific /
12:30am UTC.
You can watch it live on Air Mozilla https://air.mozilla.org/ and it
will be archived on Air Mozilla afterwards as well.
After adding better profiling
We are starting to plan what will go in the first numbered version of
Servo. The proposal is to gate the initial release on a set of
criteria, and after that releases will be time based and include
whatever features are done by the release date (much like Rust).
We need to define what the release
Love it! This is a game changer for web development. I mean it.
Does this mean you are no longer worried about that suggested benchmark? :)
We're trying to find some early benchmarks, so this kind of feedback
is valuable. I figured I'd try and close the loop here to see if this
addresses your
Two more of our amazing Servo interns are finishing up, and will be
presenting their work tomorrow.
Eric Atkinson will be presenting Layout in Servo: Parallel and Rustic
Tree Traversals at 2pm / 0:00 UTC.
Eston Schweickart will be presenting A Forest of Quadtrees: The
Graphics of Servo at 2:30pm
https://github.com/mozilla/servo/wiki/Meeting-2013-08-12
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
I'm working on the agenda for the upcoming team meeting in Mountain View.
What do people think about focusing our efforts getting some subset of
Dromaeo working? I suspect this would involve implementing DOM APIs
and measuring performance.
It seems like an easy set of tasks to split up among
Dromaeo has a bunch of DOM micro-ish-benchmarks on the one hand and
microbenchmarks of common JS libraries (jquery, etc) on the other. Just
make sure to run the DOM and CSS portions of it, not the whole thing.
The DOM ones were specifically what I had in mind. CSS testing
probably doesn't
Monday is Labor Day in the US, and so we won't have our usual Servo meeting.
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
We'll be in The Bridge every day except for Monday afternoon when
we'll be in Holodeck. I think Holodeck doesn't have a Vidyo setup, but
there will be one in The Bridge for those of you who wish to join
remotely.
jack.
___
dev-servo mailing list
You can find a draft here:
https://etherpad.mozilla.org/Servo-team-meeting
Feedback welcome.
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
There's a lot of great work being done right now, especially in
filling out the DOM implementation. jdm has a big list of bugs[1] that
are getting picked off one by one. If you are looking to contribute to
Servo, this is a good place to start. The work is pretty well defined
and there are examples
https://github.com/mozilla/servo/wiki/Meeting-2013-09-09
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
That being said, I have a
few concerns I'd like to voice over the handful of test harnesses that have
been implemented in Rust (I see reftest, contenttest.. are there more?).
reftest and contenttest are the automated ones we have currently aside
from unit tests. Only the latter currently runs
http://ariya.ofilabs.com/2013/06/optimizing-css3-for-gpu-compositing.html
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Right now we have this TreeNode abstraction that has been around for a
long time and has lost its original purpose (whatever that was). It's
only job right now appears to be to break the cyclic dependency
between the script and style crates.
Does anyone have strong feelings as to whether this is
Szia!
There is a list of collected presentations related to Servo here:
https://github.com/mozilla/servo/wiki/Videos-and-presentations
and one for Rust: https://github.com/mozilla/rust/wiki/Docs#presentations
The best way to demo servo are the following files which you can find
in
Need to check whether these are OS objects, and if so, whether they're
thread safe on all platforms. Linux fontconfig in particular is particularly
bad, as we've discovered. (You need a lock around the whole thing unless you
have a *very* recent version, newer than the one in many distros.) :(
Is it possible to programmatically identify CSS rules or page layouts which
would benefit from the parallelism that Servo potentially offers? For the CSS
un/prefixing debate I/we had some success in deploying web crawlers that
parsed and summarized millions of CSS rules from thousands of
Assuming this is enough precision for layout, I'd like to see neon
versions before we landed anything like this. Will the API a user sees
look the same? In other words, is the change localized to MaybeAuto's
implementation?
Also, speaking of these SIMD optimizations, does rustc have a compiler
https://github.com/mozilla/servo/wiki/Meeting-2014-05-19
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Most of Servo's dependencies require a modernish version of autoconf,
but Spidermonkey requires exactly 2.13. Both are needed. In most linux
distros 2.13 is in the autoconf213 or autoconf2.13 package and can be
installed at the same time as the normal autoconf package. I believe
this is true of
This looks like a huge improvement. Can you give us an idea of what the
CompositorData type looks like?
jack.
On Mon, Jun 30, 2014 at 9:33 AM, Martin Robinson mrobin...@igalia.com
wrote:
I've been working on a redesign of the compositor, in order to make
rust-layers more functional as a
I've enabled |make tidy| on Travis, and expanded it to check for
whitespace errors as well as missing license blocks (which it did
before). [1] For reference, no longer allowed are:
Did this get disabled at some pint? `make tidy` used to run as part of
`make check`. Or perhaps I'm confusing
Even more conflicts were discovered, and we lost all the EU crowd. I
moved it to tomorrow at the regular time (10am Pacific).
jack.
On Mon, Jul 28, 2014 at 10:09 AM, Jack Moffitt j...@metajack.im wrote:
For those of you who attend the Monday Servo project meeting, it has
been rescheduled today
I saw you guys mentioned my name under new contributors on the servo blog
;) Thanks!
Welcome to the team :)
Another way to find E-Easy bugs is to search for FIXME in the
codebase. Whenever we do Rust upgrades, there are always small
workarounds for various things. The FIXMEs live a lot longer
This seems relevant to us as well.
jack.
-- Forwarded message --
From: Gervase Markham g...@mozilla.org
Date: Wed, Sep 3, 2014 at 7:11 AM
Subject: Licensing of tests
To: dev-plann...@lists.mozilla.org
A case has been made for changing our licensing policy such that _tests_
On Tuesday, the Rust team will be discussing inheritance in Rust. One
of the primary use cases for this is Servo's DOM. Please take a look
at http://discuss.rust-lang.org/t/summary-of-efficient-inheritance-rfcs/494
and we'll discuss in the Monday Servo meeting.
jack.
For some reason a single PR caused buildbot not to receive updates.
I've temporarily closed that PR and it seems to have restored
operation. I'll debug the PR that failed tomorrow morning.
jack.
On Tue, Oct 7, 2014 at 7:09 PM, Gilles Leblanc gilles.lebl...@gmail.com wrote:
In the build queue
All the previous Rust meetups in Mozilla offices have been, so I think
this one will be no exception :)
jack.
On Thu, Oct 16, 2014 at 8:47 AM, Gilles Leblanc
gilles.lebl...@gmail.com wrote:
That sounds like a great meetup.
Do you know if the meetup will either be broadcasted over the web or
We pull in other pieces of Gecko outside of Azure proper in order to use
Azure in Servo.
As I remember, this is unintentional. Azure is now hosted out of tree
and shouldn't have this problem anymore, although I haven't checked. I
talked to Bas about this last October because at that time I had
Incidentally, I see no reason to move away from Azure, given how nice
Direct2D is on Windows.
Chrome uses Skia on windows right? So this apparently isn't a big
enough win for them to justify a wrapper. I'm guessing they use ANGLES
there. I think the assumption in the room was that we could
We should experiment with parallel software rendering. Using skia on
many cores might be faster than using D2D in practice, for example.
Glad to hear you say that, because the first part of that experiment
(parallel CPU rendering) is already done and on by default in Servo's master
branch.
However, do see Brian Smith's recent proposal on this topic:
https://briansmith.org/referrer-01.html
This looks extremely reasonable. Is there any reason not to adopt this
in Servo and see if it works?
jack.
___
dev-servo mailing list
`git submodule sync` fixed this for me. Perhaps mach should do this as
part of it's bootstrapping/prep.
jack.
On Thu, Feb 12, 2015 at 7:07 PM, Tetsuharu OHZEKI
saneyuki.s...@gmail.com wrote:
Have you tried `mach update-submodules` before mach clean? it might resolve
your problem.
Tetsuharu
We've discussed this several times and the response was always
positive. It hasn't caused a bunch of trouble to rust upgrade for the
deps that already track master. If we upgrade deps often enough, we
will probably already have a version of the code that will work when
we upgrade Servo. This has
Several of us will be in partner meetings tomorrow so I've canceled
the Servo meeting tomorrow.
You can still put stuff on the agenda and we will cover it next week,
or just bring it up here on the mailing list or send me email directly
if it can't wait.
jack.
The Servo meeting for US and Asia is locked to Korean time, which
doesn't have a daylight savings time change. Therefore, for the rest
of us who do, this meeting is an hour later in the day.
Today's meeting will start in about an hour, 5PM Pacific.
jack.
I semi-randomly[1] assigned all open PRs to people. Please figure out
the appropriate next action for the PR (often just reviewing). If the
PR is abandoned, please take it over.
Also, Josh has got an incredible number of reviews on his plate. I
encourage him to delegate some of these to the rest
A good place to start is generally to add some more implementations of CSS
properties that nearby implementations. For example, Patrick has
implemented several transitions, but I don't think he's done all of them.
The advantage of starting like that is that you have the implemented
versions to use
I'm +1 to make ./mach build do release builds and add new --debug
flags. Also I think Manish's idea of triggering a daily debug build
seems like a good idea.
However, what is the current time difference between debug and release
builds these days?
jack.
On Tue, Feb 24, 2015 at 7:21 AM, Manish
Several of us will be in a partner planning meeting all day on Monday,
so I'm canceling the regular project meeting for that day.
If you have any pressing agenda please use IRC or the mailing list and
we'll address them that way.
jack.
___
dev-servo
+1 from me. Most of our raw API wrappers have been better done by the
community. We were lazy when we created them in the interest of
standing up Servo as quickly as possible.
jack.
On Mon, Apr 6, 2015 at 11:39 AM, Josh Matthews j...@joshmatthews.net wrote:
Assuming the author is willing, is
Does anyone have any opposition to me opening pull requests on all non-servo
repositories that add links (inside READMEs) to their respective module on
doc.servo.org?
Ideally, each individual repository would build its own documentation for
hosting on GitHub Pages, but I think just
The mac3 builder will continue to run css tests and will now become red
when the build fails. This will not block PRs though.
Are they unreliable there? What is the reason for this difference?
jack.
___
dev-servo mailing list
For the memory profiler, it seems like some socket abstraction would
work fine. The master process can just listen on a IPC socket and the
messages can get broadcast to it.
jack.
On Thu, Jun 18, 2015 at 6:50 PM, Nicholas Nethercote
n.netherc...@gmail.com wrote:
On Thu, Jun 18, 2015 at 5:45 PM,
Cargo target-dir sharing (soon to be enabled by
https://github.com/servo/servo/pull/6306) will also not rebuild
dependencies that haven't changed. We could add the ability to put the
target directory outside of the servo tree (it's a trivial change, and
cargo already supports this). It actually
We got a request to publish rust-geom on crates.io, but someone had
already put their geom library there. We made the decision to find a
new name for our library and settled on euclid.
The repo has been renamed and is now published on crates.io
(https://crates.io/crates/euclid).
Servo is not yet
We are switching Servo's dependencies to be managed by Homu instead of
manually merged. Please use `@bors-servo: r+` on all Servo
organization repos from now on.
Not all repos are yet converted however, but just pretend they are and
if you fail to see Homu immediately start working, let someone
I've written a draft of a blog post about memory profiling in Firefox
vs. Servo, which focuses on the Rust features that make the task more
pleasant in Servo. There's a draft copy here:
http://njn.valgrind.org/measuring.html
Very nice!
One question I still had at the end was whether things
Who should that be? Everyone on https://github.com/orgs/servo/teams/owners ?
Everyone on https://github.com/orgs/servo/people ? Some other set of people?
Or something different for each package, based on people’s area of interest?
The minimum set should probably be Lars and myself since we
I’m in favor of a single alphabetical-order group.
Nicholas's points are all valid, and while I kind of like the
groupings, I have no objection to a single alphabetical list.
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
> Does the early meeting need to move at all? I thought what promted this was
> conflicts with the late meeting time.
Not necessarily, but there was interest in having both times on the
same day to reduce confusion.
jack.
___
dev-servo mailing list
As discussed on yesterday's call, I'd like to propose moving the
meeting times to Tuesdays (in the US) as there are some conflicts with
the current times. I'd also like to switch the afternoon time slot to
follow US daylight savings time like the other slot, so that both
meetings move together.
Moving the meeting later is not great since it needs to be early for
the comfort of people in Europe.
Is Wednesday better? Yours was the only conflict brought to my attention.
jack.
On Tue, Sep 29, 2015 at 12:38 PM, Josh Matthews <j...@joshmatthews.net> wrote:
> On 2015-09-29 11:38
rocksdb+rust in production (https://github.com/spacejam/rust-rocksdb?)
>
> -Manish Goregaokar
>
> On Tue, Dec 15, 2015 at 8:57 AM, Jack Moffitt <j...@metajack.im> wrote:
>>
>> Probably the easiest way to start is to get the database backend
>> sorted. We've talked a
Probably the easiest way to start is to get the database backend
sorted. We've talked about using LevelDB for this in the past, but I'm
not sure if there is an existing Rust wrapper for that or not. If not,
creating one might be a good way to get started.
jack.
On Mon, Dec 14, 2015 at 8:20 PM,
Our heads being full of Mozlando meetings, I think there is little new
to talk about. I've canceled today's meeting, but ping in IRC if there
is anything that can't wait until next week.
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
I'm canceling the meetings today and next week for the holidays. Many
of the team is out (especially next week). Please use the meeting time
to review some PRs if you are still around :)
Happy holidays everyone!
jack.
___
dev-servo mailing list
> It would be nice if you can "drop in" features from above without requiring
> daisy chaining, but AFAICT that's not always doable.
>
> It is possible currently to do `cargo build --features
> net/devices/nameoffeature` without polluting cargo.tomls, but IIRC this
> isn't always supposed to work
> 2) Move webrender and webrender_traits back into the Servo repository.
>
> Because WebRender and Stylo are the two biggest projects that will
> need to be worked on in a cross-cutting way across Firefox and Servo,
> we'd like to have them out of a separate GitHub repo (with its "update
>
How is this done in Gecko?
We learn something is not visible during one of the various cullings
of WebRender. So I guess the idea would be to have some notification
you send when something goes from visible previously to invisible. I
suppose there is an analog when doing flow construction that
> The API is probably fine, but there will be a *ton* of coordinated changes
> across Firefox/WR here. Shader tuning, implementation bug fixing, etc. None
> of these changes will be tested by the autolander in the context of Firefox
> if WR is a separate repo, so they will have to get "bounced"
I thought we had CI checks for duplicate packages, but it seems that
is not the case? Or at least I did not seem them in .etc/ci. I can't
even find an issue for it now :(
In any case, I think this can be automated by CI to catch the problem.
In general this is allowed by Cargo but we probably
Based on feedback from everyone, we've decided to move the late Servo
meeting to 2pm Pacific (2 hour earlier than it currently is).
I've updated the meeting in the calendar, but if you don't use that,
please made adjustments accordingly.
The next meeting is the early meeting on Monday, so this
Some of the team is together in Portland this week, and there was
nothing on the agenda, so I've cancel the meeting today so everyone
can keep working.
If there is anything that needs attention, please ping us in IRC.
jack.
___
dev-servo mailing list
Since it is a holiday in US and Canada, we're canceling the meeting
today. See everyone next week.
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On Wed, Mar 9, 2016 at 8:25 AM, Josh Matthews wrote:
> Hi reviewers of Servo! As you've noticed, we recently started assigning
> reviewers to new PRs by random selection. Sometimes this means that a
> reviewer ends up assigned to a PR which they don't feel comfortable
>
There was no agenda to discuss, so we'll forgo today's meeting. See
you all in IRC :)
jack.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
I'm willing to give it a try. I'd suggest shortening up the text of
the third one, and for the fourth one, add a "because:" so that they
have to justify their lack of tests.
jack.
On Fri, May 6, 2016 at 9:13 AM, Josh Matthews wrote:
> Github introduced templates for
> So is the idea that people without the ability to use webrender would need
> to use the -c flag? The linux machine I use for Servo development yields the
> "GL context creation failed" error, so if there were a way to make this
> happen transparently that would be pretty great.
Yes. I expect
On Mon, Mar 28, 2016 at 11:33 AM, <lbergst...@mozilla.com> wrote:
> On Monday, March 21, 2016 at 11:45:06 AM UTC-5, Jack Moffitt wrote:
>> I propose the following straw man transition plan:
>>
>> 1. Keep -c, -g, -w command line options as they are, but switch the
>
I hear no objections, so I'm canceling the standing meeting.
jack.
On Sun, Apr 17, 2016 at 11:31 AM, Lars Bergstrom wrote:
> On Thu, Apr 14, 2016 at 2:46 PM, Manish Goregaokar
> wrote:
>>
>> So yeah, +1 for cancelling. I do look forward to the
We have some data on which intermittents are causing the most
problems. I've collected this data on this meta bug:
https://github.com/servo/servo/issues/12424
Many of the worst intermittents are already disabled, but some are
not. I propose:
1) We immediately disable the listed tests. It is not
ayout threads together into one process. Maybe two, one for
> high-security sites and one for all other sites.
>
> Patrick
>
>
> On Aug 2, 2016 6:47 PM, "Paul Rouget" <p...@mozilla.com> wrote:
>>
>> On Tue, Aug 2, 2016 at 6:47 PM, Jack Moffitt <j...@m
> First, is multiprocess and sandboxing actively supported?
I tested this right before the nightly release, and it was working
fine and didn't seem to have bad performance. Note that you can run -M
or -M and -S, but not -S by itself (which doesn't make sense). Also
note that -M and -S probably
e benefits. Or perhaps an additional one for low-security ones
> such as ads (perhaps based on tracking blocking lists).
>
> On Wed, Aug 3, 2016 at 5:43 AM, Jack Moffitt <j...@metajack.im> wrote:
>
>> Each process is a sandboxing boundary. Without security as a concern
>>
It looks like they've refactored how the layout algorithm works, which
is pretty interesting. Down in the performance section however, there
seems to be a mix of ideas and very few of them involve parallelism.
For example, they want to enable speculative layout to precalculate
future animation
This is really cool! Also, "Right behind you" is the best location ever.
It seems like we should pick one of these and include it on some
future contributor stats page. Also, ,this is a nice screenshot for
TWiS next week :)
jack.
On Wed, Jul 6, 2016 at 8:15 PM, Shing Lyu
> Actually (though I've been busy implementing other things), I've been
> planning a somewhat different way to solve the scalability problems that I
> called "auto rollup."
This is more or less the direction I've thought we'd move in as well.
Basically try in bigger batches but have blame
Thanks everyone who helped; it was quite the long home stretch!
Blog post: https://blog.servo.org/2016/06/30/servo-nightlies/
Demo video: https://www.youtube.com/watch?v=jJXW072MatI
Enjoy,
the servo team
___
dev-servo mailing list
We've been using Paul's list to keep track of things thus far:
http://paulrouget.com/bhtml-servo-issues/
jack.
On Wed, Jun 29, 2016 at 4:59 AM, Manish Goregaokar
wrote:
> I've created a new milestone on GitHub, Tech Demo
>
Welcome!
jack.
On Fri, Jul 1, 2016 at 11:47 AM, Malisa Smith wrote:
> Hi everyone,
>
> Just wanted to introduce myself (@malisas7) as one-half of Team JaM, with
> Jeena Lee (@theJeenaLee) as the other half.
>
> Our Rails Girls Summer of Code project is to implement the
Is it possible to get the correct stack somehow?
jack.
On Sat, Jul 2, 2016 at 3:33 PM, Josh Matthews wrote:
> Hi everyone! To my dismay, I have realized that the stack traces for
> automated crash reports cannot be trusted for the purposes of marking issues
> as
> Does this also mean servo is going to move off of homu, and lose pre-commit
> testing? How is the contributor experience going to be impacted by the
> change?
Servo's own tests will still run pre-commit for both Servo and Gecko
changes. Some subset of Gecko test will run post commit. If you
To followup, the core team is in favor of this change, and since it
already landed, there's nothing more to do.
I do think it's useful to decide what to do about the old repo. Do we
put a big sign on it pointing to servo/servo? Or do we keep up synced
to take PRs?
jack.
On Thu, Feb 9, 2017 at
I think the complexity of the wpt-style setup is overkill, but I think
we could do something to alleviate the community participation issue.
We could perhaps keep the rust-selectors repo around and following the
Servo in-tree one. PRs could still be done by external contributors
the rust-selectors
> In general, I posit that Mozilla completely, utterly, lost against V8 in the
> embedded department in a huge part because of this mono-repository thing
> where everything is muddled together.
I don't think anyone is disagreeing with you on this point. The plan
is as it always has been - to
> My point is that I believe it's possible to create a setup doing full
> pre-commit testing -- with all the advantages it brings over post-commit
> testing -- while avoiding the scalability problems of the existing setup
> is Servo.
It depends what you mean by scalability. Doesn't pipelining the
Welcome! I think it's hard to understate the pain that intermittents
cause, and we're very grateful for the work you are undertaking to
help address them.
jack.
On Tue, Feb 28, 2017 at 9:46 AM, Erika Eill wrote:
> Hello!
>
> We are a team of three NC State graduate students in
I agree that seems noisy and irrelevant I could have sworn we
previously had a patch to homu to remove the template. Did this
regress or am I misremembering?
jack.
On Wed, Mar 1, 2017 at 10:29 AM, Emilio Cobos Álvarez <emi...@crisal.io> wrote:
> On Wed, Mar 01, 2017 at 08:13:36AM -0
Also, if anyone has new E-easy's, it would be good to get them filed
before this event so that the group has a reasonable amount to work
on.
jack.
On Tue, Aug 23, 2016 at 3:13 AM, Shing Lyu wrote:
> Hi,
>
> I'll attend a bootcamp called "Taiwan Code Sprint", which is aimed to
> You seem to have a lot of confidence in MoCo's ability to support a
> project on its own, and very little confidence in the Rust ecosystem
> to maintain its chosen solutions. It seems very unlikely that Rust
> projects will move to NSS over OpenSSL or *ring* once bindings for NSS
> are available
> NSS doesn’t currently support building as static libraries. Do you think it
> would be better to try to use the system NSS or ship the libraries?
Depending on the system one exclusively is one reason why our OpenSSL
bindings suck. So we have to have it built by Cargo as a fallback.
jack.
> One thing I’m also looking at is how it could be possible to make the Servo
> crypto library interchangeable via traitization (I might be making up words
> now). That way, people who want to use Rust crypto can do so, and people who
> would prefer a wrapper of a more established library can
> In addition to feeling less novel, QuickChecking JS
> APIs doesn't feel quite as useful for Servo testing (based on the
> assumption that Servo will be re-using *Monkey).
Most of the JS APIs are part of the DOM and not the built in objects.
These are implemented in the browser itself, not in
> My preference is to remove the azure code from git - it seems unlikely we'll
> be working on printing any time soon, and we will always have the history in
> git.
This is my preference as well. I think when we want to work on
printing, there may be better ways than what we have now anyway. I
> So, got any good research papers on networking?
My undestanding is that I/O is the bottleneck for networking, not the
CPU. So research here tends to focus on elimination of network
requests, optimizations to solve overhead (pipelining, keepalive),
more efficient protocols, or better data
Do you both object just as much if ./mach puts the tests in tree via
another mechanism than git clone of servo/servo? If we combined this
with having our _mozilla tests in servo/servo until they are
upstreamed, this would make contributing new tests just as easy as it
is now and fix the repo
> Your proposal scares me in the sense that (if I read it well) it would
> be at least temporarily allowing changing the style system without
> gating on Servo. There are architectural changes to the style system
> that work for Gecko, but would completely break Servo.
This would obviously be a
1 - 100 of 117 matches
Mail list logo