Closed Bug 680660 Opened 15 years ago Closed 2 years ago

Consider how onStep should interact with breakpoints

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
Other Branch
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: jorendorff, Unassigned)

Details

Follow-up to bug 673125. The patch in that bug adds a test (Frame-onStep-08.js) that basically says that if you set a breakpoint on every line of a script, onStep should still fire. I wrote the test, though, and I wasn't really thinking about it. That could be annoying API. I'm not sure there's a decision that will be good for all users. We should at least discuss it, though, make a deliberate choice, and document it.
Assignee: general → nobody
Severity: normal → S3

There isn't any indication that this API choice is annoying that I can see (based on searching Bugzilla and the fact that this test hasn't changed in 13 years).

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.