You can add a listener for DOMWindowCreated on the iframe, or content-document-global-created from the XPCOM preferences service in order to get notifications when globals are being created.
On Thu, Jun 18, 2015 at 7:07 AM, Frederik Braun <fbr...@mozilla.com> wrote: > On 18.06.2015 15:51, smaug wrote: > > On 06/18/2015 03:37 PM, Frederik Braun wrote: > >> Hi, > >> > >> I am planning to do a little analysis of FxOS Gaia to identify instances > >> of innerHTML assignments at runtime[1]. I am hoping this gives me a more > >> precise number about hot paths (in contrast to just looking at the > >> source code). > > > > What kind of information would you like to get out from the analysis? > > And before even spending too much time with innerHTML, are you sure the > > possible > > performance issues are about it, and not about creating/reflowing layout > > objects for the new elements? > > (innerHTML implementation is in common cases quite well optimized.) > > Thanks for the pointers! > > Ha, I sould have been more expressive. I am not interested in performance: > > I have written an eslint plugin to identify and disallow future patches > that contain assignments of innerHTML which do not use our XSS sanitizer > ( > https://developer.mozilla.org/en-US/Firefox_OS/Security/Security_Automation > ). > > Now I want to look at existing issues and identify those that should be > fixed first. I hope that an instrumentation (and stack traces) can give > me a better idea of what different code paths lead to these sinks. > (On the side, I was also hoping to learn something new :)) > > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
