[AU1] rendering / promisses / microtask

1

Hi,

Since a few Chromium versions (>139, <=142) we experience failures in updating bindings unless some kind of repaint is triggered, whenever the devtools is opened.
Yes, really… So very hard to detect and fix. And no clue where it might be located.

Is there someone:

  • that also experiences these issues?
  • from the dev-team that might have useful information on any possible cause and/or fix if indeed it is related to the aurelia core?

I’m thinking it might be related to [css-view-transitions-1] finished promise timing · Issue #12442 · w3c/csswg-drafts · GitHub that’s why I decided to post the question here too…

Aurelia 1
issue occurs in Google Chrome 142 when devtools are opened
issue occurs NOT in firefox
issue occurs NOT in Opera 123 with Chromium 139

2

The changelog states that only view transition timing will be affected, any existing timing isnt. So unless theres something changed under the hood without getting public, existing apps should not experience breakage. Though one thing we can try, is to change the queueMicroTask implementation to the latest native API. Like the following:

TaskQueue.prototyle.requestFlushMicroTaskQueue = () => queueMicroTask(() => this.flushMicroTaskQueue());
1 Like
3

Thanks for the reply!

There is a small typo in your code snippet, but I understand what you tried to do. I’ll continue my research, if I encounter something useful I will share it.

4

Update: all was miraculously fixed with Chrome update 143…

1 Like