Closed Bug 1614761 Opened 5 years ago Closed 5 years ago

Port content-refreshblocker.js refresh blocking to Fission

Categories

(Firefox :: General, task, P3)

task

Tracking

()

RESOLVED FIXED
82 Branch
Fission Milestone Future
Tracking Status
firefox82 --- fixed

People

(Reporter: enndeakin, Assigned: enndeakin)

References

Details

Attachments

(1 file)

This is used I think to prevent pages from reloading. This bug is about converting it to JSWindowActor and verifying what needs to be done for fission.

The content code is in content-refreshblocker.js

kmag and Nika ask whether reloading even applies to subframes.

Tracking for Fission Nightly (M6)

Fission Milestone: --- → M6
Summary: Port refresh blocking to fission → Port content-refreshblocker.js refresh blocking to Fission

Tracking for Fission M6b Nightly milestone.

Fission Milestone: M6 → M6b
Assignee: nobody → enndeakin

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: General → DOM: Content Processes
Product: Firefox → Core
Component: DOM: Content Processes → General
Product: Core → Firefox

Seems to be affecting only top level window reloads. Jamie, please confirm that this will not be critical to fix for Fission.

Status: NEW → ASSIGNED
Fission Milestone: M6b → Future
Flags: needinfo?(jteh)

This was implemented many years ago in bug 83265. It doesn't look like the preference is exposed through UI any more, though I can't find where it was removed. Also, I haven't seen many sites use meta refresh these days, though I have no data for that.

The above does suggest it's not critical for Fission release. That said, we have no telemetry for this, so it's possible there are still users who use this.

Asa, thoughts?

Flags: needinfo?(jteh) → needinfo?(asa)

Also, NI Marco for his thoughts.

Flags: needinfo?(mzehe)

I don't think I've seen this meta refresh being used anywhere for years. If updates happen nowadays, they happen dynamically with JS, and are thus much less intrusive.

Flags: needinfo?(mzehe)

Gijs describes the reasoning for removing the UI for this at https://bugzilla.mozilla.org/show_bug.cgi?id=1365133#c260

That said, I have a patch that implements this already.

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1660331 on refresh blocking UI not appearing in subframes.

Pushed by neil@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/71dbed0305a2 move refresh blocking handling from framescript to an actor, r=Gijs
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
Flags: needinfo?(asa)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: