Forgot-to-Render check for Fastmail #318
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Adam,
I was tired of forgetting to render my Markdown emails in Fastmail, and decided to see if I could extend your excellent forgot-to-render check to the Fastmail compose interface. (Issue #317)
It almost-but-not-quite works in this initial PR. The event listeners are set up and work properly, both for clicking the Send button and for using the send hotkeys (which are the same in Fastmail as Gmail). The script correctly catches and prevents sending an unrendered email when I click Send. But if I use the ⌘+Enter hotkey, the email is sent and then Markdown Here opens the forgot to render prompt. It seems that
eatEvent()
is not eating the hotkey send action.I have no prior experience with JavaScript, so I thought I would stop here and ask you for guidance. In fact, this is also my first submission to an open source project.
Michael