# \[AU1\] rendering / promisses / microtask

**URL:** <https://discourse.aurelia.io/t/au1-rendering-promisses-microtask/6542>\
**Category:** Uncategorized\
**Created:** [November 13, 2025, 2:56pm UTC](https://discourse.aurelia.io/t/au1-rendering-promisses-microtask/6542 "2025-11-13T14:56:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mroeling](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/mroeling/32/781_2.png) [@mroeling](https://discourse.aurelia.io/u/mroeling)\
**Post date:** [November 13, 2025, 2:56pm UTC](https://discourse.aurelia.io/t/au1-rendering-promisses-microtask/6542/1 "2025-11-13T14:56:08Z")

</div>

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](https://github.com/w3c/csswg-drafts/issues/12442) that’s why I decided to post the question here too…

> **[Chrome 140  |  Release notes  |  Chrome for Developers](https://developer.chrome.com/release-notes/140?hl=en#view_transition_finished_promise_timing_change)**
>
> The ToggleEvent source attribute, the font-variation-settings descriptor, and more.

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

---

<div class="post-metadata">

**Author:** ![bigopon](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/bigopon/32/18_2.png) [@bigopon](https://discourse.aurelia.io/u/bigopon)\
**Post date:** [November 13, 2025, 3:26pm UTC](https://discourse.aurelia.io/t/au1-rendering-promisses-microtask/6542/2 "2025-11-13T15:26:36Z")

</div>

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:

```typescript
TaskQueue.prototyle.requestFlushMicroTaskQueue = () => queueMicroTask(() => this.flushMicroTaskQueue());

```

---

<div class="post-metadata">

**Author:** ![mroeling](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/mroeling/32/781_2.png) [@mroeling](https://discourse.aurelia.io/u/mroeling)\
**Post date:** [November 19, 2025, 1:16pm UTC](https://discourse.aurelia.io/t/au1-rendering-promisses-microtask/6542/3 "2025-11-19T13:16:24Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![mroeling](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/mroeling/32/781_2.png) [@mroeling](https://discourse.aurelia.io/u/mroeling)\
**Post date:** [December 10, 2025, 9:44pm UTC](https://discourse.aurelia.io/t/au1-rendering-promisses-microtask/6542/4 "2025-12-10T21:44:04Z")

</div>

Update: all was miraculously fixed with Chrome update 143…