New post summary designs on site home pages and greatest hits now; everywhere else eventually

Question

Update 3 - 2022-02-01

We've rolled out another small set of changes + bugfixes. The largest change was that we removed the yellow from watched tags entirely, leaving just the new "watched" icon.

We've also added this answer where we lay out our next steps.

Update 2 - 2022-01-27

We've pushed some layout changes live. When reviewing the given feedback as a whole, we've identified a few major themes:

• Stats are too hard to pick apart, "votes" in particular
• New watched/ignored states are not bright enough/too bright (respectively) and cause too much trailing whitespace

We've made the following changes to alleviate these issues:

• Bumped up the size of stats
• Gave more visible weight to "votes"
• Gave less visible weight to "supernova" view counts by removing the :fire: icon
• Removed "watched" state label, restored the yellow background and adding highlighting/icon to the individual tags that are causing the watched status
• Removed "ignored" state label, added icon to the individual tags that are causing the ignored state

This latest set of changes also includes a number of bug fixes. We're still discussing how to better improve this component. There is still some extra whitespace at the end when there is no body excerpt and a bounty exists on the post (though, this is generally still less trailing whitespace than the current design on /questions, which has a body excerpt). Thank you for your continued feedback.

Update 1 - 2022-01-25

Most of the reported bugs have been squashed. We're currently gathering together all the discussion and feature-request feedback items to decide how we want to alter the design. Thank you everyone for your feedback.

---

Original Post

tl;dr

We’re starting a rollout of the new post summary design to many existing screens, starting with greatest hits. This will be a slow rollout, with only one set of related screens changing at a time.

What we’re shipping now

We’ve built a new component to replace the existing post summary implementation. We aimed for ~100% data compatibility with this implementation so that users are not losing any statistics or features. That being said, our desire to leave the existing data intact as much as possible has led to sub-optimal layouts in a few uncommon scenarios, particularly for the display of community wiki posts. Work on these experiences is ongoing and will improve over time.

For the initial announcement, we’ve migrated /questions/greatest-hits to use the new implementation. This way, users can have a tangible example they can use today, before we roll out the design to more and more screens. Why did we choose greatest hits to start with? It was an ideal screen for many reasons:

• Entirely standalone - no dependencies on other screens/processes and not depended on
• Low user impact - low traffic, infrequently referenced and not terribly well known (even among employees!)
• Uses the exact same component code and layout as /questions - users can see this as a very close preview for what will be shipping there later on
• In disrepair - the screen was already showing some signs of neglect and really needed some love <3

Before

After

What we’re shipping later

In addition to greatest hits, we’re aiming to roll this new design out site-wide. The areas we’re concentrating on first are the main areas of the site that still have mobile-only layouts. As we remove our final mobile views, we need to ensure that the remaining responsive views actually look good on smaller screens. More specifically, the following high traffic views are next on our list:

