Moritz L'Hoest

@engram-design Got it, thanks!

@engram-design Thanks for the explanation! I can see that this can make sense for some editorial workflows. It doesn't occur in our use-case, so my publishers were a bit confused...

@engram-design That would be great, thanks!

We're also seeing this issue. Updating an older entry with a super table field inside a matrix field caused the 3 super table blocks inside the matrix block to be...

@engram-design We're still seeing this issue on Super Table 3.0.7 (Craft 4.3.6.1). We can't reliably reproduce it, it only sometimes happens in production, seemingly randomly. Some content is saved, then...

Just got a client report about this issue again. An entry with a matrix block with a super table field inside it. Last saved in April, then a couple of...

@engram-design Could we get a comment on this? Would be nice to know if and when this might be fixed. This is one of the largest issue we're facing in...

@engram-design How about only creating a new `changedFieldIndicator` if any properties of the super table have actually changed? This would cut out 98% of the noise. This is really only...

@tsteur Thanks for the reply! > Do you maybe have a link to the page where this is mentioned? [This comment](https://github.com/matomo-org/matomo/issues/16361#issuecomment-741662259) on issue #16361 has more information: > If Art....

@tsteur Thanks! Yeah, would be great to get a some more opinions for this. > Just wanted to already mention that we're working on a feature to disable some things...