Conversely, if it helps to bring the spec closer to the implementations,
one thing we do not intend to implement in Chrome is the automatic high-DPI
canvas scaling (ie., auto-doubling of backing stores, getImageDataHD(),
putImageDataHD(), etc).
I believe Apple has also announced that they are
Yes, those should be taken out.
On Tue, Jul 9, 2013 at 8:40 AM, Stephen White senorbla...@chromium.orgwrote:
Conversely, if it helps to bring the spec closer to the implementations,
one thing we do not intend to implement in Chrome is the automatic high-DPI
canvas scaling (ie., auto-doubling
On Jul 3, 2013 4:38 PM, Justin Novosad ju...@google.com wrote:
On Mon, Jul 1, 2013 at 3:15 PM, Tom Wiltzius wiltz...@chromium.org
wrote:
On Sun, Jun 30, 2013 at 11:49 PM, Mark Callow
callow.m...@artspark.co.jp
wrote:
I thought some pretty strong objections were raised to text
On Mon, Jul 8, 2013 at 9:01 AM, Jonas Sicking jo...@sicking.cc wrote:
On Jul 3, 2013 4:38 PM, Justin Novosad ju...@google.com wrote:
On Mon, Jul 1, 2013 at 3:15 PM, Tom Wiltzius wiltz...@chromium.org
wrote:
On Sun, Jun 30, 2013 at 11:49 PM, Mark Callow
callow.m...@artspark.co.jp
On Mon, Jul 1, 2013 at 3:15 PM, Tom Wiltzius wiltz...@chromium.org wrote:
On Sun, Jun 30, 2013 at 11:49 PM, Mark Callow callow.m...@artspark.co.jp
wrote:
I thought some pretty strong objections were raised to text decoration.
Why are you actively developing it?
There were some
On 2013/06/29 4:30, Tom Wiltzius wrote:
The only major Canvas2D features being actively developed in Chromium right
now are:
- having a canvas context alpha attribute
- text decoration
I thought some pretty strong objections were raised to text decoration.
Why are you actively developing
On Sun, Jun 30, 2013 at 11:49 PM, Mark Callow callow.m...@artspark.co.jpwrote:
On 2013/06/29 4:30, Tom Wiltzius wrote:
The only major Canvas2D features being actively developed in Chromium right
now are:
- having a canvas context alpha attribute
- text decoration
I thought some
The only major Canvas2D features being actively developed in Chromium right
now are:
- having a canvas context alpha attribute
- text decoration
- compositing and blending
- canvas access in workers
(easily referenced from http://www.chromestatus.com/features)
It is concerning to me that
As long as those features don't build upon other unimplemented features,
there should be no risk.
However, accessibility (=hit regions) is a must and should be tackled as
soon as possible.
Rik
On Fri, Jun 28, 2013 at 12:30 PM, Tom Wiltzius wiltz...@chromium.orgwrote:
The only major Canvas2D
I agree there isn't a risk of these unrelated additional features not
matching their hypothetical specs.
However, my concern is Ian's comment that he'd prefer not to add additional
features to the spec -- some of the ones being actively developed in
Chromium aren't added yet, and I'd hate for
Has the Canvas 2D community considered a WebGL-like model to the
introduction of additional features?
By the WebGL model, I mean:
- Define a core feature set that's conservative and limited, but
consistently implemented by all browsers. Enforce consistent support for it
by an exhaustive
On Fri, Jun 28, 2013 at 6:35 PM, Tom Wiltzius wiltz...@chromium.org wrote:
I agree there isn't a risk of these unrelated additional features not
matching their hypothetical specs.
However, my concern is Ian's comment that he'd prefer not to add
additional features to the spec -- some of the
On Fri, Jun 28, 2013 at 7:01 PM, Benoit Jacob jacob.benoi...@gmail.comwrote:
Has the Canvas 2D community considered a WebGL-like model to the
introduction of additional features?
By the WebGL model, I mean:
- Define a core feature set that's conservative and limited, but
consistently
On Fri, 14 Jun 2013, Brian Salomon wrote:
As an implementor, we would prefer the layer approach. This would have
lower overhead in Chromium/Skia. We can make better decisions about
caching and deferred rendering. It also seems like a really handy API
for devs, especially the ability to
14 matches
Mail list logo