• / (home / recent questions) - our “QuestionMini” layout
• /questions/* (question list, list by tag, search, etc) - our “QuestionSummary” layout
  

Work on these screens has progressed fairly far already due to most of the necessary work being in the creation and implementation of the underlying component. However, we’ve decided to hold off on the rollout until after the community has had an opportunity for processing the design changes and to offer us feedback.

Eventually, everything will be the new post-summary design, but it may be some time before the changes reach the long tail of our many different views.

Where we are currently using this design

Despite my claims above that this is a “new” design, we’ve been using it in a number of places across the site for quite some time. A (non-inclusive) list of places that are already using the post-summary design:

• Many various places in Teams and Collectives
• Review queue tasks
• New user activity screens, such as bookmarks and questions

Why we’re making these changes

Our current designs have withstood the test of time, but they fall short in many areas:

1. We generally assume 3 items of metadata: score, answers, and views. If we want to add new entries for e.g. bookmarks or revisions, it can be difficult to create a consistent layout in a list of questions.
2. Inconsistencies in implementation have led to several different layouts across the site. When gathering requirements for a unified post summary component, we found at least 5 (five!) different layouts.
3. Scaling the design is tricky, both in window size and adding features and functionality. We need to support all sorts of metadata on all sorts of devices.
4. Our post summaries were only designed to support questions (and answers, kinda). We need to be able to display various content types in single lists. For example, in a list of notifications, we may want to present an article next to a question.
5. We have no unified place to put an action menu.

Our new post-summary design solves these problems while supporting future features we’re exploring. Some features we’re looking forward to are:

1. An arbitrary, scalable number of stats
2. Multiple different content types
3. A consistent location for post actions
4. Scalable excerpts
5. Responsive layouts
6. A single consistent layout regardless of what data is included

How this component was designed

An early version of this component first appeared in Stack Overflow for Teams in a feature called For You. For You is a rich list of notifications that include questions, answers, and articles.

The existing designs were desirable for familiarity, but just weren’t well suited for the task. After the initial proposal and some iterations with our team of designers, the new post summary design was ready for user testing.

User testing was run with ~170 recently active users against 5 different versions of the post summary design (two of those being existing designs). The chosen design performed better than the existing designs in some metrics (including readability) and never worse on the remaining metrics (including familiarity, data absorption).

After this new design tested well, the design systems team gathered further requirements from across the organization and built it out as an official Stacks component. If you’re technically inclined, you can see some of the iterations in various open source pull requests.

If you’re familiar with the design tool Figma, feel free to check out some explorations prior to us moving into code.

FAQ

Q: What if I find a bug/regression?
A: Report it as an answer to this post - one bug per answer please. If you’re feeling charitable, add a [tag:bug] tag to the top of your post so we can more easily find it.

Q: What if I have constructive feedback, but it isn’t a bug?
A: We’d like to hear it! Add it as an answer on this post. As above, you can add a [tag:discussion] tag to the top of the post as well.

Q: When will FAVORITE_SCREEN be migrated to use this new design?
A: 6-8 weeks

Answer 1

discussion

As also said in this answer the format of the author is a mess.

What I see when I read it is:

• The author
• Reputation! (in bold)
• and some more small print

You could (should) format it more like this instead

Furthermore, I don't see why the reputation is the only bold text there -- it would be just as readable without being bold (and its being bold at the moment is in my opinion chartjunk).

Answer 2

discussion

Not Tested Properly

Where we are currently using this design

Despite my claims above that this is a “new” design, we’ve been using it in a number of places across the site for quite some time. A (non-inclusive) list of places that are already using the post-summary design:

Many various places in Teams and Collectives
Review queue tasks
New user activity screens, such as bookmarks and questions

This is the core of the problem. It was tested in the wrong places:

• Teams - The people who use Teams are the people who have to use Teams. They are not the bulk of the users. I have no statistics, but I am pretty confident of that.
• Collectives - Too new, too small, irrelevant to the vast majority of users.
• Review Queues - Those are a different animal altogether. Most users, even those who have the reputation to do so, don't bother with review queues, and if they do then they are concentrating on a specific task (reviewing) and not scanning a list of questions.
• New user activity screens - Again, not relevant to most of the users, most of the time.

The way to test a change like this is to identify a select group of users (e.g., random selection of users above a certain level of reputation and/or activity, ping them via Inbox messages), get voluntary agreement to test for a reasonable amount of time and then get real-world feedback. This is too dramatic a change to test via random any-page-could-be-old-or-new A/B testing, and it is also too dramatic to just drop on everyone without proper testing.

Answer 3

support status-completed

What's the threshold for showing the 🔥 symbol before the number of views? From the screenshots, I guess it's 100k – is that a global constant or will it differ per site? On many smaller sites, it's rather hard to reach that amount of views.

Answer 4

discussion

Custom Styles

I'm using the Stylus browser extension to customise CSS rules for URLs matching https://(.+\.)?stackoverflow.com/(questions)?(\?tab=.*)?

Also uploaded to Userstyles.org and Stack Apps.

Features:

• Hides the user avatar
• Hides the view count (personal choice, I never found it useful)
• Hides the checkmark in the accepted answer box. This was throwing out alignment and is not needed due to the box's solid background colour
• Arranges the score and answer count into a grid to look more like it did before this change.
• Reverts watched tags back to how they looked previously

/** Container **/

