Closed Bug 1533547 Opened 6 years ago Closed 5 years ago

Column Breakpoints are not visible when reloading

Categories

(DevTools :: Debugger, task, P1)

task

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jlast, Assigned: jlast)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

STR

  1. go to dbg-scratchpad.glitch.me and add some column bps
  2. go to https://glitch.com/edit/#!/dbg-scratchpad?path=public/client.js:8:0 and edit client.js
  3. reload

ER: see column breakpoints
AR: don't see column breakpoints

The problem here was that we were not updating the viewport.

This was fixed

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED

I can still reproduce the problem on my machine.

Here is my STR:

  1. Load https://glitch.com/edit/#!/dbg-scratchpad?path=public/client.js:8:0
  2. Click 'Remix to Edit'
  3. Click 'Show' -> In a new window
  4. Select the new tab and open Debugger on it
  5. Select 'client.js' and create Col BP on line console.log('stuff')
  6. Go back to the previous tab, edit the client.js file. You can see how the other tab is auto reloading.
  7. Switch back to the other tab. The BP is gone -> BUG
    Reload and the BP is back.

@Jason, can you reproduce that?

Honza

Flags: needinfo?(jlaster)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Thanks, yes I can.

Flags: needinfo?(jlaster)
Attached image reload.gif
Priority: -- → P1
Status: REOPENED → NEW
Blocks: dbg-breakpoint
No longer blocks: dbg-column-bps-m1
Blocks: 1551199
Blocks: 1551200
Assignee: nobody → jlaster
Status: NEW → ASSIGNED
Whiteboard: [debugger-mvp]
Status: ASSIGNED → UNCONFIRMED
Ever confirmed: false
Whiteboard: [debugger-mvp]
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee: jlaster → nobody
Status: ASSIGNED → UNCONFIRMED
Ever confirmed: false
Status: UNCONFIRMED → NEW
Ever confirmed: true

Honza, I looked into it today and it worked as expected. i.e. when there was a breakpoint position that matched a breakpoint the breakpoint was shown in the UI.

Could you re-test and let me know what you think?

I can still reproduce that.

Try to append a new line e.g. in the function a() 5; so console.log('stuff') moves to the next line.

Honza

Assignee: nobody → jlaster

This looks like a breakpoint syncing edge case with glitch's hot reloading system. We can re-open if we find a more common case.

Status: NEW → RESOLVED
Closed: 6 years ago5 years ago
Resolution: --- → WONTFIX
Type: defect → task
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: