Re: [whatwg] [Canvas] Behavior on non-invertable CTM

2014-02-06 Thread Rik Cabanier
On Thu, Feb 6, 2014 at 2:14 PM, Justin Novosad wrote: > On Tue, Jul 23, 2013 at 2:11 PM, Ian Hickson wrote: > > > > > > >> The second does setTransform(0,0,0,0,0,0), which should reset the > CTM > > > >> to a zero matrix (again, not invertible). IE, Opera and FF draw a > > > >> line to 0,0 and c

Re: [whatwg] [Canvas] Behavior on non-invertable CTM

2014-02-06 Thread Ian Hickson
On Thu, 6 Feb 2014, Justin Novosad wrote: > > I am looking into correcting Chrome's behavior to make it spec-compliant in > this case. There is one specific primitive that is proving problematic: > arcTo > > The problem is that the algorithm needs to bring the last point in the > subpath into the

Re: [whatwg] [Canvas] Behavior on non-invertable CTM

2014-02-06 Thread Justin Novosad
On Tue, Jul 23, 2013 at 2:11 PM, Ian Hickson wrote: > > > >> The second does setTransform(0,0,0,0,0,0), which should reset the CTM > > >> to a zero matrix (again, not invertible). IE, Opera and FF draw a > > >> line to 0,0 and close the path afterwards (which kind of makes sense, > > >> since the

Re: [whatwg] iframes, more sandbox

2014-02-06 Thread Shane Hudson
This sounds like an interesting idea, but I think it would quite easily get out of hand if people wanted some options from More Strict but not all of them, there would probably need to be a finer control of permissions. ~ Shane Hudson On Thu, Feb 6, 2014 at 3:54 PM, Chris Coyier wrote: > Hey f

[whatwg] iframes, more sandbox

2014-02-06 Thread Chris Coyier
Hey folks. Long time listener, first time caller. I'm hoping for more a little bit more control over s. We have which is pretty fantastic right now. I'd like to see some possibilities in both directions (more and less strict). More strict: - Disallow modal dialogs (e.g. alert, confirm) but othe

Re: [whatwg] Feedback on seamless iframe attribute

2014-02-06 Thread Ryosuke Niwa
On Feb 3, 2014, at 11:23 AM, Ben Vinegar wrote: > Ultimately, seamless doesn’t affect Disqus, because it only applies to > iframes that share the same origin as the browsing context. Which is good, > because we don’t want to use the seamless attribute anyways – it would let > publishers manipulate