We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recipient_change
recipient_change errors out when compose, that has recipients, gets closed.
gmail-inject.js:8009 Can't find composeRoot for [object Object]
api.dom.compose called with invalid element
Stack trace
gmail-inject.js:8009 Can't find composeRoot for [object Object] Gmail.api.tools.error @ gmail-inject.js:8009 (anonymous) @ gmail-inject.js:9372 setTimeout (async) handler @ gmail-inject.js:9363 (anonymous) @ gmail-inject.js:9321 each @ gmail-inject.js:431 Gmail.api.observe.trigger_dom @ gmail-inject.js:9320 (anonymous) @ gmail-inject.js:9478
gmail-inject.js:8009 api.dom.compose called with invalid element Gmail.api.tools.error @ gmail-inject.js:8009 Gmail.api.dom.compose @ gmail-inject.js:10446 (anonymous) @ gmail-inject.js:9374 setTimeout (async) handler @ gmail-inject.js:9363 (anonymous) @ gmail-inject.js:9321 each @ gmail-inject.js:431 Gmail.api.observe.trigger_dom @ gmail-inject.js:9320 (anonymous) @ gmail-inject.js:9478
I guess it might be some race condition, due to setTimeout, but maybe there is a way to check if compose still exist in setTimeout callback?
setTimeout
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Summary
recipient_change
errors out when compose, that has recipients, gets closed.Steps to reproduce
recipient_change
observergmail-inject.js:8009 Can't find composeRoot for [object Object]
andapi.dom.compose called with invalid element
thrown in consoleStack trace
I guess it might be some race condition, due to
setTimeout
, but maybe there is a way to check if compose still exist insetTimeout
callback?The text was updated successfully, but these errors were encountered: