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
When using the "js" package for javascript interop I am seeing a weird case where running in Dartium gives a different result to compiled javascript running in Chrome.
Thanks for reporting. We will patch JSON.stringify in dartium to fix this issue.
The dart2js behavior is the correct behavior.
This is part of a class of bugs where we have to try hard to maintain the abstraction that a Dart List looks like a JS Array even though it is not exactly an Array and just looks like an Array as far as any non-native JS APIs can tell.
When using the "js" package for javascript interop I am seeing a weird case where running in Dartium gives a different result to compiled javascript running in Chrome.
Dart SDK version: 1.17.1 linux_x64
pkg/js version: 0.6.0
Example code:
When run in Dartium it produces:
When compiled to javascript and run in Chrome it produces (as expected):
Further experimentation in Dartium reveals that whilst the top-level object appears as this (via a
console.log()
interop):the numbers member itself appears as:
The text was updated successfully, but these errors were encountered: