Make interchangeable with Image component and intrinsic img tag #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
June 28, 2019 15:06
Add notice about HTML formatting for the content of confirmation dialog.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
So far, usages
<Image>component and<img>intrinsic HTML tag had not a consistency.<Blocks>,<Image>and<img>have a same meaning (Image block).<Section>block, only<Image>component can use as an accessory. It would raise an errorUnknown HTML-like element: imgif you try to use<img>tag.<Context>block, only<img>component can use as an image element. It would be generated a strange text[Object object]if you try to use<Image>component.By this PR,
<Image>component and<img>element would make interchangeable in any components.