Skip to content

Conversation

@GuySartorelli
Copy link
Member

2 commits intentionally - but okay to squash if you want to. Just make sure to give the squash commit a sensible name.

Issue


- [Features and enhancements](#features-and-enhancements)
- [Accessibility improvements](#accessibility-improvements)
- [Unsaved changes indicator](#unsaved-changes-indicator)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was missing though the section was added. Figured I may as well just add it in rather than spawning a whole separate issue just for this

Copy link
Member Author

@GuySartorelli GuySartorelli Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically the Move button would never be blue like this, and the Content button would.... I've cheated a bit to make it less confusing 😅

Copy link
Member

@emteknetnz emteknetnz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge conflict to resolve

@GuySartorelli
Copy link
Member Author

Rebased

@GuySartorelli GuySartorelli force-pushed the pulls/6/move-blocks branch 2 times, most recently from 3c5fc3e to 32fe085 Compare December 7, 2025 21:14
@emteknetnz emteknetnz merged commit cbcda8e into silverstripe:6 Dec 8, 2025
3 checks passed
@emteknetnz emteknetnz deleted the pulls/6/move-blocks branch December 8, 2025 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants