Re: [whatwg] Enabling LCD Text and antialiasing in canvas

2013-02-15 Thread Stephen White
On Fri, Feb 15, 2013 at 2:37 PM, Robert O'Callahan wrote: > On Sat, Feb 16, 2013 at 4:35 AM, Stephen White > wrote: > >> Even with these constraints, I don't think we can guarantee that it's >> safe to use LCD AA text. Once you've drawn with LCD AA text, even if it's >> safe at the time of drawin

Re: [whatwg] Assigning media resources represented as DOM objects to a media element

2013-02-15 Thread Robert O'Callahan
On Sat, Feb 16, 2013 at 3:46 AM, Glenn Maynard wrote: > a) This isn't the case. The tricky bit was defining precisely when > autorevocation happens; this has been resolved (the "global script clean-up > jobs list"). There's a remaining piece ( > https://www.w3.org/Bugs/Public/show_bug.cgi?id=17

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

2013-02-15 Thread Robert O'Callahan
On Sat, Feb 16, 2013 at 4:35 AM, Stephen White wrote: > Even with these constraints, I don't think we can guarantee that it's safe > to use LCD AA text. Once you've drawn with LCD AA text, even if it's safe > at the time of drawing, there's no guarantee that it will be safe later. > For instance,

Re: [whatwg] Sandboxed IFrames and downloads.

2013-02-15 Thread Ian Hickson
On Fri, 15 Feb 2013, Mike West wrote: > > Ping. Is this a terrible idea? :) Sorry for the delay in answering e-mails. Since last quarter I mostly responded to e-mails while neglecting the bug stream, this quarter I'm mostly focusing on the bugs and neglecting the e-mails. All e-mails with subst

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

2013-02-15 Thread Rik Cabanier
As an other alternative, we could also introduce a 'matteColor' attribute. It's default would be 'transparent'. If it's set to a css color, the canvas will be matted to that color. In addition if you use putImageData or a compositing operator that changes alpha, you always matte with that color af

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

2013-02-15 Thread Rik Cabanier
On Sat, Feb 16, 2013 at 2:35 AM, Stephen White wrote: > On Thu, Feb 14, 2013 at 10:21 PM, Robert O'Callahan > wrote: > >> On Thu, Feb 14, 2013 at 11:59 PM, Stephen White > > wrote: >> >>> I think this is difficult to do in the general case, such as >>> putImageData() or drawImage() or patterns, s

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

2013-02-15 Thread Stephen White
On Thu, Feb 14, 2013 at 10:21 PM, Robert O'Callahan wrote: > On Thu, Feb 14, 2013 at 11:59 PM, Stephen White > wrote: > >> I think this is difficult to do in the general case, such as >> putImageData() or drawImage() or patterns, since you would need to examine >> all the pixels of the source ima

Re: [whatwg] Assigning media resources represented as DOM objects to a media element

2013-02-15 Thread Glenn Maynard
On Tue, Jan 22, 2013 at 9:19 PM, Robert O'Callahan wrote: > Currently the only way to use one of these objects as the source of a media > element is via "element.src = URL.createObjectURL(object)". This is > problematic because the URLs minted by createObjectURL require manual > revocation. (Forms

Re: [whatwg] Assigning media resources represented as DOM objects to a media element

2013-02-15 Thread Jonas Sicking
On Fri, Feb 15, 2013 at 2:43 AM, Robert O'Callahan wrote: > On Fri, Feb 15, 2013 at 10:50 PM, Jonas Sicking wrote: >> >> Also, for what it's worth, I'm holding out hope that we can change >> createObjectURL to be autorevoking by default. That's what the latest >> drafts are saying and no implemen

Re: [whatwg] Assigning media resources represented as DOM objects to a media element

2013-02-15 Thread Robert O'Callahan
On Fri, Feb 15, 2013 at 10:50 PM, Jonas Sicking wrote: > Also, for what it's worth, I'm holding out hope that we can change > createObjectURL to be autorevoking by default. That's what the latest > drafts are saying and no implementation has objected, despite repeated > pokings. > Has any implem

Re: [whatwg] Assigning media resources represented as DOM objects to a media element

2013-02-15 Thread Jonas Sicking
On Thu, Jan 24, 2013 at 2:49 AM, Robert O'Callahan wrote: > On Thu, Jan 24, 2013 at 9:44 PM, Anne van Kesteren wrote: > >> On Wed, Jan 23, 2013 at 4:19 AM, Robert O'Callahan >> wrote: >> > I think this would be a worthwhile addition to the Web platform. >> >> It's somewhat ironic this happened,

Re: [whatwg] inputmode feedback

2013-02-15 Thread Jonas Sicking
On Wed, Feb 13, 2013 at 11:29 AM, Mounir Lamouri wrote: > Hi, > > Mozilla did implement an inputmode attribute for the element a > few months ago and the HTML specification has been updated after that to > introduce that attribute. Given that the specification and our > implementation was not mat

Re: [whatwg] Sandboxed IFrames and downloads.

2013-02-15 Thread James Ross
A quick test across browsers would suggest others think it is a reasonable protection to include: both Internet Explorer 10 and Firefox 18 block (ignore) the download attempt in the sandboxed . I couldn't find any documentation on either browser doing this, though, or if they have a sandbox

Re: [whatwg] inputmode feedback

2013-02-15 Thread 河内 隆仁
Hello Mounir, On Thu, Feb 14, 2013 at 4:29 AM, Mounir Lamouri wrote: > Regarding the three Japanese specific types, it is not clear if > inputmode is the best way to solve the use cases intended to be solved. > Actually, 'kana' and 'katakana' are trying to give a hint about the > script that has

Re: [whatwg] Sandboxed IFrames and downloads.

2013-02-15 Thread Mike West
Ping. Is this a terrible idea? :) -- Mike West , Developer Advocate Google Germany GmbH, Dienerstrasse 12, 80331 München, Germany Google+: https://mkw.st/+, Twitter: @mikewest, Cell: +49 162 10 255 91 On Sat, Feb 2, 2013 at 7:11 PM, Mike West wrote: > It's currently possible to force a downloa