-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Closed
flutter/engine
#55847Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.team-webOwned by Web platform teamOwned by Web platform team
Description
When a Flutter web engine promise is rejected for whatever reason, it is rendered to the JS Console as a Warning, which makes it harder to see around other browser notifications, for example:
The whole explanation for "Uncaught (in promise)" is right above it, but hard to spot because it looks like every other browser warning in the console.
We do this here:
printWarning is defined here:
I think we should console.error the error messages of those promises, so they show up closer to what they look like in JS:

Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: tech-debtTechnical debt, code quality, testing, etc.Technical debt, code quality, testing, etc.engineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.team-webOwned by Web platform teamOwned by Web platform team