Opened 8 months ago
Closed 4 months ago
#61786 closed defect (bug) (worksforme)
6.6.1 Link Styling Issue
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.6 |
Component: | General | Keywords: | reporter-feedback close |
Focuses: | css | Cc: |
Description
I have a few of my clients reporting link styling issues. The styling is fully gone in these instances, not underlined as in the issues before.
Is anyone else reporting this?
Thanks for your help with this.
Change History (3)
#1
@
6 months ago
- Keywords reporter-feedback added; has-dev-note removed
- Milestone changed from Awaiting Review to 6.6.3
- Version changed from 6.6.1 to 6.6
#2
@
5 months ago
- Keywords close added
- Milestone changed from 6.6.3 to Awaiting Review
This can't move forward without additional reporter feedback.
With 6.7 RC1 due out any moment and no plans to ship a 6.6.3 at this time, I'm going to punt this.
Adding the close
suggestion to circle back in a few weeks to check for additional details.
#3
@
4 months ago
- Milestone Awaiting Review deleted
- Resolution set to worksforme
- Status changed from new to closed
It looks like we haven't had any further details on this. I am going to proceed with the recommendation to close tentatively. We can always reopen if further information surfaces
Unless mistaken, I am unable to replicate anything close to this; what we could do with knowing in order to reopen would be more steps and also that requested testing in the latest version.
Thank you, everyone, for now closing this with the status 'works for me'.
Hello @nerdnestmedia,
Welcome to WordPress Core's Trac. Thank you reporting the issue.
I'm curious if the issue has already been resolved. Since this ticket, CSS specificity and style fixes shipped:
Did upgrading to 6.6.2 resolve the issue?
If yes, then this ticket can be closed.
If no, what's next?
If it's not a known issue in that tracker, then it needs to be reported upstream in Gutenberg as that's where it'll be investigated and resolved. You can open an issue here.
Tip: Sharing screenshots and step-by-step instructions (i.e. on how to reproduce the issue) helps contributors get started.
For now, I'll move this ticket into 6.6.3 for tracking and awareness.