Twenty Sixteen: barely visible bold text in 'blockquote'

[gaelbonithon]

The current code is

blockquote strong,
blockquote b {
  font-weight: 400;
}

, which makes very little difference. It seems to me that this would be better:

blockquote strong,
blockquote b {
  font-weight: bold;
}

Trac ticket: https://core.trac.wordpress.org/ticket/65108

## Use of AI Tools

[JayDeep Nimavat]

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/11623

Environment

• WordPress: 7.0-RC2-62242
• PHP: 8.3.30
• Server: nginx/1.26.1
• Database: mysqli (Server: 8.0.35 / Client: mysqlnd 8.3.30)
• Browser: Chrome 146.0.0.0
• OS: macOS
• Theme: Twenty Sixteen 3.7
• MU Plugins: None activated
• Plugins:
  • AI 0.7.0
  • Test Reports 1.2.1
  • WordPress Beta Tester 4.0.0
  • WPMozo Blocks and Addons 1.7.0
  • WPMozo Blocks and Addons Pro 1.0.0

Actual Results

1. ✅ Issue resolved with patch.

Additional Notes

• Any additional details worth mentioning.

Supplemental Artifacts

Before: ​https://ibb.co/qL9zhk4P
After: ​https://ibb.co/1fr8tsyJ

[sabernhardt]

Like the normal font-style for em (#65107), the normal font-weight has been part of Twenty Sixteen since ​initial commit.

However, I do not understand the reason for reducing the font-weight for strong elements inside a blockquote.

If a change is appropriate now, I would prefer removing the ruleset instead of editing the value.

[sabernhardt]

Quote blocks with em and strong elements within both the paragraph and the citation

[gaelbonithon]

Replying to sabernhardt:

Like the normal font-style for em (#65107), the normal font-weight has been part of Twenty Sixteen since ​initial commit.

However, I do not understand the reason for reducing the font-weight for strong elements inside a blockquote.

If a change is appropriate now, I would prefer removing the ruleset instead of editing the value.

Patch updated. For the editor, I took inspiration from your recommendations in #65107: I'm not sure if this is the best way to do it, but it works…

[darshitrajyaguru97]

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch Tested

​https://github.com/WordPress/wordpress-develop/pull/11623

Environment

• WordPress: 7.0-RC2-62242
• PHP: 8.3.30
• Server: nginx
• Database: mysqli
• Browser: Chrome
• OS: Windows
• Theme: Twenty Sixteen
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.2.1
  • WordPress Beta Tester 4.0.0

Steps to Reproduce

1. Install and set up WordPress with the above environment.
2. Attempt to reproduce the reported issue on the unpatched version.
3. Apply the patch from the PR.
4. Re-test the same scenario.

Actual Results

• ✅ Issue resolved with patch.
• No unexpected errors or regressions observed.

Expected Results

• The issue should be resolved after applying the patch. ✅

[poena]

Hi
I don't feel strongly either way, pinging @iamtakashi @karmatosed as it is their theme, in case they have any opinions about the design of the quotes.

[adrianduffell]

Moving this ticket to a future release, as it looks unlikely to be completed before the upcoming 7.1 beta.

[sabernhardt]

This probably should have agreement from one of the theme authors.