Make WordPress Core

Opened 3 years ago

Closed 4 weeks ago

Last modified 2 weeks ago

#58744 closed defect (bug) (reported-upstream)

Width issue while creating sync pattern using already existed pattern

Reported by: labunchemjong's profile labunchemjong Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.3
Component: General Keywords:
Focuses: Cc:

Description

WordPress Version: Development version (6.3-beta3)
Theme: Twenty Twenty-Three
Browser: Google Chrome Version 114.0.5735.198 (Official Build) (arm64)


Follow this step to create this issue.

  • Create a new post
  • Add any of the existing pattern into the post
  • Change that pattern to sync pattern

Now, the main issue is:
If the pattern was fullwidth style by default, when you change that pattern to sync type pattern; that pattern will change to boxed style. But the view in frontend will be in it's original style i.e. if it was fullwidth, it will be fullwidth in frontend.

Expected fix:
After we change the pattern to sync pattern, the pattern style should remain same in both frontend and backend.

Change History (5)

#1 @dalemugford
3 years ago

I can replicate this— seeing the same issue. I tried editing the synced pattern to ensure it's full-width— but there's no way to do that on a group in the synced pattern editor.

#2 @r1k0
4 weeks ago

  • Keywords needs-testing removed

Reproduction Report

Description

This report validates whether the issue can be reproduced.

Environment

  • WordPress: 6.9
  • PHP: 8.3.30
  • Server: PHP.wasm
  • Database: WP_SQLite_Driver (Server: 8.0.38 / Client: 3.51.0)
  • Browser: Chrome 144.0.0.0
  • OS: Linux
  • Theme: Twenty Twenty-Three 1.6
  • MU Plugins: None activated
  • Plugins:
    • Test Reports 1.2.1

Actual Results

  1. ❌ Error condition doesn't occur (not reproducible).

Additional Notes

Supplemental Artifacts

Screencast:
https://files.catbox.moe/z4uve8.webm

#3 @r1k0
4 weeks ago

  • Resolution set to reported-upstream
  • Status changed from assigned to closed

@labunchemjong Thank you for the ticket.
I will close this ticket. See the report above for reasons why.

Last edited 4 weeks ago by r1k0 (previous) (diff)

#4 @sabernhardt
2 weeks ago

  • Keywords needs-patch removed
  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.