So what’s keeping Scrivener from implementing this?
As noted above, one very important reason is that it’s not actually technically possible for us to add this. ![]()
Secondly though, what you are describing runs counter to the foundational design principles of the software. Or in other words, it already does this, but in a way we feel is superior to text editor based models.