1563757 - Track Changes: Ensure ChangesActor/ChangesFront always fires change events

Status: NEW

(DevTools :: Inspector: Changes, task, P2)

Description

[Razvan Caliman [:rcaliman]]

The ChangesActor has an optimization to avoid firing events on changes unless there's evidence of a consumer for those events.
Until a call to ChangesActor.allChanges() is made, no events will be fired that a client can listen to.

The intention for this optimization was to avoid needless event traffic unless the Changes panel was in view (it calls allChanges() once opened).

However, other interested consumers of change events have sprung up and this subtle optimization caused trouble for them with inconsistent firing of events.

Therefore, we should remove this optimization which trips up other developers and always fire change events regardless of any previous method calls to the ChangesActror.

Comment 1

[Razvan Caliman [:rcaliman]]

If moving to a Changes ResouceWatcher-based approach, the singular ChangesActor becomes obsolete.