[Webkit-unassigned] [Bug 53235] New: Web Inspector: new api for managing JavaScript breakpoints
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jan 27 04:49:18 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=53235
Summary: Web Inspector: new api for managing JavaScript
breakpoints
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: podivilov at chromium.org
CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
pmuellr at yahoo.com, joepeck at webkit.org,
pfeldman at chromium.org, yurys at chromium.org,
bweinstein at apple.com, apavlov at chromium.org,
loislo at chromium.org
In new protocol, there should be three methods related to JavaScript breakpoints:
[domain=Debugger] void setJavaScriptBreakpoint(in Object breakpoint, out String breakpointId, out Array locations);
[domain=Debugger] void removeJavaScriptBreakpoint(in String breakpointId);
[notify, domain=Debugger] void breakpointResolved(out String breakpointId, out Object location);
breakpoint argument has the following properties:
1. url (optional)
2. sourceID (optional)
3. lineNumber
4. columnNumber (optional, defaults to 1)
5. condition (optional)
6. enabled (optional, defaults to true)
At least one of url and sourceID should be provided.
location specifies actual location where breakpoint was resolved by VM, location has 3 properties: sourceID, lineNumber, columnNumber.
When frontend enables debugger, it should set all JavaScript breakpoints one by one using setJavaScriptBreakpoint method. After that, breakpoints will be resolved in parsed scripts automatically during debugging session (until frontend is closed).
When provisional breakpoint is resolved (e.g. on navigation), breakpointResolved notification is used to update frontend with the new breakpoint location.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list