Twenty Fifteen: fix Table block's Stripes style

[nidhidhandhukiya]

Steps to reproduce the issue :-

1. Activate Twenty Fifteen theme.
2. Choose Table block.
3. Choose stripes from style.

Now check both the side editor end front end.
Design not looks same both the side it should be same in both the side.

I have attached video for better understanding.
Video URL :-​https://share.cleanshot.com/sFxg16JqbnqprL5T3hNd

[sabernhardt]

adding .is-style-stripes class to cell border styles to prevent block styles from overriding theme, removing bottom border from block (figure) element

[sabernhardt]

I did not add a background color because that is an iframe editor issue (GB57176). If that would be fixed in individual themes, it would be better to assign the background color to .editor-styles-wrapper for the whole canvas.

The block styles for Stripes were more specific than the theme's, so I added the extra class (and kept the original selectors). The patch also removes the bottom border from the block, but only if it is a figure (the classes were on the table in WordPress 5.0 but moved to the figure by 5.3).

[karmatosed]

Let's see about getting this into the next version. I have updated the milestone.

[hmbashar]

Test Report

Patch tested: 60424.patch and also I've tested this 60424.2.patch

Environment

• WordPress: 6.6-alpha-57778-src
• PHP: 8.3.7
• Server: nginx/1.25.4
• Database: mysqli (Server: 8.3.0 / Client: mysqlnd 8.3.7)
• Browser: Chrome 125.0.0.0
• OS: macOS
• Theme: Twenty Fifteen 3.7
• MU Plugins: None activated
• Plugins:
  • FakerPress 0.6.6
  • Test Reports 1.1.0

Actual Results

1. there is no changed

Screenshots

Editor Before Patch	Editor After Patch

Frontend Before Patch	Frontend After Patch

[hmbashar]

Hello @nidhidhandhukiya,

I've tested a few tickets submitted by you. Your instructions are good and easy to understand for testing. However, I've noticed that you're sharing video instructions for better understanding. Unfortunately, I can't watch any of your videos from the links you provided. It seems the links expire a few days after submission.

Therefore, I request that when you share your videos, please upload them as attachments or ensure the video URLs remain active for testing and viewing.

Best Regards
Bashar

[karmatosed]

@hmbashar when you say no change do you mean this is passed in testing because I am trying to be clear that you are happy as I do see visual differences.

[hmbashar]

Replying to karmatosed:

@hmbashar when you say no change do you mean this is passed in testing because I am trying to be clear that you are happy as I do see visual differences.

I didn't notice any changes before or after applying the patch, so perhaps the patch didn't solve the issue. Maybe more work is needed with the patch.

https://core.trac.wordpress.org/ticket/60424

[audrasjb]

After applying patch: doesn't work

[audrasjb]

I can confirm the proposed patch doesn't work in the editor.

[sabernhardt]

I think the main problem in testing this now is that the theme's gray table border #eaeaea and the Stripes background #f0f0f0 nearly match the admin CSS gray background #f0f0f1, but the patch probably could be improved anyway. When the iframe editor is fixed, this should be a little easier.

[audrasjb]

The previous patch didn't work because of the grey background used in T15.

I suggested another approach in the above PR. See screenshot below.

[audrasjb]

After applying new PR: "even" rows are now white :)

[audrasjb]

@sabernhardt ah yes the iframed editor could make it easier to fix it though.
Then even if my solution works great, I'm not sure it's worth fixing this issue in 6.6 you're right.

[sabernhardt]

Moving this to 6.7 instead of Future

[ugyensupport]

@sabernhardt @karmatosed I checked and I don't see any difference between the frontend and backends with table stripe with T15 theme. Is the changes already updated in WordPress 6.6.1

[karmatosed]

I also can no longer see this as an issue with the theme so I am going to recommend we close this.

[karmatosed]

Based on the lack of being able to replicate and no further updates I am going to close this. If anyone is still able to replicate the issue we can always open again or have a new ticket. Thank you everyone for your collaboration on this.