Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Floating images is broken in large screens #784

Closed
youknowriad opened this issue May 12, 2017 · 4 comments
Closed

Floating images is broken in large screens #784

youknowriad opened this issue May 12, 2017 · 4 comments
Assignees
Labels
[Type] Bug An existing feature does not function as intended
Milestone

Comments

@youknowriad
Copy link
Contributor

Floating image blocks is broken because we the editor wrapper has no max-width to 700px but all the non-floated blocks and non-wide blocks have a max-width of 700px to center these blocks. This causes the floated block to show "outside" the limit of the 700px.

Note: Fixing this can have an impact of full-width images too. Make sure to test this to avoid regressions.

screen shot 2017-05-12 at 17 23 00

cc @jasmussen

@youknowriad youknowriad added the [Type] Bug An existing feature does not function as intended label May 12, 2017
@aduth
Copy link
Member

aduth commented May 12, 2017

Dunno when it was changed, but I encountered this challenge as well with the original implementation of full-width images which tried to avoid putting max-width on the blocks themselves due to this behavior:

#518 (comment)

@jasmussen jasmussen self-assigned this May 15, 2017
@jasmussen
Copy link
Contributor

I have an idea for how to fix this (float the div inside editor-visual-editor__block rather than editor-visual-editor__block itself), which I'm going to try out.

Given the difficulty full width presents for us in the editor, it suggests we probably do want to gate it behind add_theme_support, doesn't it?

@aduth
Copy link
Member

aduth commented May 15, 2017

Given the difficulty full width presents for us in the editor, it suggests we probably do want to gate it behind add_theme_support, doesn't it?

To me it seemed like we'd want this regardless, since otherwise how can we expect the image to be shown correctly on the front-end if the theme doesn't specifically target support for it?

@jasmussen
Copy link
Contributor

This is fixed in master now! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

3 participants