For posterity, here were our objections to the original high-DPI canvas
spec:
- The API feels like a short-term hack to automagically do something
that the developer may or may not want done (e.g., if the game/app was
tuned for particular resolution, or for pixel-exact rendering) that
On 9/10/13 2:55 PM, Dean Jackson wrote:
Ouch. Who is doing this and why?
Any browser in which zoom changes the size of a CSS pixel, and because
that's the definition of devicePixelRatio?
-Boris
On Tue, 10 Sep 2013, Ian Hickson wrote:
In cases when the hostname is non-ASCII, the Referer header will
have it encoded in punycode.
Is that defined anywhere?
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.36 which
defines it syntactically as a URI,
On 11 Sep 2013, at 5:32 am, Ian Hickson i...@hixie.ch wrote:
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 12:14 am, Stephen White senorbla...@chromium.org
wrote:
now that some browsers are including browser zoom (page zoom) in
window.devicePixelRatio
Ouch. Who is doing
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 5:32 am, Ian Hickson i...@hixie.ch wrote:
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 12:14 am, Stephen White senorbla...@chromium.org
wrote:
now that some browsers are including browser zoom (page zoom) in
On 11 Sep 2013, at 6:13 am, Ian Hickson i...@hixie.ch wrote:
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 5:32 am, Ian Hickson i...@hixie.ch wrote:
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 12:14 am, Stephen White senorbla...@chromium.org
wrote:
now that
On 9/10/13 3:54 PM, Ian Hickson wrote:
These seem like the logical places for it to be set. Am I missing
something?
No, you're not. I was.
Well, then they'll be broken, I guess. (They'll break safe, though.)
Well, the outcome is user can't use site. (Which they care more about
than
On Fri, 12 Jul 2013, Boris Zbarsky wrote:
On 7/12/13 2:15 PM, Ian Hickson wrote:
The document's referrer is not really defined anywhere in a useful
way that I can find.
What's not useful about the way it's defined? It's set to a specific
string.
I couldn't find where it was
On Tue, Sep 10, 2013 at 12:45 PM, Dean Jackson d...@apple.com wrote:
On 11 Sep 2013, at 5:32 am, Ian Hickson i...@hixie.ch wrote:
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 12:14 am, Stephen White senorbla...@chromium.org
wrote:
now that some browsers are including
On Tue, 10 Sep 2013, Boris Zbarsky wrote:
On 9/10/13 3:54 PM, Ian Hickson wrote:
[some sites compare values that are always-punycoded domains with
values that can be full Unicode for security checks]
Well, then they'll be broken, I guess. (They'll break safe, though.)
Well, the
On Wed, 11 Sep 2013, Dean Jackson wrote:
I think there are two separate things a developer might want:
- the number of actual pixels that correspond to 1 CSS px without zoom
- the page zoom
Why? Exposing page zoom separately from device density seems like a
fundamental abstraction
On 11 Sep 2013, at 12:14 am, Stephen White senorbla...@chromium.org wrote:
now that some browsers are including browser zoom (page zoom) in
window.devicePixelRatio
Ouch. Who is doing this and why?
Dean
On Fri, 12 Jul 2013, Jonas Sicking wrote:
The algorithms in the spec are great when it comes to defining things
with high level of exactness. However they only work well when the
implementations of those algorithms actually look like the algorithms in
the spec.
When they don't, the
On Fri, 12 Jul 2013, Glenn Maynard wrote:
On Fri, Jul 12, 2013 at 2:45 PM, Ian Hickson i...@hixie.ch wrote:
Why? As a user on desktop, I can resize my window however I want, to
be landscape or portrait. Why wouldn't I be allowed to do the same on
any other device?
In mobile
On Tue, Sep 10, 2013 at 10:22 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 15 Jul 2013, Kornel Lesiński wrote:
Since specific, locked screen orientation is mostly needed in games, and
forced rotation is disruptive to other things on the screen (e.g. moving
buttons/addressbar to other physical
On Tuesday, September 10, 2013 at 11:22 PM, Ian Hickson wrote:
On Sat, 13 Jul 2013, Tobie Langel wrote:
It is not uncommon for mobile experiences to rely on the accelerometer
as an input mechanism, for example to control page scrolling (e.g.
Instapaper) or for gameplay.
In such cases,
On Fri, 19 Jul 2013, Brendan Long wrote:
On Jul 19, 2013 3:14 PM, Ian Hickson i...@hixie.ch wrote:
What if we added a supportedPlaybackRates attribute, which holds
an array of playback rates supported by the server, plus
(optionally) any rates the user agent can support due to the
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 restart the browser.
Here's a demo I built that
On Tue, 10 Sep 2013 21:22:51 +0100, Dean Jackson d...@apple.com wrote:
I think there are two separate things a developer might want:
- the number of actual pixels that correspond to 1 CSS px without zoom
- the page zoom
If you merge the two, then an unsuspecting developer might think that
On Tue, 20 Aug 2013, Edward O'Connor wrote:
[W]e do want users to be able to bring up the native controls via a
context menu and be able to use them regardless of what the page
does in its event handlers. So, I request that the spec be explicit
that interacting with the video controls
On Tue, 9 Jul 2013, Igor Minar wrote:
The current url resolution as described in the spec results in some
unhelpful behavior when the following combination of web technologies
are used in a client-side web app:
- a combination of path-relative urls (a
On Wed, 11 Sep 2013, Dean Jackson wrote:
On 11 Sep 2013, at 12:14 am, Stephen White senorbla...@chromium.org
wrote:
now that some browsers are including browser zoom (page zoom) in
window.devicePixelRatio
Ouch. Who is doing this and why?
Why ouch?
Actually what I really think we
On Tue, Sep 10, 2013 at 6:35 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 20 Aug 2013, Glenn Maynard wrote:
It's the behavior users expect when watching videos, which is the case
video should optimize for. If you're doing something else where the
user interacts with the video in other
On 9/10/13 4:13 PM, Ian Hickson wrote:
I guess we'll just have to treat devicePixelRatio as legacy and introduce
a new value that's the real device:pixel ratio, then.
I would be interested in some data on what different UAs do with
devicePixelRatio...
-Boris
On 9/10/13 4:22 PM, Dean Jackson wrote:
I think there are two separate things a developer might want:
- the number of actual pixels that correspond to 1 CSS px without zoom
What are the use cases for this, as opposed to number of actual pixels
that correspond to 1 CSS px?
And are you
On Mon, Sep 9, 2013 at 7:31 PM, Ian Hickson i...@hixie.ch wrote:
Right, resetting the context would definitely be part of the deal. This
mode would be specifically defined as a mode where you had to listen to
onresize or your canvas would almost certainly get cleared sooner or
later. In fact,
On Tue, Sep 10, 2013 at 6:24 PM, Glenn Maynard gl...@zewt.org wrote:
Yeah, my suggestion, if we do this, would be to not do it until high
density displays are even more widely available than now. This is mostly a
convenience and performance-improving API, not a critical feature add.
High-DPI
27 matches
Mail list logo
