You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
We have an application that uses core-signals for a couple of custom events. With Dartium/Chromium.app for SDK 1.12.2 and earlier, the signals work just fine. But, as soon as we upgrade to Dartium/Chromium.app for SDK 1.13 or above, they no longer work.
We really want to upgrade to the current release 1.13.2 so that we can use the new @js() and JS-Interop features, but we also need these custom core-signals working.
We have an application that uses core-signals for a couple of custom events. With Dartium/Chromium.app for SDK 1.12.2 and earlier, the signals work just fine. But, as soon as we upgrade to Dartium/Chromium.app for SDK 1.13 or above, they no longer work.
We really want to upgrade to the current release 1.13.2 so that we can use the new @js() and JS-Interop features, but we also need these custom core-signals working.
I have posted a test program that is able to illustrate the problem at https://github.com/gtaylor20/incoming.git
The text was updated successfully, but these errors were encountered: