Closed Bug 1500392 Opened 6 years ago Closed 6 years ago

[remote-dbg-next] migrate aboutdebugging test: browser_service_workers_not_compatible.js

Categories

(DevTools :: about:debugging, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1500391

People

(Reporter: jdescottes, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: old-remote-debugging-ng-m3)

Summary: browser_service_workers_pushremote-dbg-next] migrate aboutdebugging test: browser_service_workers_not_compatible.js → [remote-dbg-next] migrate aboutdebugging test: browser_service_workers_not_compatible.js
filter on remote-debugging-next-move-m3-to-m2
filter on remote-debugging-next-move-m3-to-m2
filter on remote-debugging-next-move-m3-to-m2
No longer blocks: remote-debugging-ng-m3
Priority: P3 → P2
Whiteboard: old-remote-debugging-ng-m3

Is this bug superseded by Bug 1500391? Or a "child" bug? Should we close this one?

Flags: needinfo?(jdescottes)

Oh thanks for finding this!!!

It looks like I stumbled when creating this bug. This was meant to be about another test: browser_service_workers_push.js. The summary is correct but the title isn't

And then I ended up migrating the test in Bug 1509038 (and I was wondering why there was test migration for this one,
https://bugzilla.mozilla.org/show_bug.cgi?id=1509038#c4)

Anyway thanks for identifying the mistake. Closing. One more slot for the MVP :)

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jdescottes)
Resolution: --- → DUPLICATE
No longer blocks: remote-debugging-ng-m2
You need to log in before you can comment on or make changes to this bug.