FLUID-6700: Materialised binding makes validation workflow impossible due to backwash protection

Metadata

Source
FLUID-6700
Type
Bug
Priority
Major
Status
Open
Resolution
N/A
Assignee
Antranig Basman
Reporter
Antranig Basman
Created
2021-11-25T06:58:37.685-0500
Updated
2022-02-03T10:40:05.344-0500
Versions
  1. 4.0
Fixed Versions
  1. 5.0
Component
  1. Renderer

Description

The initial implementation of the "domOutput" materialiser makes it impossible to implement workflows which validate/reject updates originating from the DOM, since the backward leg of the materialiser was written with a source exclusion matching its own source. As a result of the "source globbing" we implemented in the ChangeApplier (described by FLUID-5498), the update is considered sourced from the original DOM update triggered by the user, even if it is interrupted by a modelListener. We should probably just remove the guard from the implementation of fluid.materialisers.domValue which currently reads

that.applier.modelChanged.addListener({segs: segs, excludeSource: "DOM"}, modelListener);