Open Bug 1594726 Opened 2 years ago Updated 9 months ago

Edit & Resend request should be executed in the right context

Categories

(DevTools :: Netmonitor, enhancement, P3)

enhancement

Tracking

(Fission Milestone:Future)

Fission Milestone Future

People

(Reporter: Honza, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: dt-fission-future)

There are two features in the Network monitor that allow resending HTTP requests.

  • Resend
  • Edit and Resend

(both accessible through context menu)

Requests should always be resent in the right context (e.g. OOP frame) and so, using the right scope settings (e.g. CORS). This is particularly important for Fission.

Honza

Whiteboard: dt-fission-reserve

Tracking Fission DevTools bugs for Fission Nightly (M6)

Fission Milestone: --- → M6
Type: defect → enhancement
Priority: P3 → P2
Whiteboard: dt-fission-reserve → dt-fission-m2-mvp
Priority: P2 → P3
Whiteboard: dt-fission-m2-mvp → dt-fission-m2-reserve

dt-fission-m2-reserve bugs do not need to block Fission Nightly (M6). For now, let's track them for Fission riding the trains to Beta (M7) so we revisit these bugs before we ship Fission.

Fission Milestone: M6 → M7
Whiteboard: dt-fission-m2-reserve → dt-fission-m2-reserve, dt-fission-M3-mvp
Whiteboard: dt-fission-m2-reserve, dt-fission-M3-mvp → dt-fission-M3-mvp

Bulk move of all dt-fission-m3-mvp bugs to Fission MVP milestone.

Fission Milestone: M7 → MVP
Whiteboard: dt-fission-M3-mvp → dt-fission-m3-reserve

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

Fission Milestone: MVP → Future
Whiteboard: dt-fission-m3-reserve → dt-fission-future
You need to log in before you can comment on or make changes to this bug.