Opened 2 years ago
Closed 2 years ago
#56121 closed defect (bug) (reported-upstream)
Twenty Twenty Two: Button width issue occurs on front end side
Reported by: | multidots1896 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.0 |
Component: | Bundled Theme | Keywords: | |
Focuses: | Cc: |
Description
Twenty Twenty Two theme Post comments form block having button width issue occur on front end side.
Steps to replicate:
1: Twenty Twenty Two
2: Add Post comments form block
3: Publish post and check the form on front side.
Attachments (1)
Change History (7)
#1
@
2 years ago
- Summary changed from In Twenty Twenty Two theme button issue occur on front end side to Twenty Twenty Two: Button width issue occurs on front end side
#2
follow-up:
↓ 3
@
2 years ago
- Keywords reporter-feedback added
@multidots1896 Does this only occur in Twenty Twenty-Two, or in all block themes?
If the issue is only in Twenty Twenty-Two, then this change should likely be made directly in Twenty Twenty-Two.
If the issue is with the Post Comments Form block in general, I think this change is needed on the Gutenberg side, in this file.
#3
in reply to:
↑ 2
@
2 years ago
Hi @costdev
I have generate pull request on gutenberg repository here i have added link of my pull request
https://github.com/WordPress/gutenberg/pull/42179.
#4
follow-up:
↓ 5
@
2 years ago
Hi @multidots1896, thanks!
Can you also create a new issue on the Gutenberg repository with a description of the problem and commemt here with a link to the issue? This will keep the issue and its solution in one place, and we can then close this Trac ticket as reported-upstream
.
#5
in reply to:
↑ 4
@
2 years ago
Hi @costdev
I have this issue on gutenberg repo and here is link https://github.com/WordPress/gutenberg/issues/42184
Thanks
#6
@
2 years ago
- Keywords has-patch reporter-feedback removed
- Milestone Awaiting Review deleted
- Resolution set to reported-upstream
- Status changed from assigned to closed
Thanks @multidots1896!
I'll close this ticket as reported-upstream
so that folks can focus the discussion/solution on the issue linked above.
added patch