939742 - Investigate removing a sync flush when a window is closed

Status: RESOLVED DUPLICATE of bug 1171708

(Firefox :: Session Restore, defect)

Description

[Tim Taubert [:ttaubert] (inactive)]

Bug 874502 did some work on making window.close() not truly async but it looks like that only makes it happen on the next tick?

With bug 930967 we need a sync flush when a window is closed to ensure we don't lose data that is currently queued in frame scripts. It would be great to be able to remove the sync flush and make window.close() wait for an async message that is sent from the frame script.

Comment 1

[Bobby Holley (:bholley)]

(In reply to Tim Taubert [:ttaubert] from comment #0)
> Bug 874502 did some work on making window.close() not truly async

No, the opposite.

> but it
> looks like that only makes it happen on the next tick?

precisely.

> With bug 930967 we need a sync flush when a window is closed to ensure we
> don't lose data that is currently queued in frame scripts. It would be great
> to be able to remove the sync flush and make window.close() wait for an
> async message that is sent from the frame script.

From, this, I'll assuming that the first part of comment 0 was a typo.

Comment 2

[Tim Taubert [:ttaubert] (inactive)]

Yes, sorry. I meant to say "not truly sync".

Comment 3

[Mike Conley (:mconley) (:⚙️)]

This is being done in bug 1171708.