Make WordPress Core

Opened 9 months ago

Closed 7 months ago

Last modified 7 months ago

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

WP 6.8 Core added a Button block CSS property width of 100% rendering some buttons the full width of the browser.

Reported by: ceenee's profile ceenee Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.8
Component: Editor Keywords: needs-test-info
Focuses: Cc:

Description

Hi,

This is related to a support forum bug with the release of WP 6.8 as described here: https://wordpress.org/support/topic/6-8-adds-width-of-100-to-wp-block-button__link/#post-18441988

The wp-block-button__link class on the Button block now has a width of 100% in WordPress Core. This has made several existing buttons, independent of theme, stretch the entire width of the browser after upgrading to WP 6.8 from WP 6.7.x. The width of 100% is not in WP 6.7.x.

Thanks!

Change History (6)

#1 @abcd95
9 months ago

  • Keywords needs-testing-info added

Hi @ceenee, Thanks for bringing this up.

I've been trying to reproduce the issue described, which is the addition of width: 100% to the buttons 6.8 onwards, but I did not see any anomaly as mentioned.

I tested this using the following setup :

  • Used a default theme (Twenty Twenty-Four) with no active plugins
  • Created a new post and added a standard Button block with default settings (no changes to alignment, justification, or width options in the block inspector)
  • Added a couple paragraphs in between
  • Viewed the post on the front-end

I did this with both 6.7.2 and 6.8 and didn't notice any significant deviations.

Could you provide some steps for reproduction or maybe screenshots if possible?

#2 @sabernhardt
8 months ago

  • Component changed from General to Editor
  • Milestone changed from Awaiting Review to 6.8.2
  • GB64770 added width: 100%.
  • Then GB69637 used width: auto the fix the comment form button instead of removing the 100%.

#3 @wildworks
8 months ago

Thanks for the report.

The approach taken in GB 64770 may have been a bit too aggressive. I submitted GB 70054 to solve this ticket.

This ticket was mentioned in Slack in #core by joedolson. View the logs.


8 months ago

#5 @joemcgill
8 months ago

  • Keywords needs-test-info added; needs-testing-info removed

#6 @wildworks
7 months ago

  • Milestone 6.8.2 deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

This issue was fixed by GB70054.

Last edited 7 months ago by wildworks (previous) (diff)
Note: See TracTickets for help on using tickets.