Re: [whatwg] High-density canvases

2013-09-11 Thread Robert O'Callahan
On Tue, Sep 10, 2013 at 10:46 PM, Tab Atkins Jr. jackalm...@gmail.comwrote: High-end laptops have high-dpi screens (the Pixel I'm using right now has one), and they're slowly spreading down the price scale. On Mac there are Retinas of course, and on Windows Firefox defaults to a non-1.0

Re: [whatwg] High-density canvases

2013-09-11 Thread Robert O'Callahan
On Tue, Sep 10, 2013 at 1:26 PM, Rik Cabanier caban...@gmail.com wrote: There's a thread on www-style: http://lists.w3.org/Archives/Public/www-style/2012Nov/0144.html It's been in firefox for a while and blink is going to ship it soon:

Re: [whatwg] Should video controls generate click events?

2013-09-11 Thread Simon Pieters
On Wed, 11 Sep 2013 01:35:00 +0200, Ian Hickson i...@hixie.ch wrote: On Tue, 20 Aug 2013, Rick Waldron wrote: Also, at the time, the surface click to play was non-standard and incredibly annoying because it just showed up as someone's pet feature in Firefox. (I'm still not sure if it's a

Re: [whatwg] Should video controls generate click events?

2013-09-11 Thread Philip Jägenstedt
On Wed, Sep 11, 2013 at 10:48 AM, Simon Pieters sim...@opera.com wrote: On Wed, 11 Sep 2013 01:35:00 +0200, Ian Hickson i...@hixie.ch wrote: On Wed, 21 Aug 2013, Robert O'Callahan wrote: I think you basically have to assume that if you specify controls then the controls may accept clicks

Re: [whatwg] High-density canvases

2013-09-11 Thread Tab Atkins Jr.
On Wed, Sep 11, 2013 at 1:20 AM, Robert O'Callahan rob...@ocallahan.org wrote: Actually what I really think we should do is also change the window.devicePixelRatio for pinch zoom. Combined with the suggestions for canvas, that would allow (as Rik pointed out on IRC) for high-quality

Re: [whatwg] Should video controls generate click events?

2013-09-11 Thread Philip Jägenstedt
On Wed, Sep 11, 2013 at 11:18 AM, Simon Pieters sim...@opera.com wrote: On Wed, 11 Sep 2013 10:51:44 +0200, Philip Jägenstedt phil...@opera.com wrote: That might be good so that the behavior is consistent between browsers. However, I think it should be conditional on whether the controls are

Re: [whatwg] URL resolution of fragment urls in html5 webapps

2013-09-11 Thread Anne van Kesteren
On Tue, Sep 10, 2013 at 8:34 PM, Ian Hickson i...@hixie.ch wrote: On Wed, 10 Jul 2013, Rafael Weinstein wrote: I'm curious: Is it useful to have fragment URL resolve against anything other than the display url? I.e. when is the current behavior wrt fragments appropriate. It's a good

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

2013-09-11 Thread Anne van Kesteren
On Tue, Sep 10, 2013 at 8:54 PM, Ian Hickson i...@hixie.ch wrote: On Fri, 12 Jul 2013, Anne van Kesteren wrote: But then we shouldn't garble pathname either and we do because we have to. So I'm not sure that line of reasoning makes sense. I do think we should offer some kind of conversion

Re: [whatwg] Question about document.referrer (and document.URL, document.location.href) when IDN domains are in use

2013-09-11 Thread Ian Hickson
On Wed, 11 Sep 2013, Anne van Kesteren wrote: On Tue, Sep 10, 2013 at 8:54 PM, Ian Hickson i...@hixie.ch wrote: On Fri, 12 Jul 2013, Anne van Kesteren wrote: But then we shouldn't garble pathname either and we do because we have to. So I'm not sure that line of reasoning makes sense. I do

Re: [whatwg] URL resolution of fragment urls in html5 webapps

2013-09-11 Thread Ian Hickson
On Wed, 11 Sep 2013, Anne van Kesteren wrote: On Tue, Sep 10, 2013 at 8:34 PM, Ian Hickson i...@hixie.ch wrote: On Wed, 10 Jul 2013, Rafael Weinstein wrote: I'm curious: Is it useful to have fragment URL resolve against anything other than the display url? I.e. when is the current

Re: [whatwg] High-density canvases

2013-09-11 Thread Ian Hickson
On Wed, 11 Sep 2013, Robert O'Callahan wrote: Pinch-zoom is hard because we don't want to trigger reflows or other expensive behavior on pinch-zoom. I'd leave pinch-zoom out of it for now. Unless I'm missing something fundamental, changing the pixel density doesn't cause a layout, it's

Re: [whatwg] High-density canvases

2013-09-11 Thread Rik Cabanier
On Wed, Sep 11, 2013 at 11:24 AM, Ian Hickson i...@hixie.ch wrote: On Wed, 11 Sep 2013, Robert O'Callahan wrote: Pinch-zoom is hard because we don't want to trigger reflows or other expensive behavior on pinch-zoom. I'd leave pinch-zoom out of it for now. Unless I'm missing something

Re: [whatwg] High-density canvases

2013-09-11 Thread Ian Hickson
On Wed, 11 Sep 2013, Rik Cabanier wrote: On Wed, Sep 11, 2013 at 11:24 AM, Ian Hickson i...@hixie.ch wrote: On Wed, 11 Sep 2013, Robert O'Callahan wrote: Pinch-zoom is hard because we don't want to trigger reflows or other expensive behavior on pinch-zoom. I'd leave pinch-zoom out of

Re: [whatwg] Sortable Tables

2013-09-11 Thread Ian Hickson
On Fri, 19 Jul 2013, Stuart Langridge wrote: On Thu, Jul 18, 2013 at 11:48 PM, Ian Hickson i...@hixie.ch wrote: but time is more of a problem if you have multiple things in one cell. For example, one semi-common pattern is to put some data and an input type=checkbox in a single

Re: [whatwg] img loading events - can load error fire for the same image?

2013-09-11 Thread Ian Hickson
On Mon, 22 Jul 2013, Jake Archibald wrote: Take http://jsbin.com/ifihex/1/edit - the image on this page receives a valid full HTTP request, but the received data isn't valid image data (it's html). Starting from

Re: [whatwg] Outline style to use for drawSystemFocusRing

2013-09-11 Thread Ian Hickson
On Tue, 10 Sep 2013, Dominic Mazzoni wrote: We've finished implementing drawSystemFocusRing and drawCustomFocusRing in Chrome. Try it in Chrome 31 or higher (either canary or dev channel should work today). You'll need to go to chrome://flags and enable *experimental canvas features*, then

Re: [whatwg] remove resetClip from the Canvas 2D spec

2013-09-11 Thread Ian Hickson
On Fri, 9 Aug 2013, Simon Sarris wrote: As an alternative [to resetClip()] I would propose something like setClip() or setClip(path) (with the former working on the current path, just like clip()/fill()/stroke() does). Seems like this would have the same problems as resetClip(), since it's

Re: [whatwg] [[GetOwnProperty]] for named properties of the Window object

2013-09-11 Thread Boris Zbarsky
On 9/11/13 6:05 PM, Gavin Barraclough wrote: Interesting, I had just assumed this was okay – is it not spec-compliant for Window.prototype to be a named properties object? No, it's not. The spec defines exactly what the prototype chain looks like here. See the definitions of [[Prototype]]