+Yoichi Osato, who is working on implementing inputmode spec for Blink and
Chromium.
On Fri, Jun 7, 2013 at 8:04 AM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jun 6, 2013 at 2:08 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 15 Feb 2013, Jonas Sicking wrote:
Using semantic names might
Back from a vacation, sorry about the late reply - hopefully still useful.
On Wed, Aug 7, 2013 at 3:02 PM, Glenn Maynard gl...@zewt.org wrote:
On Wed, Aug 7, 2013 at 4:21 PM, Chang Shu csh...@gmail.com wrote:
If we plan to enhance the Encoding spec, I personally prefer a new pair
of
On Mon, Aug 12, 2013 at 6:16 PM, Joshua Bell jsb...@google.com wrote:
FWIW, I've landed an experimental (behind a flag) implementation of the API
in Blink/Chromium; changing it is definitely possible for us. I believe Moz
is shipping it web-exposed already in FF?
Yes, since Firefox 18 (since
On Fri, Aug 9, 2013 at 1:40 PM, Justin Novosad ju...@google.com wrote:
On Fri, Aug 9, 2013 at 4:20 PM, Ian Hickson i...@hixie.ch wrote:
This is a quite widely requested feature. What should we do to address
this request instead?
What if resetClip restored the clip to what it was at
I think most performance-minded use cases will be fine with junov's idea
since they will not want to touch the stack in the first place.
Here's a simple use case: Suppose there are nested objects to be drawn,
Panels, TextBlocks, and other visual elements. Panels are containers that
draw a
On Mon, Aug 12, 2013 at 2:15 PM, Rik Cabanier caban...@gmail.com wrote:
On Fri, Aug 9, 2013 at 1:40 PM, Justin Novosad ju...@google.com wrote:
On Fri, Aug 9, 2013 at 4:20 PM, Ian Hickson i...@hixie.ch wrote:
This is a quite widely requested feature. What should we do to address
this
On Mon, Aug 12, 2013 at 1:24 PM, Justin Novosad ju...@google.com wrote:
On Mon, Aug 12, 2013 at 2:15 PM, Rik Cabanier caban...@gmail.com wrote:
On Fri, Aug 9, 2013 at 1:40 PM, Justin Novosad ju...@google.com wrote:
On Fri, Aug 9, 2013 at 4:20 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, Aug 12, 2013 at 4:34 PM, Rik Cabanier caban...@gmail.com wrote:
On Mon, Aug 12, 2013 at 1:24 PM, Justin Novosad ju...@google.com wrote:
On Mon, Aug 12, 2013 at 2:15 PM, Rik Cabanier caban...@gmail.com wrote:
On Fri, Aug 9, 2013 at 1:40 PM, Justin Novosad ju...@google.com
Good point, I think part of the problem has to do with the fact that save
is non-selective (saves all of the state).
Yes, since save() and restore() save and restore everything, it creates the
side effect of needing to set ctx.font/fillStyle/strokeStyle more often
than otherwise, which are slow
Ok, so here is a simple proposal:
IDL:
enum CanvasSaveMode { all, transform, clip, transform-and-clip };
save(optional CanvasSaveMode mode);
Modes:
all: save the entire rendering context state
transform: save only the current transform
clip: save only the current clip
if mode is not specified,
On Mon, Aug 12, 2013 at 2:26 PM, Justin Novosad ju...@google.com wrote:
Ok, so here is a simple proposal:
IDL:
enum CanvasSaveMode { all, transform, clip, transform-and-clip };
save(optional CanvasSaveMode mode);
Modes:
all: save the entire rendering context state
transform: save only the
On Tue, Aug 6, 2013 at 4:47 PM, Adam Klein ad...@chromium.org wrote:
On Tue, Aug 6, 2013 at 4:38 PM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Aug 6, 2013 at 4:27 PM, Adam Klein ad...@chromium.org wrote:
On Tue, Aug 6, 2013 at 4:21 PM, Jonas Sicking jo...@sicking.cc wrote:
As I recall it
On Mon, Aug 12, 2013 at 10:27 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Aug 12, 2013 at 6:16 PM, Joshua Bell jsb...@google.com wrote:
FWIW, I've landed an experimental (behind a flag) implementation of the API
in Blink/Chromium; changing it is definitely possible for us. I believe
On Aug 8, 2013, at 7:29 AM, Jukka K. Korpela jkorp...@cs.tut.fi wrote:
2013-08-08 2:57, Ryosuke Niwa wrote:
On Aug 2, 2013, at 6:10 AM, Jukka K. Korpela jkorp...@cs.tut.fi
wrote:
[...]
But regarding the effect of language markup on fonts, the effect is
limited to situations where the
If this is strictly a performance issue, then we definitely should fix that
before adding new API, IMHO. It would be great to get some reduced test
cases where save()/restore() is a bottleneck.
(Incidentally, we did some performance fixes recently for setFont() in
Chrome.)
Stephen
On Mon, Aug
On Fri, Aug 9, 2013 at 2:34 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 9 Aug 2013, Rik Cabanier wrote:
On Fri, Aug 9, 2013 at 1:32 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 11 Mar 2013, Kenneth Russell wrote:
It would be useful to be able to create an ImageData [1] object with
On Sat, Aug 10, 2013 at 9:43 PM, Rik Cabanier caban...@gmail.com wrote:
Ah, so you are relying on pixel snapping (=rounded up to 2 pixels).
Rounded to the nearest integer pixel. If you give 1.25, the width would be
1.
If you can do that with your approach, why not with strokes that are
On Mon, Aug 12, 2013 at 6:45 PM, Glenn Maynard gl...@zewt.org wrote:
On Sat, Aug 10, 2013 at 9:43 PM, Rik Cabanier caban...@gmail.com wrote:
Ah, so you are relying on pixel snapping (=rounded up to 2 pixels).
Rounded to the nearest integer pixel. If you give 1.25, the width would
be 1.
18 matches
Mail list logo
