-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove Legacy Admin Layout #2127
Conversation
We want to remove the legacy layout of the admin and this is one of the few remaining pieces that relied on a specficically named element being available.
This is a simplification of this admin interface in order to prepare to switch the admin to a responsive layout. This optimization had a weird side effect in that it fully replaced the content on the page instead of loading the form in, say, a modal. This would mean that hitting "Cancel" on the form would actually trigger a page load instead of just removing the form from the page.
Looks like the order page is borked. Will fix. |
Fixed the order page. The bug was from a few releases ago but it went unnoticed because none of the pages using the new layout also had a sidebar. |
6bf36c0
to
318e9fd
Compare
This commit removes the conditional in the admin layout to fallback to the legacy layout. By moving all pages to the new layout we get (relative) responsiveness for free. Since we've transitioned all of the `col-X` classes to use Bootstrap we should no longer have any fixed-width grid elements.
In a previous commit the `make-row()` mixin was removed from `.content` causing the sidebar to not have enough room on the right side of the screen. Now that we're moving to the new layout full-time we can just add the necessary Bootstrap classes directly to the markup. Special note: we're explicitly not using the `.container` class because we don't want to use Bootstrap's built-in breakpoints.
If stores are still using these classnames they can import this file directly into their project but we made the move to Bootstrap over a year ago and it's time to remove the confusion of having two grid systems.
318e9fd
to
38fb6b8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I haven't clicked through all the pages but if anything comes up we'll still have a fair chunk of time to fix it before next release
Fix the vertical position of the content sidebar for layouts having tabs and having none.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Was about time
I added a fix for the vertical position of the sidebar. Sent you a PR @graygilmore
Adjust sidebar to new admin layout
That's great! Thank you! Happy to see |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff!
This removes the legacy admin layout and gives us half-decent responsiveness due to the nature of using Bootstrap classes. Previously, using
.container
our content would sit at a maximum width of960px
and shrink down to awkward sizes depending on the browser size.This PR also finally removes the Skeleton Grid CSS from the admin. If stores are still relying on it in order to make overrides to their stores they can pull that CSS directly into their app.
Oooo, fancy!
Before at awkward breakpoint
After