On Oct 5, 2014, at 7:49 PM, Boris Zbarsky wrote:
> On 10/5/14, 7:51 PM, Cameron Zwarich wrote:
>> Are there any plans to eliminate the copies in Gecko?
>
> No. Measurement showed that in practice the cost of copying short strings,
> which most of these are, is very low. For large strings you
Hi all
I tried running the wpt tests (./mach test-wpt) and got the following error:
http://pastebin.com/f8kH8rah
I am running the latest dev version of servo (at the time of writing) and
all submodules are updated as well (by virtue of running ./mach build).
I'm running ubuntu 14.04.
Let me
On 10/6/14, 3:53 AM, Cameron Zwarich wrote:
Where do most of the small strings larger than a single character that benefit
from the inline small string optimization originate, the DOM or user JS code?
That's a good question.
When the optimization was added, strings that originated in the DOM
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 depend on
On Oct 6, 2014, at 9:00 AM, Simon Sapin wrote:
>> For me, absent evidence, it's much easier to believe that using WTF-8
>> instead of potentially ill-formed UTF-16 would be a win for the JS
>> engine than to believe that using WTF-8 instead of UTF-8 in the DOM
>> would be a win.
>
> So you’re su
https://github.com/servo/servo/wiki/Meeting-2014-10-06
Cheers,
Josh
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 06/10/14 11:14, Prasoon Shukla wrote:
> Hi all
>
> I tried running the wpt tests (./mach test-wpt) and got the following error:
>
> http://pastebin.com/f8kH8rah
This was a regression in the test runner that somehow went unnoticed.
Sorry about that. It should work now (you might want to delete
On 10/6/14, 10:27 AM, Cameron Zwarich wrote:
This is an increase in memory usage over all existing engines
Is it an increase over Gecko?
Are we trying to optimize for performance or memory usage here, or both
at once?
-Boris
___
dev-servo mailing
On Oct 6, 2014, at 2:49 PM, Boris Zbarsky wrote:
> On 10/6/14, 10:27 AM, Cameron Zwarich wrote:
>> This is an increase in memory usage over all existing engines
>
> Is it an increase over Gecko?
If Servo used UTF-8 strings in the DOM, then it wouldn’t be able to use
JS_NewExternalString in the
On 10/6/14, 3:32 PM, Cameron Zwarich wrote:
then it wouldn’t be able to use JS_NewExternalString in the places where Gecko
is able to use it.
Ah, true.
Is there any particular place where you feel there is tension between the goals
of memory usage and performance?
I don't know yet. I mea
This is just an informational message to inform everyone of the design
of current scrolling model. I hope this will also be useful to shine the
way toward overflow:scroll. I'm also interested in hearing about
potential improvements to this model, because it would be best to
implement them now, befo
On 10/6/14 5:17 PM, Martin Robinson wrote:
There isn't a lot in the way to extend this model to
overflow:scroll. The layout code would simply need to make a layer for
the content inside the scrolling flow and a layer for the scrolling
root. The two main dependencies for this would be:
a. Adding
Could you clarify how CSS animations and transitions are related here?
Cheers,
Josh
On 2014-10-06 8:31 PM, Patrick Walton wrote:
On 10/6/14 5:17 PM, Martin Robinson wrote:
There isn't a lot in the way to extend this model to
overflow:scroll. The layout code would simply need to make a layer fo
On 10/6/14, 5:17 PM, Martin Robinson wrote:
This is just an informational message to inform everyone of the design
of current scrolling model. I hope this will also be useful to shine the
way toward overflow:scroll. I'm also interested in hearing about
potential improvements to this model, becaus
On 10/6/14, 7:44 PM, Boris Zbarsky wrote:
Just to check, what's the plan for doing "overflow: sticky"?
I mean "position: sticky", of course. ;)
-Boris
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-serv
On 10/6/14 7:14 PM, Josh Matthews wrote:
Could you clarify how CSS animations and transitions are related here?
Sure. For optimum performance, browsers with accelerated and
off-main-thread compositing have traditionally run a subset of CSS
animations/transitions (those that require no complex
On 10/6/14 7:44 PM, Boris Zbarsky wrote:
Just to check, what's the plan for doing "overflow: sticky"? And does
this model handle position:fixed things that end up both above and below
pieces of a single position:static thing?
I'd have to page `position:sticky` information back into my brain, b
On Oct 6, 2014, at 3:49 PM, Boris Zbarsky wrote:
>> Is there any particular place where you feel there is tension between the
>> goals of memory usage and performance?
>
> I don't know yet. I mean, for charAt, sure. ;)
JS engines have been using ropes for quite some time now, which means tha
18 matches
Mail list logo
