Full width images when regardless of alignment up to 768px, css, mini… #1630
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
benlk
added
type: improvement
status: needs review
community contribution
category: gutenberg
|
Closing in favor of #1671 |
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.
…fied, mixin
#1611
I shot for the 767px range. Are there any tests I can perform over and above viewing the content types in the browsers and provide screenshots?
Is there any accommodation I need to make for Gutenberg vs Classic perhaps?
I've performed some viewing tests locally with images aligned left and right throughout a post and across the post layouts and the results are positive.
Is the CSS / LESS in the right file/place?
@benlk