On Tue, Oct 7, 2014 at 3:57 PM, Henri Sivonen wrote:
> > UTF-8 strings will mean that we will have to copy all non-7-bit ASCII
> strings between the DOM and JS.
>
> Not if JS stores strings as WTF-8. I think it would be tragic not to
> bother to try to make the JS engine use WTF-8 when having the
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 wrote:
> In the build queue there are 5 approved but t
On Tue, Oct 7, 2014 at 6:57 AM, Henri Sivonen wrote:
> On Mon, Oct 6, 2014 at 8:27 PM, Cameron Zwarich
> wrote:
> >> So you’re suggesting Servo could get away with UTF-8 in the DOM? I
> hadn’t considered it. I remove my proposal at the start of this thread, I’d
> like us to try this instead.
> >
On Mon, Oct 6, 2014 at 7:49 PM, Patrick Walton wrote:
> 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?
>>
On 10/8/14 10:51 PM, Robert O'Callahan wrote:
You can get away with that for position:fixed, but I don't think you can
get away with that for overflow:auto/scroll. We find in Gecko many real
situations where scrolled content for a given scrollable container has
to be split into multiple layers be
On Oct 8, 2014, at 10:48 PM, Robert O'Callahan wrote:
> On Tue, Oct 7, 2014 at 6:57 AM, Henri Sivonen wrote:
>
>> On Mon, Oct 6, 2014 at 8:27 PM, Cameron Zwarich
>> wrote:
So you’re suggesting Servo could get away with UTF-8 in the DOM? I
>> hadn’t considered it. I remove my proposal at t
6 matches
Mail list logo
