Closed Bug 1060925 Opened 10 years ago Closed 3 years ago

Switch to window-ready|destroyed events of the BrowsingContextTargetActor

Categories

(DevTools :: Storage Inspector, defect, P3)

Product:
DevTools
Component:
Storage Inspector
Type:
defect

Tracking

(Fission Milestone:Future)

Status:
RESOLVED INVALID
Project Flags:
Fission Milestone Future

People

(Reporter: ntim, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: dt-fission-future)

No description provided.
Blocks: 977043, 970517
Depends on: 1061509
Also doing this would also allow you to stop using `browser` reference and would make the actor work on b2g!
Assignee: nobody → mratcliffe
Depends on: 1194190
Blocks: 1194190
No longer depends on: 1194190
A correction to comment 1. Bug 1061509 will take care of properly firing the events. A combination of this and that will make frame selection automagically work.
Priority: -- → P2
Summary: Switch to window-ready|destroyed events of the tabActor → Switch to window-ready|destroyed events of the BrowsingContextTargetActor
Product: Firefox → DevTools

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?
Whiteboard: [fission-]

Alex, is this still relevant?

Honza

Flags: needinfo?(poirot.alex)

Well, yes, this bug is about making the storage panel work with the iframe drop down menu.
This should still be broken as I'm not aware of any work being done around window-ready/destroyed events in storage.

Having said that, we would probably revisit the implementation of the iframe dropdown someday and ultimately get rid of these window-ready/destroy evens in favor of one brand new WindowGlobalTargetActor for each new navigation no matter if it is top level of iframe document.
But there is no concrete plan yet to do that. It could be a M3 cleanup task.

Flags: needinfo?(poirot.alex)

Thanks for the explanation Alex.

Honza

Fission Milestone: --- → M7
Priority: P2 → P3
Whiteboard: [fission-] → dt-fission-m3-reserve

Honza said this is not part of dt-fission-m3-mvp and is not considered Fission M7 blocker.

Fission Milestone: M7 → ---

Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: --- → Future
Whiteboard: dt-fission-m3-reserve → dt-fission-future

This no longer make sense now that we moved to storage resources.

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