I concur with Boris's concerns. Can we at least avoid having OverrideBuiltins
on Document?
Or can we keep HTMLDocument that just defines name getter?
- R. Niwa
On Jul 12, 2013, at 11:04 AM, Boris Zbarsky wrote:
> On 7/12/13 1:57 PM, Ian Hickson wrote:
>> Having not heard any interest from an
On Jul 28, 2013, at 4:24 PM, Jonas Sicking wrote:
> On Sun, Jul 28, 2013 at 1:59 PM, Ojan Vafai wrote:
>>
>> I was just picturing lazy computing the list. You don't need to compute the
>> list until you query the length or index into the NodeList, at which point,
>> if it's a static NodeList, y
On Tue, Aug 13, 2013 at 11:57 AM, Ian Hickson wrote:
> On Mon, 12 Aug 2013, Kenneth Russell wrote:
>>
>> The use case is the passing of ImageData objects back and forth to
>> workers to fill and refill with data.
>>
>> An ImageData is essentially a wrapper for the underlying
>> Uint8ClampedArray,
Am 13.08.2013 um 23:10 schrieb Edward O'Connor :
> Hi Anselm,
>
> You wrote:
>
>> [A]s WebKit today implemented the srcset attribute [1] according to
>> the W3C specification [2] I do think it is time to update the WHATWG
>> specification [3] reflecting the syntax as written in W3C's spec.
>
>
On Sat, 10 Aug 2013, Jonas Sicking wrote:
> On Fri, Aug 9, 2013 at 7:47 PM, Ian Hickson wrote:
> >> >> 1) Content-Disposition: inline
> >> [snip]
> >> > This seems unambiguous. Where's the problem?
> >> >
> >> >> 2) Content-Disposition: inline; filename="B.txt"
> >> [snip]
> >> > Again, this seems
Hi Anselm,
You wrote:
> [A]s WebKit today implemented the srcset attribute [1] according to
> the W3C specification [2] I do think it is time to update the WHATWG
> specification [3] reflecting the syntax as written in W3C's spec.
I think you might have this backwards. All normative content of t
On Jul 28, 2013, at 10:29 AM, James Greene wrote:
> I think it makes sense, too. That said, if the goal is to REPLACE the
> NodeIterator and TreeWalker APIs completely, it wouldn't be all that
> valuable for me as my most common use case has always been to get TEXT
> NODES from under a root node
On 2013-08-13 19:56 (GMT) Ian Hickson composed:
...Firefox...
...Firefox...
...Firefox ... Firefox...
Please type Gecko unless you mean to exclude SeaMonkey, Camino and other
browsers built on Gecko. It's only five letters, thus quicker to type than
Firefox's seven, and should help to furthe
Dear WHATWG members and editor(s),
as WebKit today implemented the srcset attribute [1] according to the W3C
specification [2]
I do think it is time to update the WHATWG specification [3] reflecting the
syntax as written in W3C's spec.
Currently both specifications differ due to the different
On Thu, 8 Aug 2013, Boris Zbarsky wrote:
> On 8/8/13 5:05 PM, Ian Hickson wrote:
> > I think the problem is that I have no idea what these ES6 terms are or
> > what they mean.
>
> OK. Which terms, exactly?
Probably all the JS terms that were introduced since the late 90s...
(Thanks for the edu
On Aug 12, 2013, at 11:28 PM, Yoichi Osato wrote:
> I have questions about some inputmode attributes.
> In the desktop case, full-width-latin, kana and katakana look to intend
> user local IME. Right?
> I think whether IME is on or off is very important to user because some IME
> have state and
On Tue, 13 Aug 2013, Daniel Trebbien wrote:
>
> Reading through the spec, I am not seeing how an application can
> determine whether a drop into a different window was successful.
This was an error in the spec. Good catch.
I've updated the spec. The trick is to check event.dataTransfer.dropEffec
On Mon, 12 Aug 2013, Kenneth Russell wrote:
>
> The use case is the passing of ImageData objects back and forth to
> workers to fill and refill with data.
>
> An ImageData is essentially a wrapper for the underlying
> Uint8ClampedArray, providing an associated width and height. However,
> the
On Mon, Aug 12, 2013 at 4:50 PM, Glenn Maynard wrote:
> On Mon, Aug 12, 2013 at 12:16 PM, Joshua Bell wrote:
>
>> To recap history: early iterations of the Encoding API proposal did have
>> base64 but it was removed with the suggestion to extend atob()/btoa()
>> instead, and due to the confusion
Reading through the spec, I am not seeing how an application can determine
whether a drop into a different window was successful.
Example use case: An app wants to take advantage of multiple screens, and so
it opens two different windows which can be placed on different screens. The
user can
On Sat, Aug 10, 2013 at 11:07 PM, Rik Cabanier wrote:
>
>
> On Sat, Aug 10, 2013 at 7:50 AM, Glenn Maynard wrote:
>
>> On Sat, Aug 10, 2013 at 7:42 AM, Stephen White
>> wrote:
>>
>>> Chrome (well, Skia actually) uses a "hairline" mode for line widths < 1.
>>> It draws a line of width 1, and use
> If this is strictly a performance issue, then we definitely should fix
that before adding new API, IMHO. It would be great to get some reduced
test cases where save()/restore() is a bottleneck.
I'd argue its not strictly a performance issue. More generally its awkward
that you can reset any piec
17 matches
Mail list logo
