#61437 closed defect (bug) (fixed)
Twenty Nineteen: Button block Appearance setting (font-weight) is not working.
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.7 | Priority: | normal |
Severity: | minor | Version: | |
Component: | Bundled Theme | Keywords: | has-patch changes-requested commit |
Focuses: | css | Cc: |
Description
In Twenty Nineteen, Button Block's Appearance setting option is not working on both frontend and backend.
Steps to reproduce the issue -
- Add a Button Block to the editor
- Add some text to the button
- Go to block setting and enable appearance setting
- Select Any Appearance option.
Its Not showing any font-weight added to text in button block
Attachments (3)
Change History (11)
This ticket was mentioned in PR #6831 on WordPress/wordpress-develop by @sabernhardt.
9 months ago
#1
- Keywords has-patch added
Inherits custom font weight and text decoration settings, both on the front end and within the editor.
#2
@
9 months ago
- Focuses css added
- Keywords needs-testing added
- Milestone changed from Awaiting Review to 6.7
The default font-weight
needs to remain bold, while adding support for other weights.
The custom text-decoration
would need an adjustment too, at least on the front end (I updated both front end and editor styles in PR 6831).
@
9 months ago
sample blocks for default styles plus custom font weight and text decoration settings
#3
@
9 months ago
- Keywords changes-requested added
- Milestone changed from 6.7 to Future Release
I think we need to have some adjustments made for this based on the last comment so for now moving this out into future release.
#5
@
8 months ago
- Milestone changed from Future Release to 6.7
- Owner set to karmatosed
- Status changed from new to assigned
Let's see what we can do about testing and moving this one on. Putting it into the next release to do that.
#6
@
8 months ago
- Keywords commit added
In testing I can confirm that this resolves with the patch. Thank you everyone. I will now be adding commit to progress this.
@sabernhardt commented on PR #6831:
6 months ago
#8
Committed in r58851
After applying this patch , this issue is resolved