Hi [USER], thanks for working on the changes in this PR! I had a quick chat about this with [USER], and the problem with this fix is that changing DOM value happens asynchronously and that can lead to subtle issues as described in [this comment]([URL]) We think the best approach would be to update the DOM value once the rendering is complete. Currently there is no lifecycle hook that for that, and we'd need a project proposal to add one. If there is a decision to add such lifecycle hook, the fix in this PR can leverage that and we should be able to land the change. 

This is certainly a disappointing outcome, since this is a major performance issue and you put in a lot of effort on this. Sorry that it turned out to be blocked on a major addition like this :/