Publicado el Deja un comentario

Sticky

This is a sticky post.

There are a few things to verify:

  • The sticky post should be distinctly recognizable in some way in comparison to normal posts. You can style the .sticky class if you are using the post_class() function to generate your post classes, which is a best practice.
  • They should show at the very top of the blog index page, even though they could be several posts back chronologically.
  • They should still show up again in their chronologically correct postion in time, but without the sticky indicator.
  • If you have a plugin or widget that lists popular posts or comments, make sure that this sticky post is not always at the top of those lists unless it really is popular.
Publicado el Deja un comentario

Super/Duper/Long/NonBreaking/Path/Name/To/A/File/That/Is/Way/Deep/Down/In/Some/Mysterious/Remote/Desolate/Part/Of/The/Operating/System/To/A/File/That/Just/So/Happens/To/Be/Strangely/Named/Supercalifragilisticexpialidocious.txt

Super/Duper/Long/NonBreaking/Path/Name/To/A/File/That/Is/Way/Deep/Down/In/Some/Mysterious/Remote/Desolate/Part/Of/The/Operating/System/To/A/File/That/Just/So/Happens/To/Be/Strangely/Named/Supercalifragilisticexpialidocious.txt

A few things to check for:

  • Non-breaking text in the title, content, and comments should have no adverse effects on layout or functionality.
  • Check the browser window / tab title.
  • If you are a plugin or widget developer, check that this text does not break anything.

The following CSS properties will help you support non-breaking text.

-ms-word-wrap: break-word;
word-wrap: break-word;
Publicado el Deja un comentario

Comments

This post tests comments in the following ways.

  • Threaded comments up to 10 levels deep
  • Paginated comments (set Settings > Discussion > Break comments into pages to 5 top level comments per page)
  • Comment markup / formatting
  • Comment images
  • Comment videos
  • Author comments
  • Gravatars and default fallbacks