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.

Sign up for GitHub

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

Jump to bottom

Live Preview fix for WP 6.6 (backwards compatible) #599

Merged
merged 1 commit into from
Jul 18, 2024
Merged

Live Preview fix for WP 6.6 (backwards compatible) #599

merged 1 commit into from
Jul 18, 2024

Conversation

arunshenoy99
Copy link
Member

Proposed changes

Type of Change

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

  • I have read the CONTRIBUTING doc
  • I have viewed my change in a web-browser
  • Linting and tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@arunshenoy99 arunshenoy99 added the Code Review The PR is in Code Review label Jul 18, 2024
@arunshenoy99 arunshenoy99 added Ready to merge The Code Review and QA is done and it can be merged. and removed Code Review The PR is in Code Review labels Jul 18, 2024
@arunshenoy99 arunshenoy99 merged commit 778085d into trunk Jul 18, 2024
5 of 6 checks passed
@arunshenoy99 arunshenoy99 deleted the fix/wp-6.6save-and-continue branch July 18, 2024 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@diwanshuster diwanshuster diwanshuster approved these changes

Assignees
No one assigned
Labels
Ready to merge The Code Review and QA is done and it can be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@arunshenoy99 @diwanshuster