[Webkit-unassigned] [Bug 110779] New: WebKit API for enabling DOM logging for certain worlds

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=110779

           Summary: WebKit API for enabling DOM logging for certain worlds
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ataly at google.com


The overall goal is to enable logging of DOM accesses carried out by 
JavaScript code running in V8, on a per-world basis. One use-case for such a
mechanism would be to allow the chromium side to obtain a log of DOM accesses carried
by extension code running in certain isolated worlds.

Our approach is to wrap specific DOM bindings for the world so that when invoked,
they first log a message into a log object provided by chromium side.

This patch adds initial plumbing for the above mechanism. In particular it adds the following 
methods to the WebKit chromium API:

* void WebCoverWrapping::setLog(int worldID, WebCoverWrapping::Log* log)

* bool WebCoverWrapping::hasLog(int worldID)

The method setLog simply adds an entry for the worldID and log, in a HashMap present in DOMWrapperWorld
(similar to the map for SecurityOrigin and ContentSecurityPolicy)

Subsequent WebCore patches would add code to appropriately wrap the DOM bindings for a world.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.