.s-post-summary {
  padding-left: 8px;
}

/** Stats grid **/

.s-post-summary .s-post-summary--stats {
  display: grid;
  width: unset;
  grid-template-areas:
    "score answers views"
    ". bounty ."
    ;
  grid-template-columns: repeat(2, 1fr); /* change to 3 for views */
  column-gap: var(--s-post-summary-stats-gap);
  row-gap: var(--s-post-summary-stats-gap);
  align-content: start;
  align-items: center;
}

.s-post-summary--stats .s-post-summary--stats-item,
.s-post-summary--stats .s-post-summary--stats-item.has-answers {
  display: flex;
  flex-direction: column;
  margin: 0;
  padding: 4px;
  width: 60px;
}

/** State grid items **/

.s-post-summary--stats .s-post-summary--stats-item .s-post-summary--stats-item-number {
  font-size: larger;
  margin-right: 0 !important;
}

.s-post-summary--stats .s-post-summary--stats-item:nth-child(1) {
  grid-area: score;
}

.s-post-summary--stats .s-post-summary--stats-item:nth-child(2) {
  grid-area: answers;
}

.s-post-summary--stats .s-post-summary--stats-item:nth-child(3) {
  grid-area: views;
  display: none; /* remove for views */
}

.s-post-summary--stats-item.has-bounty {
  grid-area: bounty;
}

.s-post-summary--stats .s-post-summary--stats-item.s-post-summary--stats-item__emphasized {
  color: var(--fc-light);
}

/** Tags **/

.post-tag.s-tag__watched {
  padding-left: 0.5em;
}

.post-tag.s-tag__watched:before {
  content: none;
}

/** Hide unwanted elements **/
.s-post-summary--stats .s-post-summary--stats-item.has-accepted-answer .iconCheckmarkSm,
.s-post-summary--meta .s-avatar {
  display: none;
}

TODO:

