learning rust along the way, so any feedback is welcome.
Have fun,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
t-dev/2012-December/002679.html
Indeed, I probably copied this pattern from another library. Good to know.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
for servo?
Regards,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
d level of parallelism?
Regards,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
you
should prepend ? On Windows there’s also a lot of fun with UNC paths,
but I didn’t bother.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
interning for
property/element/attribute names and other keywords to avoid many linear
string comparisons. There is a set of known names, but we still want to
support eg. unknown HTML element in Selectors. How does or should that work?
Cheers,
--
Simon Sapin
shouldn’t
be a problem to add later.
Perhaps more tricky is dynamic changes (in stylesheets, in DOM tree,
etc.) Should we consider as soon as now how to make them fast in
selector matching?
Would it help to have a video / whiteboard discussion of all this?
Cheers,
--
Simon Sapin
question is: are these feature intrinsically too expensive to
be used in stylesheets evaluated dynamically? Or could we find some
clever optimization that makes performance acceptable? Does Servo’s
parallelism help compared to mostly single-threaded browsers?
--
Simon Sapin
___
e (non-functional) pseudo-classes. Same as ID
selectors, repeating the same pseudo-class does not change the selector.
(eg. :empty:empty is the same as :empty. This is true for all
pseudo-classes defined in Selectors 4 AFAIK.)
--
Simon Sapin
___
dev-servo
hey on the
Roadmap ? https://github.com/mozilla/servo/wiki/Roadmap or somewhere else ?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Le 29/07/2013 20:06, Boris Zbarsky a écrit :
On 7/29/13 11:38 AM, Simon Sapin wrote:
type Namespace = i32 // Is this some kind of interning as well?
In Gecko, yes.
* Use vectors / arrays instead of linked lists for AtomList,
PseudoClassList and SelectorList. (Less allocations) This
able to meet at 9am every other Monday?
I'd be happy to hear questions, comments, or alternative suggestions.
It appears to not be possible to accommodate everyone each week, and
this seems the best compromise.
Being in London I would only attend half of the meetings, but otherwise
it work
ained at http://publicsuffix.org/
Cheers,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
to
rewrite the layout code to use logical keywords (eg. measure/extent
instead of width/height) while we don’t have much layout code.
http://dev.w3.org/csswg/css-writing-modes/
http://dev.w3.org/csswg/css-writing-modes/#abstract-box
--
Simon Sapin
just use "Servo" for now, and revisit this when we actually
worry about being compatible with the long tail of websites.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
W3C and Gecko.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
on github any regression
you find. I’m already aware that selector parsing is broken, I’ll look
into this next.
Cheers,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
between CSS px and device
pixels, exactly like zooming. Shouldn’t it just be different default zoom?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Le 29/10/2013 17:22, Patrick Walton a écrit :
On 10/29/13 8:52 AM, Simon Sapin wrote:
Le 29/10/2013 15:06, Josh Matthews a écrit :
https://github.com/mozilla/servo/wiki/Meeting-2013-10-28
Retina display
P: In the short term, we should change the Au that CSS reports.
I disagree. Au as I
data types.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
o.com/support/software-downloads/
This is what I use.
We also have an (audio-only) phone bridge.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
-> [Token]) followed by "block and
function grouping" ([Token] -> [ComponentValue]) in order to get
equivalent functionality to rust-cssparser, do you still get speedups
compared to current rust-cssparser? (Which does str -> [Comp
ing and
drawing. Can this be more specific?
* Compositing
Thoughts?
These are perhaps not "phases" but while we’re into naming, additional
components are:
* Content: Documents, elements, attributes, etc. The HTML parser
produces a content tree.
* DOM: The set of APIs exposin
On 04/02/2014 17:15, Daniel Hackney wrote:
Simon Sapin wrote:
If you have speculative lexing (str -> [Token]) followed by "block and
function grouping" ([Token] -> [ComponentValue]) in order to get equivalent
functionality to rust-cssparser, do you still get speedups compared
review is probably to make a pull request. We have
tools that make tracking the review much easier then.
(Also, if you use IRC at all, you should join #servo on irc.mozilla.org :))
Cheers,
--
Simon Sapin
___
dev-servo mailing list
dev-servo
today, which helps us answer the
big questions that Servo set out to answer.
Yes, Web compat is important. But Acid3 in particular is a poor proxy
for Web compat, IMO.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
foo to IFoo and BFoo, respectively.
3. "top"/bottom"/"left"/"right"/"width"/"height" (today);
4. Same as (3), but with "logical" added.
And for "line-relative directions":
1. "over"/"under"/"
On 28/02/2014 10:37, Simon Sapin wrote:
In general I prefer using spec terminology, but in this specific case I
don’t really like either extent/measure (too foreign, not obvious which
is which) not logical-width/logical-height (too "physical-like").
Actually I think this is worth ch
st be confident that the
cast will succeed or task failure will occur.
Would it make sense to have downcasting return an option? That way you
can either match to have different behavior in either case, or use
.unwrap() when you expect success.
--
Simon
On 28/02/2014 19:07, Simon Sapin wrote:
On 28/02/2014 10:37, Simon Sapin wrote:
In general I prefer using spec terminology, but in this specific case I
don’t really like either extent/measure (too foreign, not obvious which
is which) not logical-width/logical-height (too "physical
data:text/html,document.write("a\uD800b")
Unfortunately I’d be less surprised if someone relies on having the two
halves of a surrogate pair in separate document.write() call, as this
seems more interoperable:
data:text/html,document.write("\uD83D");document.write("\uDCA9")
--
On 29/03/2014 23:15, Boris Zbarsky wrote:
On 3/29/14 6:56 PM, Simon Sapin wrote:
Or I guess we could use what I’ll call "evil UTF-8", which is UTF-8
without the artificial restriction of not encoding surrogates.
http://en.wikipedia.org/wiki/CESU-8
CESU-8 is evil too, but it’s not
On 29/03/2014 22:56, Simon Sapin wrote:
On 10/03/2014 23:54, Keegan McAllister wrote:
Speaking of which, [5]
Any character that is a not a Unicode character, i.e. any isolated
surrogate, is a parse error. (These can only find their way into
the input stream via script APIs such as
s to parse from a string in any case.)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
the spec that way, a few years ago:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11298#c2
Henri, any comment?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
s/35
I have done a simple microbenchmark and found that using SSE4/AVX to
compute two sides at once is 66% faster than doing it sequentially using
branches. This is true even if percentages are not used and all branches
are predicted correctly.
Thoughts?
--
Simon Sapin
n-css/
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
eading does not require `&mut`. Or
perhaps we should have all three.
Is there a better way to do accessors in Rust?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 26/05/2014 22:52, Patrick Walton wrote:
On 5/26/14 2:44 PM, Simon Sapin wrote:
Unlike C++, Rust does not have method overloading so the accessors are
much more verbose.
`nscoord ISize(WritingMode aWritingMode) const` overloaded with
`nscoord& ISize(WritingMode aWritingMode)` bec
On 27/05/2014 18:14, Patrick Walton wrote:
On 5/26/14 3:11 PM, Simon Sapin wrote:
I’m fine with that, but I’m more interested in the signature than the
naming. That is, which of these (or others) to have, for each private
field?
fn(&self) -> T
fn(&mut self, T)
fn(&'a mu
hysical
So Gecko and the spec seem to have a different ideas of what
flow-relative means. Is there a reason for this?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
he guiding principle to decide how many structs to have, and
which properties go where? Why not have every longhand property in its
own "struct", sharable separately? Is there something you’d like to
change in Gecko’s distribution, but don’t because making the change
would be too painf
By the way, I use the attached script to list Gecko’s CSS properties by
style struct.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
w, but suggestions are welcome.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
go in Servo would mean two builds of rustc. At
the moment, Cargo is in a separate repository. When and if it moves
inside the rustc repository, we’ll get it as part of the snapshot.
(The lack of cross-compiling support is still problematic, of course.)
--
Simon
tself.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 07/07/14 17:12, Steve Klabnik wrote:
... and like magic, they have just appeared!
https://github.com/rust-lang/cargo#installing-cargo
What a coincidence! Thanks Steve :)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
Hi all,
Can someone help this person with Servo on Android? Please keep them in
CC as they’re probably not subscribed to the list.
Thanks,
--
Simon Sapin
On 10/07/14 14:39, Cristian Silaghi wrote:
Can you share with me one recent build of Servo for Android? I want to
test it on my phone
r example in rust-url:
git remote set-url origin g...@github.com:servo/rust-url.git
Cheers,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Critic.
To update your git remotes and avoid the redirect, run on of:
git remote set-url upstream https://github.com/servo/servo.git
git remote set-url upstream g...@github.com:servo/servo.git
for read-only or read/write access, respectively.
--
Simon Sapin
manage who has push or admin
access to the servo repository, in the same place as for the various
repositories for servo submodules.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
reader. Input welcome on potential improvements.”
I suppose event dispatching is relevant too.
Anyone wants to take a look? Feedback on the spec should filed in its
bug tracker (see the “file a bug” link at the top), or annevk can be
found on IRC #whatwg @ Freenode.
--
Simon Sapin
Please review carefully, and decide if we should push for the spec to
change in some way.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
hing to
put there more interesting that what’s already in the README.
(http://www.servo.org/ redirects to http://servo.org/)
By the way, the way to request changes to the DNS configuration is to
file a bug in bugzilla, in the "mozilla.org" product and "
code that generates the sidebar:
https://github.com/rust-lang/rust/blob/8a02304a44/src/librustdoc/html/static/main.js#L682-L698
I suppose we could patch it so that it generates subsections, or something.
--
Simon Sapin
___
dev-servo mailing list
/rust-lang/rust/issues/16328
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
es care of passing all the
necessary command line arguments to find dependencies (which we
currently do ourselves in the Makefile.)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
:
There are at least two cases of this, both currently annotated with FIXME:
https://github.com/servo/servo/search?utf8=%E2%9C%93&q=TraitObject
I submitted https://github.com/servo/servo/pull/3170 to fix these four,
but haven’t looked for other places where we might have the same issue.
--
S
On 15/09/14 05:13, Matt Brubeck wrote:
Today's Cargo nightly contains some recent fixes [...]
Which version is that? I just updated to 3f6af3d 2014-09-13, which may
or may not be today’s because of
https://github.com/rust-lang/rust/issues/16649
--
Simon
something out for .charAt() and friends), SpiderMonkey could support
WTF-8 internally for JS strings and Servo’s bindings could remove the
conversion.
What do you think?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
On 06/10/14 07:57, Henri Sivonen wrote:
On Sun, Oct 5, 2014 at 7:26 PM, Simon Sapin wrote:
JavaScript strings, however, can. (They are effectively potentially
ill-formed UTF-16.) It’s possible (?) that the Web depends on these
surrogates being preserved.
It's clear that JS programs depe
se.
XML5 is entirely based on the assumption that we can give any meaning we
want to input sequences that used to fail to parse.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
rch with the bar at the top, or
with an URL like http://doc.servo.org/servo/?search=foo
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
way through, with a couple of different available inline sizes.
[1] http://dev.w3.org/csswg/css-sizing/#block-intrinsic
This means using results (for a subtree) of our third traversal in the
first traversal. Can we do that without compromising parallel layout?
--
Simon Sapin
ck for older browsers that don’t support CSS transforms.
(Still, this is more of an exception than a common case.)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
mportantly, if you use execute './target/servo' directly, it will
be your previous build and will not be updated by 'mach build' anymore.
You should use './components/servo/target/servo' or 'mach run' instead.
You can also run 'mv tar
, likely some time in January) of this
page:
https://wiki.mozilla.org/Community:SummerOfCode14:Brainstorming
We can still start gathering ideas, of course.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org
cations and lots
of copying.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
w scroll event handlers).
* CSS Async Style
As far as I understand, this proposes adding control on what phases of
rendering of what parts of the document can be deferred or (de)prioritized.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lis
depends on bswap? In the Rust version that Servo
uses right now, that functionality is part of the standard library’s
std::old_io::Reader and std::old_io::Writer and the bswap library did
not exist yet.
--
Simon Sapin
___
dev-servo mailing list
dev-servo
platform-specific code
however, I don’t think Appveyor brings us anything.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
ll be "forced" to publish changes on
crates.io before Servo can use them.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
e’s area of interest?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Please delay landing any PR in servo/servo until
https://github.com/servo/servo/pull/6174 gets reviewed and merged.
If you want to discuss the idea, head over to
https://github.com/servo/servo/issues/6041 .
--
Simon Sapin
___
dev-servo mailing list
On 24/05/15 09:21, Simon Sapin wrote:
Please delay landing any PR in servo/servo until
https://github.com/servo/servo/pull/6174 gets reviewed and merged.
If you want to discuss the idea, head over to
https://github.com/servo/servo/issues/6041 .
It’s landed, the tree is open again. Thanks
ependency declaration at the same time isn’t too much
of a bother.)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
his is less and less the case: many libraries can be
updated without updating Rust, and a smaller number of libraries need to
be updated when we update Rust. In time, there’ll be no reason to do
both at the same time.
--
Simon Sapin
___
dev-servo m
at
all), so old Servo commits should still build.
We should still update to the new name, though, and use the crates.io
copy to force ourselves to keep it up-to-date. I’ve filed
https://github.com/servo/servo/issues/6406 about this.
--
Simon Sapin
serde
to notify of breaking changes in Rust Nightly and they are kept
up-to-date then the problem is solved, isn’t it?
Erickt has offered to give push access to some of us to help make this
happen. I don’t mind doing it if nobody else wants to.
--
Simon Sapin
single alphabetical-order group.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
as of code", to start, could be each crate in the
servo/servo repository and each other repository in the servo org on github.
Of course we may not be able to reach this ideal state yet, but we
should still go towards it.
--
Simon Sapin
___
dev-ser
On 01/09/15 10:15, Anthony Ramine wrote:
I can be the second person on h5e, if you want.
That’s great, thanks!
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
#structfield.user_stylesheets
to add "user origin" stylesheets to every document.
See https://drafts.csswg.org/css-cascade/#cascade-origin and
https://drafts.csswg.org/css-cascade/#cascading-origins
--
Simon Sapin
___
dev-servo mailing list
by 10am. Batching meetings would be ideal for me, but other
days work too.
Does the early meeting need to move at all? I thought what promted this
was conflicts with the late meeting time.
--
Simon Sapin
___
dev-servo mailing list
dev-servo
.gz>)
in the meantime.
If you also have a clone of the Servo repository, you can use its Rust
snapshot (which is downloaded automatically) by using e.g.
`../servo/mach cargo` instead of `cargo`.
--
Simon Sapin
___
dev-servo mailing lis
part of the WPT suite.
./mach build -r
./mach test-wpt -r
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
d and README.md.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 23/10/15 05:43, Pranesha Shashwath Kumar Kattepura Jayabheema Rao wrote:
Python virtualenv failed to execute properly.
Try removing the python/_virtualenv directory, it should be re-created
automatically next time you run ./mach build
--
Simon Sapin
http://doc.rust-lang.org/book/macros.html
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 12/11/15 01:22, Lars Bergstrom wrote:
the 1--2AM US Pacific slot that
appears to be both the "deadzone" for our reviewer coverage
That’s 10~11 am in my time zone. I’m generally awake at that time, feel
free to ping me on IRC if I can unblock something.
--
S
at do you think of making it advisory rather than a hard requirement?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 26/11/15 17:05, Simon Sapin wrote:
Currently, pull requests can not land until `./mach test-tidy` passes,
which includes checking that we’re not building more than one version of
any crate.
This usually makes sense: duplicate crates increase binary size and
sometimes cause build errors
nverge with some of these?
[1] https://github.com/servo/rust-smallvec
[2]
https://github.com/SimonSapin/rust-std-candidates/blob/master/string-wrapper/lib.rs
[3] https://github.com/SimonSapin/rust-utf8
--
Simon Sapin
___
dev-servo mailing lis
to be a distraction
if we don’t bikeshed it.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
?
http://www.ibiblio.org/harris/500milemail.html
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
same the other way around?
How long would it typically take between approving a GitHub PR and
having it land in GitHub master? (This matters when a conflicting PR
needs to be rebased.) Would it be blocked on mozilla-inbound being
merged into mozilla-central?
servo IRC channel:
https://wiki.mozilla.org/IRC
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Hi all,
I have a pull request for rust-url with large breaking changes:
https://github.com/servo/rust-url/pull/176
I’d appreciate feedback (preferably in github comments) on the API design.
Thanks!
--
Simon Sapin
___
dev-servo mailing list
dev
an fbdev. And i did not have the
exact nightly used by the build script, too.
Servo does do a lot of stuff of the GPU, but I don’t know the exact
requirements.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.o
do
this, though it may unexpectedly break in the future.
Why isn’t this supposed to work? Based on conversations with Alex, Cargo
by design builds a crate with the union of all requested features. There
is no need for all dependents to specify the same set of features and
this
1 - 100 of 159 matches
Mail list logo
