Column breakpoints seem to spring into existance when you stop scrolling

RESOLVED FIXED in Firefox 67

Status

Product:
DevTools
Component:
Debugger
Type:
defect
Status:
RESOLVED FIXED
Reported:
3 months ago
Modified:
21 days ago

People

(Reporter: jlast, Assigned: jlast)

Tracking

Version:
unspecified
Target:
Firefox 67
Dependency tree / graph

Firefox Tracking Flags

(firefox67 fixed)

Details

Attachments

(2 attachments)

Bug 1533547 - Column Breakpoints are not visible when reloading. r=loganfsmyth
47 bytes, text/x-phabricator-request
Details | Review
Bug 1533549 - Column breakpoints seem to spring into existance when you stop scrolling. r=loganfsmyth
47 bytes, text/x-phabricator-request
Details | Review
Assignee

Description

•
3 months ago

STR:

  1. scroll through a file where there are column bps

ER: see them quickly
AR: you don't see them until you stop scrolling
Assignee

Comment 1

•
3 months ago

The problem here is that we use lodash debounce
Assignee

Comment 2

•
3 months ago

Bug 1533547 - Column Breakpoints are not visible when reloading. r=loganfsmyth

Attachment #9049346 - Attachment description: Bug 1533549 - Column breakpoints seem to spring into existance when you stop scrolling. r=loganfsmyth → Bug 1533547 - Column Breakpoints are not visible when reloading. r=loganfsmyth

Comment 4

•
3 months ago 
Pushed by jlaster@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6d58a14e2cef
Column breakpoints seem to spring into existance when you stop scrolling. r=loganfsmyth

Comment 5

•
3 months ago 
Pushed by jlaster@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d1d79a310137
Bug 1533547 - Column Breakpoints are not visible when reloading. r=loganfsmyth

Comment 6

•
3 months ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/6d58a14e2cef
https://hg.mozilla.org/mozilla-central/rev/d1d79a310137

Status: NEW → RESOLVED
Last Resolved: 3 months ago
status-firefox67: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 67
Assignee: nobody → jlaster
You need to log in before you can comment on or make changes to this bug.