Re: [whatwg] Bicubic filtering on context.drawImage

2013-12-09 Thread Juriy Zaytsev
On Mon, Dec 9, 2013 at 4:06 PM, Glenn Maynard wrote: > On Mon, Dec 9, 2013 at 1:21 AM, Tab Atkins Jr. > wrote: > > > Hm, I wonder if image-interpolation on the should affect > > this? It's defined to only have an effect when you scale the > > element itself, but I think it probably makes sens

Re: [whatwg] Questions regarding Path object

2013-09-20 Thread Juriy Zaytsev
FWIW, in Fabric.js [1], everything is scoped under global `fabric` object. `fabric.Path`, `fabric.Circle`, `fabric.Color`, etc. For any third-party library in a cross-browser environment, this has been the only sane strategy of avoiding conflicts and keeping things scalable. We learned about "glob

Re: [whatwg] Browser support or polyfill for latest Canvas spec additions?

2013-01-15 Thread Juriy Zaytsev
AFAIK, only dashed lines in WebKit at the moment — http://kangax.github.com/jstests/canvas-v5/ More things coming soon, such as Path — https://bugs.webkit.org/show_bug.cgi?id=97333 Not sure about shims. I implemented some of the features (paths, ellipses, dashed lines) in Fabric.js (http://fabric

Re: [whatwg] Canvas 2d: proposal to add path(DOMString)

2011-07-31 Thread Juriy Zaytsev
I'd love to see something like this as well. In my experience this takes more than 80 lines. In Fabric.js [1], for example, `fabric.Path#render` has ~180 LOC chunk [2] dedicated to doing exactly this — drawing translated-from-SVG path using a combination of `lineTo`, `moveTo`, `bezierCurveTo`, etc

Re: [whatwg] Proposing .toBlob(contentType)

2011-04-13 Thread Juriy Zaytsev
I would be in favor of this. In my recent app — http://mustachified.com — I used `mozGetAsFile` to retrieve file from canvas, append it to form data and send to an external service via cross-domain request. When mozGetAsFile was not available, I had to build blob manually from canvas' data url. A

[whatwg] Removal of blocking script

2010-11-15 Thread Juriy Zaytsev
When removing [1] a long-loading script element from a document, browsers seem to disagree on whether such removal should affect page rendering. A simple test — http://kangax.github.com/jstests/blocking_script_removal_test/— shows that Opera (9.x - 11) and IE (5.5 - 9) immediately continue parsing

Re: [whatwg] document.head

2009-09-20 Thread Juriy Zaytsev
mplement document.documentElement and document.body. On Sep 20, 2009, at 4: 00PM, Juriy Zaytsev wrote: Surely better than abominable – `document.getElementsByTagName('head')[0]` :) I agree. Unfortunately that is the most popular method I've seen. There are better solutions, but they haven&

Re: [whatwg] document.head

2009-09-20 Thread Juriy Zaytsev
On Sep 20, 2009, at 5:20 PM, Joseph Pecoraro wrote: On Sep 20, 2009, at 4: 24PM, Juriy Zaytsev wrote: Speaking of `document.head`, I think Mootools does exactly that. Good thinking. I took a look at some JavaScript Libraries / Frameworks. Here are some quick counts of how many times I

Re: [whatwg] document.head

2009-09-20 Thread Juriy Zaytsev
On Sep 20, 2009, at 4:15 PM, Joseph Pecoraro wrote: On Sep 20, 2009, at 3:57 PM, Michael A. Puls II wrote: I think it'd be cool to have to complement document.documentElement and document.body. On Sep 20, 2009, at 4: 00PM, Juriy Zaytsev wrote: Surely better than abomi

Re: [whatwg] document.head

2009-09-20 Thread Juriy Zaytsev
On Sep 20, 2009, at 3:57 PM, Michael A. Puls II wrote: On Sun, 20 Sep 2009 14:22:38 -0400, Joseph Pecoraro > wrote: Was there any discussion for including "document.head" in HTML5? I think it'd be cool to have to complement document.documentElement and document.body. Surely better than