[webkit-dev] Moving MemoryInfo under window.internals
rniwa at webkit.org
Tue May 28 16:49:13 PDT 2013
Sounds good to me. Just make sure we don't break performance tests.
- R. Niwa
On Tue, May 28, 2013 at 1:27 PM, Žan Doberšek <zandobersek at gmail.com> wrote:
> the MemoryInfo interface is currently exposed in window.console and
> window.performace despite not being standardized or in process of
> standardization by any spec. It's also only partially functional under the
> JSC bindings as the jsHeapSizeLimit attribute returns an undefined value.
> At the moment grepping through the source tree only shows two uses of the
> interface in a couple of PerformanceTests files. Is anyone else aware
> of any other places where it's used downstream (so its removal would break
> things outside of WebKit)?
> If possible, I propose moving the interface under window.internals and
> adjust the two places where it's used. This also opens the possibility of
> removing two MemoryInfo-specific settings, memoryInfoEnabled and
> quantizedMemoryInfoEnabled. The quantization of the given memory
> information is also not necessary anymore as the information is not exposed
> to the Web anymore.
> The jsHeapSizeLimit attribute should be removed as well as it's basically
> a no-op with the JSC bindings.
>  http://trac.webkit.org/browser/trunk/Source/WebCore/page/Console.idl
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev