Make WordPress Core

Opened 2 years ago

Closed 8 months ago

#56929 closed defect (bug) (wontfix)

Twenty Twenty-Three: Sticky posts not visually different than regular posts

Reported by: bgturner's profile bgturner Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.1
Component: Bundled Theme Keywords: reporter-feedback close
Focuses: Cc:

Description

When a sticky post exists, it isn't styled differently than other posts.

The TT3 theme correctly:

  • Puts a sticky post as first in the blog roll
  • Applies the sticky class
  • Also shows the post in the original position, without the sticky class

This was found when doing QA of the 6.1 release candidate:

Replication

  • Install 6.1 and be sure that TT3 is active
  • Import the theme unit test data:
  • Navigate to the posts homepage and note that the sticky post doesn't look visually different than other posts but it does have the correct sticky class
  • Navigate to older posts until you find the sticky post where it should be. Note that it correctly does not have the sticky class

Here's a screenshot to help visualize:

https://i.getf.ly/wbuQpJqn

Attachments (1)

wp6-1-qa-sticky-posts.jpg (1.6 MB) - added by bgturner 2 years ago.

Download all attachments as: .zip

Change History (10)

#1 @sabernhardt
2 years ago

  • Component changed from General to Bundled Theme

#2 @poena
2 years ago

I did not understand in what way this is a bug?
I believe it is a design decision.

#3 @desrosj
2 years ago

  • Keywords reporter-feedback added

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


2 years ago

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


2 years ago

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


2 years ago

#7 @poena
21 months ago

With the introduction of the Custom CSS field in 6.2, the user has easier access to adding their own styles to the .sticky class. Does that solve the issue?

#8 @karmatosed
8 months ago

  • Keywords close added

I feel in agreement with @poena that the custom class field would resolve this. For now, I am going to add the close keyword with a recommendation and we can move it forward into closing should no further feedback happen. Thank you everyone for collaborating on this.

#9 @karmatosed
8 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Thank you everyone, let's follow with closing as it has waiting for feedback.

Note: See TracTickets for help on using tickets.