On 16 Apr 2015, at 6:42 am, Elliott Sprehn espr...@chromium.org wrote:
3. Accessing rendered pixel size is layout-inducing. To avoid layout
thrashing, we should consider making this an asynchronous getter (e.g.
asyncGetBoundignClientRect). This would also prevent renderedsizechanged
events
On 24 Feb 2015, at 6:32 pm, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Feb 24, 2015 at 2:40 AM, Dean Jackson d...@apple.com wrote:
The idea was to allow the resize event on elements. I don't really care what
the solution is, so maybe someone here can come up with a better idea (size
At the recent Houdini meeting there was a vague agreement between the browser
engines on adding a way for elements to be notified when their size changes.
We've run into a number of scenarios where this is extremely useful, and is
otherwise difficult or annoying (e.g. checking your size on a
On 20 Jun 2014, at 12:54 am, Stephen White senorbla...@chromium.org wrote:
On Thu, Jun 12, 2014 at 11:42 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
I think I'd rather not take control of canvas resizing away from
applications, even opt-in. That leads to complexity such as extra
FWIW - I think that
ctx.currentPath != ctx.currentPath
is a horrible mistake and we should fix WebKit.
Dean
On 4 Nov 2013, at 2:47 pm, Rik Cabanier caban...@gmail.com wrote:
On Mon, Nov 4, 2013 at 11:25 AM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Nov 4, 2013 at 1:49 AM, Jürg
On 17 Oct 2013, at 9:20 am, Ian Hickson i...@hixie.ch wrote:
PS: iOS 7 is barely released, but the first bug reports are already
coming in, because the new Mobile Safari now defines Path, and clashes:
https://twitter.com/danetag/status/380636739251220480
Looks like this user solved the
On 11 Sep 2013, at 3:20 am, Robert O'Callahan rob...@ocallahan.org wrote:
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
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 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
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 10 Sep 2013, at 10:00 am, Ian Hickson i...@hixie.ch wrote:
On Wed, 17 Jul 2013, Rik Cabanier wrote:
Ian wrote:
The density aspect of this might be pointless, given the failure of
getImageDataHD(); if we're dropping that one, I'll drop this one at
the same time.
Yes, please drop it
On 4 Sep 2013, at 10:47 am, Boris Zbarsky bzbar...@mit.edu wrote:
On 9/3/13 7:13 PM, Ian Hickson wrote:
Wouldn't checking for window.WebGLRenderingContext be just as unreliable
then? I don't understand why it's ok to be able to test that, but why
probablySupportsContext() wouldn't be ok.
On 25/06/2013, at 5:54 PM, Simon Pieters sim...@opera.com wrote:
On Mon, 24 Jun 2013 23:31:59 +0200, Dean Jackson d...@apple.com wrote:
Also, the presence of window.WebGLRenderingContext doesn't necessarily
indicate
that WebGL is supported. On iOS for example, that object is available
On 25/06/2013, at 5:56 AM, Benoit Jacob jacob.benoi...@gmail.com wrote:
2013/6/21 Benoit Jacob jacob.benoi...@gmail.com
Any other application use cases?
Anyone?
I believe that if no unquestionable application use case can be given, then
this function should be removed from the spec.
On 09/01/2013, at 4:08 PM, Dirk Schulze dschu...@adobe.com wrote:
On Jan 8, 2013, at 9:35 AM, Rik Cabanier caban...@gmail.com wrote:
I looked at pdf2js which is using this fillRule property. As I expected,
introduction of the property results in code like this:
eoFill: function
I sent this to the public-h...@w3.org list:
http://www.w3.org/mid/b2fff68c-cd91-4273-8087-ec3058d24...@apple.com
Copied below.
[[[
I propose adding a new method to HTMLCanvasElement:
interface HTMLCanvasElement : HTMLElement {
boolean supportsContext(DOMString contextId, any... arguments);
On Sep 10, 2012, at 12:28 PM, Tobie Langel tobie.lan...@gmail.com wrote:
On Sep 10, 2012, at 8:14 PM, Dean Jackson d...@apple.com wrote:
I propose adding a new method to HTMLCanvasElement:
interface HTMLCanvasElement : HTMLElement {
boolean supportsContext(DOMString contextId, any
Gullen
Scirra.com
On 10 September 2012 19:14, Dean Jackson d...@apple.com wrote:
I sent this to the public-h...@w3.org list:
http://www.w3.org/mid/b2fff68c-cd91-4273-8087-ec3058d24...@apple.com
Copied below.
[[[
I propose adding a new method to HTMLCanvasElement:
interface
On Sep 10, 2012, at 12:44 PM, Tobie Langel tobie.lan...@gmail.com wrote:
What about enabling feature detection by providing a method per context?
interface HTMLCanvasElement : HTMLElement {
object get2DContext();
object getWebGLContext(any... args);
};
That way, developers can use
On Sep 10, 2012, at 1:03 PM, Rick Waldron waldron.r...@gmail.com wrote:
On Mon, Sep 10, 2012 at 3:56 PM, Tobie Langel tobie.lan...@gmail.com wrote:
This is actually what we could do now. We could hide
window.WebGLRenderingContext
when we can't create one. But then we'd have to hide
On 07/07/2012, at 10:11 AM, Charles Pritchard ch...@jumis.com wrote:
On Thu, Jul 5, 2012 at 1:05 PM, Edward O'Connor eocon...@apple.com wrote:
As things currently stand in the spec, implementations basically need to
keep N+1 bitmaps per canvas, where N is the number of hit regions. I
doubt
On 13 Apr 2005, at 19:31, Ian Hickson wrote:
On Wed, 13 Apr 2005, Dean Jackson wrote:
Ok. Could you provide us with a list of features you believe need use
cases listed? That would be really helpful in creating such a
document.
All of them.
That's never going to happen, just like the XHTML working
22 matches
Mail list logo
