Re: [webkit-dev] What is the relationship between WebIDL and WebKitIDL?

On Wed, Mar 14, 2012 at 07:08, Seo Sanghyeon wrote: > However, there doesn't seem to be any progress on this. > I am interested in moving this forward. Is it okay? Yes. It would be much appreciated. -- erik ___ webkit-dev mailing list webkit-dev@lists

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Mon, Apr 16, 2012 at 3:34 PM, Maciej Stachowiak wrote: > > On Apr 16, 2012, at 1:44 PM, Darin Fisher wrote: > > On Mon, Apr 16, 2012 at 1:42 PM, Oliver Hunt wrote: > >> >> On Apr 16, 2012, at 1:00 PM, Darin Fisher wrote: >> >> On Mon, Apr 16, 2012 at 12:55 PM, Maciej Stachowiak wrote: >> >>>

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 4:30 PM, Maciej Stachowiak wrote: > > On Apr 16, 2012, at 4:03 PM, Dirk Schulze wrote: > >>> >>> Different developers will have different priorities. HD image data and >>> async readback both have potential benefits in image quality and >>> nonblocking responsiveness resp

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 4:03 PM, Dirk Schulze wrote: >> >> Different developers will have different priorities. HD image data and async >> readback both have potential benefits in image quality and nonblocking >> responsiveness respectively. Here is an example of an application using >> getImageD

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On 4/16/2012 3:34 PM, Maciej Stachowiak wrote: On Apr 16, 2012, at 1:44 PM, Darin Fisher wrote: On Mon, Apr 16, 2012 at 1:42 PM, Oliver Hunt > wrote: On Apr 16, 2012, at 1:00 PM, Darin Fisher mailto:da...@chromium.org>> wrote: On Mon, Apr 16, 2012 at 12:55

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

> > Different developers will have different priorities. HD image data and async > readback both have potential benefits in image quality and nonblocking > responsiveness respectively. Here is an example of an application using > getImageData which would clearly benefit from HD, but it's not ob

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 1:44 PM, Darin Fisher wrote: > On Mon, Apr 16, 2012 at 1:42 PM, Oliver Hunt wrote: > > On Apr 16, 2012, at 1:00 PM, Darin Fisher wrote: > >> On Mon, Apr 16, 2012 at 12:55 PM, Maciej Stachowiak wrote: >> >> On Apr 16, 2012, at 10:52 AM, Darin Fisher wrote: >> >>> Could t

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 1:48 PM, Oliver Hunt wrote: > > On Apr 16, 2012, at 1:44 PM, Darin Fisher wrote: >> I'm not sure why developers would choose to ignore HiDPI. It seems like it >> helps their apps/pages look better! >> >> You really feel like you need to "kowtow" to developers to get them

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 1:44 PM, Darin Fisher wrote: > I'm not sure why developers would choose to ignore HiDPI. It seems like it > helps their apps/pages look better! > > You really feel like you need to "kowtow" to developers to get them to adopt > HiDPI? The existing API supported high dpi, n

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Mon, Apr 16, 2012 at 1:42 PM, Oliver Hunt wrote: > > On Apr 16, 2012, at 1:00 PM, Darin Fisher wrote: > > On Mon, Apr 16, 2012 at 12:55 PM, Maciej Stachowiak wrote: > >> >> On Apr 16, 2012, at 10:52 AM, Darin Fisher wrote: >> >> Could this be an opportunity to design an asynchronous API for

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 1:00 PM, Darin Fisher wrote: > On Mon, Apr 16, 2012 at 12:55 PM, Maciej Stachowiak wrote: > > On Apr 16, 2012, at 10:52 AM, Darin Fisher wrote: > >> Could this be an opportunity to design an asynchronous API for fetching the >> pixel buffer? It seems like many implementa

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On 4/16/2012 12:55 PM, Maciej Stachowiak wrote: On Apr 16, 2012, at 10:52 AM, Darin Fisher wrote: Could this be an opportunity to design an asynchronous API for fetching the pixel buffer? It seems like many implementations are GPU backed now, and fetching the pixel buffer is an expensive (bl

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Mon, Apr 16, 2012 at 12:55 PM, Maciej Stachowiak wrote: > > On Apr 16, 2012, at 10:52 AM, Darin Fisher wrote: > > Could this be an opportunity to design an asynchronous API for fetching > the pixel buffer? It seems like many implementations are GPU backed now, > and fetching the pixel buffer

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

On Apr 16, 2012, at 10:52 AM, Darin Fisher wrote: > Could this be an opportunity to design an asynchronous API for fetching the > pixel buffer? It seems like many implementations are GPU backed now, and > fetching the pixel buffer is an expensive (blocking) operation. Had you > considered ma

Re: [webkit-dev] Feature announcement: canvas pixel access API additions for high-resolution backing stores

Could this be an opportunity to design an asynchronous API for fetching the pixel buffer? It seems like many implementations are GPU backed now, and fetching the pixel buffer is an expensive (blocking) operation. Had you considered making such a change? Regards, -Darin On Thu, Apr 12, 2012 at

[webkit-dev] Adding archive.org-based page loading time performance tests

*Summary* I propose to add a new page load time performance test suite that loads pages on archive.org. *Problem* Google's page cycler and Apple's PLT test suites are both private due to copyright restrictions, and people outside of these two organizations cannot see the contents. This severely li