• Handle bounty badge (though, to be honest, it doesn't look too bad)

• Align user and timestamp (again, I think this looks OK)

Answer 5

bug status-review

Mobile: multiline titles have a larger font size.

Answer 6

discussion status-bydesign

The removal of the badge count information next to a user's avatar and reputation was intentional. While that information was not of critical importance by any means, I did find it informative and interesting.

Can you speak to the reasoning behind removing it, since it doesn't seem to be a matter of needing that space for layout purposes (overflowing the width parameter there bumps that whole line down to a new line anyway)?

Answer 7

discussion

This is a response specifically to update 2. You mention as a major issue that votes are too hard to see and write that as a response you bumped the size there. From this I get the impression that there is still a huge disconnect between what some of us are considering a critical fault in the new design and what SE is perceiving as our complaint.

The problem isn't just that the score is a point or two too small in font size. I reduced the font size for the numbers in the current /questions view to the size of the new design, and this still was much more readable than the new design. The size isn't the main issue, the layout is. The old layout clearly separates the number from the description and it's very easy to quickly scan the values. The new design puts the number as part of the text with its description.

I don't think you can fix the fundamental issue while keeping the new design of the statistics area.

Answer 8

bug status-completed

Keyboard navigation doesn't work. Pressing j/k should move down/up in the list of posts, and Enter should click through to the post. This worked in the old style views, but doesn't work on the redesigned views.

Answer 9

feature-request status-review

Word-breaks in titles make it difficult to read quickly

Some words in the titles of questions on the Home page and Questions page are now broken across two lines with a hyphen. This is what I’m seeing on Academia SE’s Home page on mobile (in the responsive design):

The titles in the above image appear as follows:

• is there a way to include an updated paper cita-
  tion link in excel

• Should professors use the f*** word during lec-
  tures? [closed]

• Should I upload unfinished work to arxiv or oth-
  er similar platforms?

• Can an academic paper use a fictional world
  (such as the show WestWorld) as a case study
  for AI, software engineering, and system imple-
  mentation?

In my experience, this does not improve readability, and in fact it slows me down. My feeling is that this is happening because the titles are anyway not fully justified (such as in the last question in the above screenshot), so having some words broken like this using hyphens—while others are fully moved to the next line—makes it confusing to follow.

Can this aspect of the UI please be improved?

---

Possibly related report in this same thread by Rafael Tavares: A title with a long word is not wrapped correctly.

Answer 10

discussion

Please actually make use of space that will be taken up anyway, and line-wrap sensibly

For reference, here is what the old /questions interface and new / interface look like for me (i.e., the two versions of the interface I get to see live at the moment), when the tags on a question are long enough to cause interference:

The old way often wastes tons of vertical space. However, the new way still wastes space when the tags are "incredibly long", and we sacrifice user card information for no benefit. The small card jumps down to the next line and looks weird and misaligned; and with the "incredibly long" tags, empty space above cannot be used. Meanwhile, when the tags are shortened and the user card moves back to the same line, it barely even conserves vertical space:

For me, it goes from 103 pixels between the vertical lines to... 101. Less than a 2% savings. Because of the information on the left-hand side (even without a "watched" badge, which seems like it might get changed anyway), almost all of that vertical space where the user card got displaced before, is still in use.

As I see it, the fundamental problem is that even though the tags and user card are intended to appear side by side, the tags don't account for this when wrapping.

My proposal is that the div containing the tags should be designed not to take up the whole width, but instead reserve space for the user card beside them. Along with a rearrangement to prioritize vote numbers (which seems in line with what others are suggesting), we could have something like:

To me, that looks much better already, even before giving any thought to the alignment of the elements in on the left side. This way ensures that vertical space is conserved (supposedly a motivating factor in the new design) even when the tags get longer; keeps things neatly organized regardless; and shows us the original, more informative user card.

---

Addendum: there was some confusion here because I am comparing apples to oranges in that the / page has always had a slightly different layout from the /questions page. At the risk of veering off topic:

My argument here, essentially, is that the oranges should be apples. It is jarring to move from one version of the layout to another as soon as I want to filter (not sort) questions in any way; and it is not at all obvious to me that a "home page" view distinct from a questions view makes any sense for Stack Exchange websites.

Just to make sure we're on the same page here: Questions are the reason Stack Exchange exists. Questions are the content being used for the "home page". The differences, apparently, are a) the layout (different, even though the OP spends paragraphs talking about the desire to have everything work the same way); b) the sorting and filtering functionality (inexplicably and arbitrarily limited); and c) some default filtering (not very discoverable, can't be interacted with, and can't be leveraged elsewhere).

For a site that tries to cater to an audience of the most sophisticated computer users out there, all of these choices strike me as absolutely bizarre. As a site user, I am defaulted to a mostly inferior version of the interface I want to use, get visually shocked every time I switch to the full version (which happens automatically if I do so much as click a tag), and can't properly capitalize on its few advantages.

Answer 11

bugstatus-completed

Content jumping

The new 'watched' label causes content jumping, so much that the lower questions are shifted down by 2 rows.

On page load, I start reading questions that get my attention. Half a second later, that questions jumps down by 1/2. Very annoying and unpleasant to the eye.

Answer 12

discussion

I'm not sure if it’s all intentional, but

1. The 25/01/2022 update (maybe 24! Time zones!) de-emphasises the score of a post significantly. I am not sure how I feel about that.

2. The left information panel seems inconsistent - based on the state of the question - watch/followed/bountied. I guess there are advantages to seeing this all in one place, but I think there's a certain value to not having different sets of visible things based on the state of the question. It's also really crammed... which makes the fact that SE's webpage has lots of whitespace elsewhere more obvious.

   

   Hardly anyone can see a deleted post, and being greyed out seems.. enough, rather than a bright red deleted sign right on top?

   I'm not a UX person, but my gut feeling feels like having the three basic items (answer count, score and views) feels like a reasonable compromise.

3. It seems more 'valuable' to show whether a post is followed (or bookmarked) to a user. There's less value to showing some tag somewhere on the question is watched where it is. Maybe highlight the specific tag(s) - which makes more sense with multiple tags.

4. The title is what everyone is interested in - and the space for it gets narrower. You have all the horizontal space in the world on a desktop. Just give it whatever you took away for the new style metadata, and make it consistent across all content, and it would be a better use of space. I know SE's allergic to excessively wide content, but at the moment, at best you're using a 1/5th of my screen.

5. The front page is a list. It’s jarring to have lists with variable sized items and metadata with no particular standard view. I also am not sure why view counts are on top, over score, since aside from the title, it seems that the score is what someone would want to look at.

6. Space is wasted. Consider the below, rather quick and dirty image

   

   By dropping the tick mark (or I guess moving it to the left, and left justifying this - basically all your metadata is lined up (well, it would be if my skills at everything were better). You can use the saved space to have more space for the title, and everything would 'line up' more naturally. You wouldn't have a jagged line of metadata along the left/margins of the home page either.

Answer 13

bug status-bydesign

On this page -- https://buddhism.stackexchange.com/?tab=active -- I'm seeing the number of answers above the number of votes.

This is not what I expect (given what's quoted in the "question" at the top of this meta-topic), and not what I want.

---

Edit to add -- at least for now it's currently appearing as follows (which I think is better):

Because, depending on your interest, you can now easily scan either the number of answers (because it's highlighted), or the number of votes (because it's the top-most of the three statistics).

Answer 14

discussion duplicate

In the "interesting" view which I use by default, all I see is "watched" questions:

Which begs the question, what's the point in this badge here? Especially being as it's colour and location gives it a really high prominence.

Answer 15

bug status-bydesign

Capitalization for "C/community wiki" is now inconsistent between list view and within the question:

The old view was consistent with lowercase-"c" used in both list and within a question. Is this change intended? Is there some reasoning for upper- or lower-case to be preferred here?

For what it's worth, another capitalization inconsistency is still present: "asked" is lowercase in list view and uppercase within the question.

Answer 16

discussion

This is a response to this statement by SE that they will continue rolling out the new design.

We're going to continue to roll out this design to the screens it already most resembles. This includes /questions, tagged questions and search results. The largest unresolved issue (see above) does not apply to these screens, as they have always had their stats laid out vertically like in the new design.

This is a fundamental misunderstanding of our complaints, the unresolved issues certainly do apply to these pages as well and by continuing to roll out the new design in its current state SE will make those pages hard to use. The old design on those pages was vertical as well, that is true. But it was also still very easily scannable as the important numbers were larger and the labels were below the numbers and produced easily recognizable shapes for the stats area.

I use almost only the /questions pages for looking at a site, all my previous complaints about the new design apply fully to those pages as well. And using the mobile view as you suggested is not a real solution either, that one is also inferior to the old design.

You're trying to make this widget more generic than it can be. You want to be able to display any new kind of content you can come up with. But not all information is equal here, and by putting everything into a uniform list you're buying that flexibility for a high price, making the new design worse overall.

The problem with the very limited amount of horizontal space in a vertical list of this kind is pretty much unavoidable. You can't just keeping putting more stuff in there without drawbacks. So you should also carefully consider which new features or concepts really need to be visible there or not. Or also old ones, e.g. whether it is really that important to show the number of views there.

Answer 17

discussion status-deferred

I mainly visit Stack Overflow on a mobile device and my main entrypoints are the "newest tag questions" of various tags. I then read through the question titles, filter out the ones I do not know anything about and open the rest in a separate tab. In the old mobile view I can see 5 questions at a time, whereas in the current responsive tag view I can only see 2 at a time. In the responsive "home" I can see 4 questions and on the new "greatest hits" I see 3. So rolling the new post summary to the tag view would improve the information density for me, whereas rolling it out to home would decrease it. Also it's still worse than the good old mobile UI.

Now the main difference between the new UI and the current responsive "home" seems to be the question's body excerpt, which I won't read anyway as either the title catches my attention and I visit the question or I do not. Would it be possible to omit it somehow from the new tags view in favor of having more questions in view?

Answer 18

discussion

The justification for these changes do not make any improvements for the user.

1. We generally assume 3 items of metadata: score, answers, and views. If we want to add new entries for e.g. bookmarks or revisions, it can be difficult to create a consistent layout in a list of questions.

Is it necessary to provide this additional information, if so why?

2. Inconsistencies in implementation have led to several different layouts across the site. When gathering requirements for a unified post summary component, we found at least 5 (five!) different layouts.

Why not pick one of the five, or at least incorporate the best features of each?

3. Scaling the design is tricky, both in window size and adding features and functionality. We need to support all sorts of metadata on all sorts of devices.

Again, how much meta information is necessary for the users to make quick decisions and navigate the site easily?

4. Our post summaries were only designed to support questions (and answers, kinda). We need to be able to display various content types in single lists. For example, in a list of notifications, we may want to present an article next to a question.
5. We have no unified place to put an action menu.

I don't understand either of these justifications.

Answer 19

bug status-planned

The display of the author information for community wiki posts is not always on one line. Browser: Firefox 95.0.1 on Ubuntu, 100% zoom. For the first CW question the author line does not go below the tags (which is different from the screenshot in the announcement, where it does go below the tags). For some CW posts the line does go under the tags however.

For the posts with a normal author it seems to work fine.

I tested also in Chrome and there the bug is not reproduced.

Another one where there is clearly enough space next to the tags where Firefox wraps the line (and in Chrome it is a single line next to the tags):

Answer 20

bug localization status-completed

There is no string to translate for "Watched" label:

Answer 21

bug duplicate

The watched badge gets added after page load, increasing prior non-badged posts' height.

I understand the "watched" functionality is client-side, because of performance reasons.

However, when it gets added like half a second after page load, a pixel or two get added to the post line's height on the homepage if the post had no badges (or answers) on page load. This is distracting.

The badge also jumps into view while you're reading, which is also distracting. The yellow background was more subtle in its appearing.

Answer 22

feature-requeststatus-review

Watching/Ignoring overrides the red coloring of moderator-only tags.

Moderator-only tags are usually red, but watching and ignoring them overrides this:

I think instead it should look something like this when you have a moderator tag watched or ignored, preserving the red color but adding the appropriate eye symbol:

(Image created courtesy of this bug.)

Answer 23

feature-requeststatus-review

Align tags and author to bottom of panel

I was trying to work out why the homepage looks "empty". As pointed out in response to another answer, the homepage has never had text excerpts, but it felt less obvious somehow.

I think the problem is that without a text summary, most of the content is floated at the top of the panel, with whitespace below it caused by the stack of labels on the left.

Compare these two questions:

In the first, the three labels on the left extend below the two lines needed for the title and tags, so almost an entire line of whitespace is left at the bottom. In the second, the long title is enough to bump the tags and author to below the stack of labels on the left, so the whitespace is just a thin strip on the left, and the gap at the end of the title's second line.

If the tags and author were aligned to the bottom of the panel, rather than to the top below the title, the first example would look more like this:

Since the whitespace is now inside the panel, it looks more deliberate, and less like something's missing.

Answer 24

feature-request status-completed

Currently of the 4 meta data fields in the post summary only views has a tooltip.

Answer 25

discussionduplicate

With the new main page design, I'm finding watched tag badges to be quite overwhelming in the design. At least at GraphicDesign.se.

They essentially "scream" at the viewer in my opinion.

Is there a local setting I can adjust to reduce their prominence?

---

I have used a custom style:

.post-tag.flex--item.mt0.s-tag__watched {
    background-color: var(--yellow-300);
}

Which, to me, appears much more inviting:

Or better still... yellow-500 border and color.

But, to be honest, I'd rather not have to employ custom styling.

Answer 26

In response to update 3:

Responsiveness - This was the primary catalyst for the change. The old layout was unusable on mobile and could not be feasibly scaled to work.

I miss being able to see the vote, answer, and view counts aligned as separate columns on the homepage so I'd like to emphasize why I believe the approach stated above is incorrect.

I understand that this is a difficult problem: it's either hard or impossible to make a single interface that scales well for the extremely different screen dimensions here. It's inevitable that you will need to make some sacrifices.

I believe sacrifices should be made by prioritizing. A vast majority of people who use all SE sites by browsing through a list of questions are using desktops/laptops. People contributing answers (particularly for programming and STEM sites which include math and code, which cannot be easily typed on a mobile) are almost certainly looking for questions to respond to while on computers. The number of mobile users looking at the question list and trying to parse information is small. It is their cosmetic experience that should be compromised on.

The present approach sounds like "If mobile viewers cannot experience the column-based layout, then nobody can." I'd prefer "A column-based layout for question lists is extremely important to the people who use that screen the most. Unfortunately, this means that mobile users won't have the best experience they can be given when using that screen, but that's just how it goes." It's utilitarianism.

Answer 27

discussionwatched-tags

Update 2022-01-29: It looks that the gold/yellow color of the watched tags was removed: thank you very much.

---

As I mentioned in a comment to the question, I really dislike how the watched tags looks now (update 2).

Now I'm wondering, have you considered the use cases ? ...

• where the user is following a popular tag so the homepage frequently has several questions with watched tags
• where the popular tags have a high activity (above the 50% of the questions have one)
• where multiple tags are watched and is common having questions with two or more of these tags? i.e. google-sheets and google-apps-script in Web Apps and SO.

Several of the recent answers show screenshots having multiple questions with watched tags:

• https://meta.stackexchange.com/a/375638/289691
• https://meta.stackexchange.com/a/375639/289691
• https://meta.stackexchange.com/a/375641/289691

Also, have you considered the users that visits the homepage multiple times every day?

Answer 28

discussion status-review

It might be worth mentioning in the context that above a certain resolution the title "1,000 questions" and the message below it are moved from the bottom of the page to the sidebar.

When that happens it squeezes the post summaries into narrowness leaving only an empty gutter below the message. I wonder if there could be a better solution for this and what it would be?

A larger resolution:

A smaller resolution:

Answer 29

feature-request

Add classes to the individual elements so custom user styling can be used with CSS without the need for JavaScript and string parsing for contents.

Current

<div class="s-post-summary--stats js-post-summary-stats">
   <div class="s-post-summary--stats-item js-added-stat-entry is-watched"> 
      <svg class="svg-skeleton-element-during-loading mr4"> 
      </svg>
      Watched
   </div>
   <div class="s-post-summary--stats-item has-answers">
       1 answer
   </div>
   <div class="s-post-summary--stats-item">
       0 votes
   </div>
   <div class="s-post-summary--stats-item " title="15 views">
      15 views        
   </div>        
</div>

Proposed

<div class="s-post-summary--stats js-post-summary-stats">
   <div class="s-post-summary--stats-item watch-stat js-added-stat-entry is-watched"> 
      <svg class="svg-skeleton-element-during-loading mr4"> 
      </svg>
      Watched
   </div>
   <div class="s-post-summary--stats-item answers-stat has-answers">
       1 answer
   </div>
   <div class="s-post-summary--stats-item votes-stat">
       0 votes
   </div>
   <div class="s-post-summary--stats-item views-stat" title="15 views">
      15 views        
   </div>        
</div>

Answer 30

bugstatus-review

Unexpected behavior when removing tags from watched and ignored.

I was able to create this interesting situation:

1. Add a tag to your watch list.
2. Add that tag directly to your ignore list
3. Remove that tag from your ignore list.

The result will be a tag with the watched color, the ignored eye symbol, and no tags on your watched and ignored list.

Alternatively, just removing a tag from your watch list removes the background shading of the question card, but the tag remains yellow:

Similarly, adding and removing a tag from ignore leaves the eye symbol in the tag:

Refreshing the page corrects the coloring to your settings.

(I've reproduced this bug on Win10 Chrome and iOS Safari.)