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

Editor view rearranges columns to match mobile ordering #434

Closed
iAmSteveBeatty opened this issue Apr 22, 2020 · 3 comments · Fixed by #435
Closed

Editor view rearranges columns to match mobile ordering #434

iAmSteveBeatty opened this issue Apr 22, 2020 · 3 comments · Fixed by #435
Labels

Comments

@iAmSteveBeatty
Copy link

The editor view of the homepage will unexpectedly shift columns around to match the priority given to the columns for mobile display. For instance, in a 25-50-25 three-column layout, the emphasis is on the center column. So it's reordered for mobile for the center column to be shown first. Until recently, that reordering didn't affect the view in the editor.

Frontend of Ye Olde Newspack.blog:
Screen Shot 2020-04-22 at 2 03 41 PM

Backend editor view:
Screen Shot 2020-04-22 at 2 04 06 PM

I saw the issue happen when I was giving a demo. I added Style 2 from the Newspack Patterns. It wasn't immediate, but somewhere along the line, the editor view shifted. Sorry that I can't immediately reproduce. I'll keep trying to see what triggers it.

@laurelfulford
Copy link
Contributor

I can recreate this -- seems to be related to some CSS class changes in Gutenberg 7.9+ (in 7.8.1 and lower, it previews as expected).

@laurelfulford
Copy link
Contributor

laurelfulford commented Apr 23, 2020

... and now I can't. I can see it on the newspack.blog site though -- going to keep on digging!

Edited to add: newspack.blog is on Gutenberg 7.8.1, so I clearly am looking at the wrong things! 😅

@matticbot
Copy link
Contributor

🎉 This issue has been resolved in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants