Gutenberg: Deleted tweets store frontend information only

[bahiirwa]

When a tweet is reference via the twitter block. Works like a charm as a point of reference for rich content. However once the owner of the tweet deletes it for whatever reason, the front end information is reserved, while the back end goes kaput - dead white.

To Reproduce
Steps to reproduce the behavior:

1. Reference a tweet in the backend.
   
2. Preview the front end on save or publish
   
3. Delete the tweet from Timeline
   
4. Check back end. The tweet is gone
   
5. On the front end however, the information text is retained minus the formatting.
   

Expected behavior
If the tweet is deleted, let the information block also vanish from content or rather retain the information irregardless if information is deleted on twitter.

Desktop (please complete the following information):

• OS: Windows 10
• Chrome browser
• Version 70.0.3538.102 (Official Build) (64-bit)

It's a great block for building rich content, however, was this the original behavior intention of the block?

[swissspidy]

Frontend output is as expected. Embedded content is cached in the database, that‘s why you still see something in the frontend. But since the tweet doesn‘t exist anymore, Twitter‘s JS can‘t losd all the data for it.

Are there any errors in the editor, i.e. in the database?

[designsimply]

Tested and confirmed that a deleted tweet shows up completely blank in the editor using 4.5.1. No errors show up either in devtools or in the server error.log files.

^{Tested with WordPress 4.9.8 and Gutenberg 4.5.1 with Firefox 63.0.3 on macOS 10.13.6.}

I would consider this an enhancement request and suggest displaying an error message that the content is unreachable (or if you can detect that a tweet really was deleted and want to get really specific, the error could say that directly—though I think a message saying the content is unreachable may suffice).

[designsimply]

Design team: would this issue be a good candidate for the Good First Issue label?

[melchoyce]

@designsimply I think so — a mockup with a core error message inside the block would be a good way to move this forward.

[karmatosed]

The copy could do with some iteration, but here is a suggestion.

[karmatosed]

In this week's design triage this direction was agreed so let's remove the feedback label.