docs: update Image props #48726
Merged
docs: update Image props #48726
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
styfle
reviewed
Apr 23, 2023
styfle
approved these changes
Apr 23, 2023
|
I fixed the usage to match the next-image-experimental codemod output. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hey! Hope this can help anyone dealing with this in the future.
I'm also using the
TinaMarkdownprovider to generate my MDX and one of the things that I've found helpful so that the image was better handled in the browser was to set position toundefined, as it was the only way to unset it fromabsolute, which was affecting the visual aspect of the page.