On Wed, Sep 24, 2014 at 10:38 AM, Nils Dagsson Moskopp <
n...@dieweltistgarnichtso.net> wrote:
> Jonas Sicking writes:
>
> > In some cases websites uses the UA strings for bad reasons ("this is
> > how we've always done it"), in other cases because it's literally the
> > best way for them to crea
On Mon, Jul 14, 2014 at 5:44 PM, Anne van Kesteren wrote:
> On Mon, Jul 14, 2014 at 3:47 PM, Konstantin Welke
> wrote:
> > How we use it:
> > * We try to launch our native application using a custom URI scheme
> > * If successful, we show some “success” UI
> > * If no handler installed, the user
On Mon, Jun 16, 2014 at 3:00 PM, Anne van Kesteren wrote:
> On Mon, Jun 16, 2014 at 12:57 PM, Jussi Kalliokoski
> wrote:
> > Another bad example of using strings for these kind of things, from much
> > closer, is XHR's responseType where it's excruciatingly pain
Reading the Fetch spec, the only major issue I have with the API is the
`to()` method on the FetchBodyStream. Having different kinds of behavior
behind one function that takes a string that determines the actual
underlying implementation is bad enough as it is (think about canvas's
`getContext()` f
On Nov 13, 2013 6:41 PM, "Dirk Schulze" wrote:
>
> On Nov 13, 2013, at 2:53 PM, Rik Cabanier wrote:
>
> > [resending because of a bounced message]
> >
> > DrawingPath is saying the same thing twice.
> > Maybe DOMDrawing is better? (with "drawing" the definition of
> > http://dictionary.cambridge.
On Thu, Jul 25, 2013 at 3:39 AM, Ryosuke Niwa wrote:
>
> getElementById is okay but we want to discourage authors from using
> methods like getElementsByTagName and getElementsByClassName that return
> live NodeList objects. They incur a lot of implementation cost in WebKit
> and hurts the DOM per
> (I've used querySelector exclusively for quite some time, and I find
> arguments that querySelector isn't readable or "the wrong tool" to simply
> not hold up. I find it more readable, actually, since I don't have to
> change interfaces depending on whether I'm searching for an ID or a class.)
>
On Sat, Jun 29, 2013 at 5:01 AM, Boris Zbarsky wrote:
> This is actually false. For example, getElementById("foo:bar") is just
> querySelector("#foo\\:bar"), which is ... nonobvious.
>
> It gets worse if you don't control the id that's passed in, because
> getElementById(arg) becomes querySelect
On Sat, Dec 22, 2012 at 8:04 PM, Ian Hickson wrote:
> On Sat, 22 Dec 2012, Anne van Kesteren wrote:
> >
> > Is there not some way we can have a lineDash attribute that returns a
> > manipulatable object that inherits from Array rather than the current
> > Java-like API? I remember this was discus
There is something like this cooking in the form of
responseType = "chunked-text"
and
responseType = "chunked-arraybuffer"
For reference, see [1] and [2]. Would be cool to hear a status update on
specifying these. Anyway, apparently the right forum of discussion for this
is the webapps mailing li
On Sat, Oct 27, 2012 at 3:14 AM, Ian Hickson wrote:
> On Thu, 9 Aug 2012, Jussi Kalliokoski wrote:
> >
> > On W3C AudioWG we're currently discussing the possibility of having web
> > workers that run in a priority/RT thread. This would be highly useful
> >
Please see the DSP API [1]. It's currently developed unofficially under the
W3C Audio WG [2], so if you have input, please post it to the audiowg
public mailing list. This should scratch your itch and more. ;)
Cheers,
Jussi
[1] http://people.opera.com/mage/dspapi/
[2] http://www.w3.org/2011/audio
Tue, Sep 4, 2012 at 11:03 PM, Boris Zbarsky wrote:
> On 9/4/12 3:31 PM, Jussi Kalliokoski wrote:
>
>> Hmm... Is it visible to the page outside getContext() ?
>>
>
> No. Why does that matter?
>
> -Boris
>
Hmm... Is it visible to the page outside getContext() ?
On Tue, Sep 4, 2012 at 10:21 PM, Boris Zbarsky wrote:
> On 9/4/12 3:17 PM, Jussi Kalliokoski wrote:
>
>> When all references to the context are lost (garbage collected)
>>
>
> That never happens while the canvas i
This might be a silly idea, but what about this:
When all references to the context are lost (garbage collected), simply
store the image on the canvas and make it behave like it was just an image.
This would lose all the state of the context, but since the problem seems
to be mostly with things li
On Thu, Aug 30, 2012 at 11:43 AM, Jussi Kalliokoski <
jussi.kallioko...@gmail.com> wrote:
> It's pretty simple to make a naive placeholder for contenteditable
> elements with CSS:
>
> [contenteditable]:not(:focus):empty::after {
> content: attr(data-placehold
It's pretty simple to make a naive placeholder for contenteditable elements
with CSS:
[contenteditable]:not(:focus):empty::after {
content: attr(data-placeholder);
color: #ccc;
}
I call it a bit naive because it turns out that if you have insert a line
break in the box, there will
bApps WG)
>
> In Gecko there is support for moz-chunked-arraybuffer
> response type.
>
>
>
>
> On 08/24/2012 03:23 AM, Jussi Kalliokoski wrote:
>
>> Hello,
>>
>> I've got a little proposal to solve a problem we're facing with one of our
>> c
s/questions inline.
>
> Le 8/24/2012 12:23 PM, Jussi Kalliokoski a écrit :
>
> Hello,
>>
>> I've got a little proposal to solve a problem we're facing with one of our
>> codebases ( aurora.js [1], i.e. audio codecs in JavaScript ).
>>
>> We need to
Good idea! I'm not attached to the semantics, only to the functionality.
Cheers,
Jussi
On Fri, Aug 24, 2012 at 3:46 PM, Simon Pieters wrote:
> On Fri, 24 Aug 2012 14:19:43 +0200, Jussi Kalliokoski <
> jussi.kallioko...@gmail.com> wrote:
>
> On Fri, Aug 24, 2012 a
On Fri, Aug 24, 2012 at 3:04 PM, Nils Dagsson Moskopp <
n...@dieweltistgarnichtso.net> wrote:
> Jussi Kalliokoski schrieb am Fri, 24 Aug
> 2012 13:23:03 +0300:
>
> >[…]
> >
> > My first idea was that if you set a property called "chunkSize" on
>
Hello,
I've got a little proposal to solve a problem we're facing with one of our
codebases ( aurora.js [1], i.e. audio codecs in JavaScript ).
We need to stream the audio files (you don't want to store a 2 hour long
live stream in the memory or wait until a whole file is loaded before
playing).
On Sun, Aug 12, 2012 at 6:48 AM, Jonas Sicking wrote:
> On Sat, Aug 11, 2012 at 3:22 PM, Jussi Kalliokoski
> wrote:
> > On Fri, Aug 10, 2012 at 11:07 PM, Glenn Maynard wrote:
> >
> >> On Thu, Aug 9, 2012 at 1:20 AM, Jussi Kalliokoski <
> >> jussi.kallioko
On Fri, Aug 10, 2012 at 11:07 PM, Glenn Maynard wrote:
> On Thu, Aug 9, 2012 at 1:20 AM, Jussi Kalliokoski <
> jussi.kallioko...@gmail.com> wrote:
>
>> On W3C AudioWG we're currently discussing the possibility of having web
>> workers that run in a priority/RT thr
On Thu, Aug 9, 2012 at 6:09 PM, David Bruant wrote:
> Le 09/08/2012 09:59, Jussi Kalliokoski a écrit :
>
> Hello David,
>
> Hi Jussi,
>
> On Thu, Aug 9, 2012 at 3:54 PM, David Bruant wrote:
>
> * The last source is your own content competing with itself for CP
Hello David,
On Thu, Aug 9, 2012 at 3:54 PM, David Bruant wrote:
> Le 09/08/2012 02:20, Jussi Kalliokoski a écrit :
>
> Hello there!
>>
>> On W3C AudioWG we're currently discussing the possibility of having web
>> workers that run in a priority/RT thread.
Hello there!
On W3C AudioWG we're currently discussing the possibility of having web
workers that run in a priority/RT thread. This would be highly useful for
example to keep audio from glitching even under high CPU stress.
Thoughts? Is there a big blocker for this that I'm not thinking about or
27 matches
Mail list logo
