> Date: Sat, 29 May 2010 17:02:52 -0700
> From: sam.wei...@gmail.com
> To: mnaga...@chromium.org
> CC: pfeld...@google.com; webkit-dev@lists.webkit.org
> Subject: Re: [webkit-dev] On adding 'console.memory' API (and about the whole
> 'console' object.)
>
> In
In general, hassle should not be used as a rationale for API design :).
Another question ,if the browser has multiple heaps, should it report the
combined memory use by all the heaps or just the heap used by the page the
memory object is coming from?
-Sam
On Sat, May 29, 2010 at 12:48 PM, Mikhai
You mean I should create an .idl description for it? That's not a
problem. Using a vanilla JS object just seemed easier to me, because
adding a new .idl file involves much hassle due to the need of
registering it in a half dozen project files.
On Sat, May 29, 2010 at 19:44, Sam Weinig wrote:
> Wh
Why does this API use a vanilla JS object for the memory object rather than
an interface as we do with pretty much every other API?
-Sam
On Fri, May 28, 2010 at 10:50 AM, Mikhail Naganov wrote:
> Greetings, WebKit deveopers,
>
> As a response to requests from web apps developers, I was intended
How will the directory structure and all the files therein be represented in
the form submission?
-Sam
On Fri, May 28, 2010 at 3:17 PM, John Gregg wrote:
> Hi WebKit,
>
> I recently proposed adding directory upload support to HTML via a new
> attribute to whatwg@, and the discussion arrived at
5 matches
Mail list logo
