Bug 69879
| Summary: | Web Inspector: [JSC] Breakpoint not hit if code is called from debug console | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jon Honeycutt <jhoneycutt> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | apavlov, burg, bweinstein, efidler, ggaren, joepeck, keishi, kpiascik, loislo, mark.lam, oliver, pfeldman, pmuellr, rik, vsevik, yurys |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | data:text/html,<script>function x() { return 0; }</script><button onclick="x()">click me</button> | ||
Jon Honeycutt
A JS breakpoint set in the inspector will not be hit if the code is called from the debug console.
To reproduce:
1. Open the above URL
2. Inspect the page
3. Go to the Scripts panel, and select the script "button%3E" from the drop-down
4. Put a breakpoint on line 1
5. Go back to the browser, and click the button in the page. Note that the breakpoint is hit.
6. Open the debug console, and run x()
The function is called and returns 0, which prints to the console, but the breakpoint is not hit.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jon Honeycutt
<rdar://problem/10269504>
Vsevolod Vlasov
I can not reproduce that on chromium ToT.
Is it Safari specific or are you using an older version?
Jon Honeycutt
I cannot reproduce in Chrome either. Seems to be Safari-specific.