-648

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.

enter image description here

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.

enter image description here enter image description here enter image description here

Update 1 - 2022-01-25

Most of the reported bugs have been squashed. We're currently gathering together all the and 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

post summary before

After

post summary 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 questionmini layout
  • /questions/* (question list, list by tag, search, etc) - our “QuestionSummary” layout
    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:

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

162
  • 194
    I wish more work went into improving the UX instead of the UI.
    – Travis J
    Jan 12 at 22:34
  • 190
    I sure don't like it; much harder to see the metadata on the home page. Jan 24 at 21:58
  • 207
    This layout makes the desktop experience on the homepage worse, due to a lower information density displayed at once on the screen (# questions per screen), more difficult to parse and smaller statistics, too much padding between list items, misaligned tag and user bars with the bottom of the question block
    – illustro
    Jan 24 at 22:12
  • 161
    Is it just me or does anyone hates these changes to the feed and profile? I say "hate", because they're ruining the desktop experience. Jan 24 at 23:12
  • 60
    @BernardoDuarte the rapidly declining score on this post says "yes". As we've seen before though, score on announcements means nothing
    – Phil
    Jan 24 at 23:14
  • 138
    I honestly don't see how this can be considered an improvement. It's harder to find information from a glance and it looks incredibly unbalanced.
    – Ambo100
    Jan 24 at 23:42
  • 131
    It's horrible in nearly every way. Not a single improvement to my experience and several things which are worse.
    – takendarkk
    Jan 24 at 23:52
  • 84
    Why do UX changes always make things harder to read and digest sigh
    – deep64blue
    Jan 24 at 23:59
  • 74
    The change to add ignored tags with a black background, just to make questions you want to ignore stand out even more is ridiculous and bad UX design
    – illustro
    Jan 25 at 1:26
  • 72
    While it was great that you released this on the Greatest Hits page first for us to poke around with, there's a fundamental problem with that, and it's why so many people are upset now: no one uses the Greatest Hits page. It's not part of anyone's regular workflow, so it's harder for us to see how the new design will break our workflows. People aren't used to using it, so if information is a little awkward to acquire, or certain use-cases aren't served, it's difficult for us to see it. I don't have a solution, just wanted to point out why the pre-release didn't end up being that useful.
    – bobble
    Jan 25 at 1:37
  • 136
    While I appreciate the effort that's gone into this, it's really disappointing how consistently any UI changes to the site actually make the experience worse. It seems like every change is a net regression. Do the staff just think our consistent complaining is because people hate change? Because it's much more than that. Almost every change is a significant step backwards in some respects. This change seems to have a number of objective flaws. I feel like all the effort that's spent twiddling with a layout that's always been fine could be put to better use.
    – Michael
    Jan 25 at 2:03
  • 60
    I've created a userscript that brings back the old design.
    – Spectric
    Jan 25 at 3:50
  • 117
    In the name of everything that you hold sacred, please revert this!. My brain hurts trying to process this layout. There's way too much empty space and a tiny vote count is purely awful!
    – jojek
    Jan 25 at 9:27
  • 104
    As a Stack Overflow old-time developer. Don't come to the community with solutions. Come to the community with a problem statement and an idea and iterate. This way you'll get a better solution than this and you won't get massive downvotes. Remember: most people here are (a) better stack overflow experts than you or me and (b) better developers too. Give them a chance.
    – Sklivvz
    Jan 25 at 10:34
  • 76
    "While it was great that you released this on the Greatest Hits page first for us to poke around with, there's a fundamental problem with that, and it's why so many people are upset now: no one uses the Greatest Hits page." I have been around for over 11 years, and this meta.SE question is literally the first time I have ever heard about a "greatest hits" page. Staring at the current Stack Overflow interface, I have absolutely no clue how one is intended to navigate there, other than by manually entering the URL. So... no wonder nobody uses it. Jan 25 at 10:41

95 Answers 95

30

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

enter image description here

You could (should) format it more like this instead

enter image description here

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).

0
30

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.

29

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.

7
  • 5
    Yup, 100k views to reach "supernova" is correct. The thresholds for warm (1k), hot (10k) and supernova (100k) are preexisting and unfortunately hard coded, which means they can't be customized per site.
    – Ben Kelly StaffMod
    Jan 12 at 22:20
  • 30
    I’m not a fan of these symbols. Older eye’s and small screens lead to me trying to figure out what that symbol says only to zoom in enough to realize it’s not something to be read, and then not clear why it is there at all.
    – PatS
    Jan 16 at 14:53
  • 10
    @PatS Agreed. We'll just have to add another user script to surpress it, I guess.
    – Mast
    Jan 17 at 9:53
  • 8
    User script count is getting really out of hand. Every site "improvement" results in 5 more scripts...
    – takendarkk
    Jan 24 at 23:59
  • 1
    We wouldn't need all of these userscripts if they just gave us a profile setting to enable or disable all of the new "improvements" Jan 25 at 3:03
  • @BenKelly hardcoded into what exactly? If it's an external library that SE is making use of (something I doubt) then you may have a point, but anything hard coded into SE's own code isn't a valid reason for saying it can't be changed, and honestly it would be a far better improvement than half of the changes in this update to do so. (This update is pretty regressive in terms of differing usage needs and workflows in an attempt to unify what shouldn't be)
    – Andrew
    Jan 25 at 17:40
  • luckily .iconFireSm{display:none;} is enough to get rid of it. Works in Stylish.
    – MMM
    Jan 26 at 12:52
29

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.

light mode

dark mode

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--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)

11
  • 1
    “Hide ‘Ignored’ badge, do something with the question itself (hide?)” — This is already an option. If you click on the “edit” button in the “Ignored Tags” sidebar section on the home page, there’s a radio button setting of “Hide questions in your ignored tags” vs. “Gray out questions in your ignored tags”. Jan 25 at 3:34
  • @SebastianSimon thanks man, I had them hidden so couldn't see them to create a rule. Turns out the fade-out for ignored question titles is still active in the new design, just had to hide the badge
    – Phil
    Jan 25 at 5:45
  • 10
    Can you move this to a separate question thread so it doesn't get lost under a mountain of other answers? Jan 25 at 6:31
  • @SurpriseDog you mean like a new question on Meta? I don't think that will fly since a) it's not a question, and b) it would just be a duplicate of this answer
    – Phil
    Jan 25 at 7:22
  • 3
    Post it to stackapps.com . And you should probably upload this to github, this will cause the script to be auto-updated for the users when you change it. Jan 25 at 7:31
  • @HolyBlackCat it's already on Userstyles.org
    – Phil
    Jan 25 at 7:34
  • Oh. That works then. But I still suggest posting a link to stackapps.com. Jan 25 at 7:36
  • 1
    @HolyBlackCat done ~ stackapps.com/questions/9296/…
    – Phil
    Jan 25 at 7:45
  • It didn't work for me in dark mode. it was all wonky. Jan 25 at 8:53
  • @Tschallacka don't know what to say, it works for me. The browser needs CSS grid support
    – Phil
    Jan 25 at 12:16
  • @Phil i.imgur.com/S3kym0D.png that is what it looks like. If I hit f5 it renders ok. it seems to only not function when I come from a seperate site. Might have to do with that the user style applies before the css file of stack overflow is loaded. By adding !important behind everything it works properly for me in chrome all the time. Jan 25 at 13:20
27

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)?

4
  • 6
    The reasoning here is basically "less info > more space > less wrapping". In the majority of cases (for "normal" usage), the user cards as-is do not wrap to a new line, but adding the badges back would cause them to do so. From testing, the things that cause the line wrapping the most often are 1) many, long tags 2) adding Staff+Mod badges 3) long community wiki text. Using the MSE greatest hits page as our benchmark is a little misleading because all three of those things are very abundant here! Check out the Stack Overflow greatest hits page for more a more typical example.
    – Ben Kelly StaffMod
    Jan 14 at 15:40
  • 6
    A very informal study: MSE greatest hits first page, ~50% wrap. SO greatest hits first page exactly 2 posts wrap. If I get some time later, I'll write up a quick (local) script to add badges to those pages and see how many more wrap.
    – Ben Kelly StaffMod
    Jan 14 at 15:41
  • 3
    yet, you found plenty of space to emphasize collective leaderboard badges, even though gold badges are applicable network-wide.
    – Kevin B
    Jan 25 at 1:01
  • 3
    "The reasoning here is basically "less info > more space > less wrapping". In the majority of cases (for "normal" usage), the user cards as-is do not wrap to a new line, but adding the badges back would cause them to do so." So what?. The question title normally fits on one line. Even if you fit the tags, user info and question date into one line, the entire question will take up three lines anyway for answers, votes and views (four, with the current "watched" badges). So there is room for the old-style user card anyway, and also room to wrap a long set of tags to two lines. Jan 25 at 10:59
27

Mobile: multiline titles have a larger font size.

enter image description here

2
  • No repro on Firefox Nightly 98.0a1. Jan 25 at 3:00
  • 3
    This is probably unrelated to this change; I have a screen shot from a couple of weeks back from my phone because I meant to ask about this apparent bug, before this change rolled out.
    – tripleee
    Jan 25 at 7:57
27

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.

22

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

enter image description here

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):

enter image description here

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).

3
  • The order of the statistics on the left side have been tweaked since I took the original screenshots. answers has been moved to the top, as you're seeing now.
    – Ben Kelly StaffMod
    Jan 24 at 22:15
  • 29
    @BenKelly But why... The number of answers might be relevant if I'm searching for a post looking for an existing answer, but not when browsing recently active questions. I want to find things the community decided were great or terrible (or new!), not questions that are most answered (which on the sites I used mostly means the question is an older/recently-bumped posts, because answers accumulate slowly). I especially don't want my view to be dominated by which questions have an accepted answer, which usually says more about the asker (did they bother to come back) than the content. Jan 24 at 22:26
  • 7
    @BenKelly By design or not, I think it's a defect. Why did you change the order of statistics? You already visually highlight the number of answers, by giving it a border -- so I think you can afford to position the number of votes above that, for users and moderators who are mostly interested in a score.
    – ChrisW
    Jan 25 at 8:12
22

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.

5
  • 4
    Seems like U is also missing, at least they updated the ? menu to reflect the missing shortcuts.
    – 3limin4t0r
    Jan 25 at 23:38
  • 2
    This has now been fixed (for j/k/u, which is all of the shortcuts). Something interesting to note is that the existing code explicitly disallows ENTER for "clicking through" to the post on the home page specifically. This doesn't make much sense to me, but I'm leaving it in place until I get a chance to dig in and find out why. Just mentioning this so it isn't reported as a followup bug.
    – Ben Kelly StaffMod
    Jan 27 at 16:10
  • 2
    @BenKelly Weird. I'm pretty sure I've used j/j/…/enter on the home page and not just on /questions. Maybe j/k used to focus the link to the question and the browser's default Enter binding applied? Jan 27 at 20:45
  • 1
    @BenKelly The Enter key is still not working, and now I can't use /questions anymore to have a decent view and keyboard navigation. Feb 10 at 11:54
  • @BenKelly Some time later, this is still not working. Any update on this?
    – Ollie
    14 hours ago
21

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:

old interface, "very long" tags old interface, even longer tags new interface, "very long" tags new interface, even longer tags

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:

short tags in new version

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:

proposal ("very long" tags) proposal (even longer tags)

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.

6
  • How did you make these screenshots?
    – mkrieger1
    Jan 25 at 13:04
  • 1
    The ones for the existing UI are done with heavy use of Firefox's "Inspector" view, from right-click -> Inspect. (Any modern browser should have an equivalent feature.) I just screenshot normally after editing the DOM. My proposal is mocked up in Paint. Jan 25 at 13:06
  • 5
    As a small note, your first example is not what the homepage looked like prior to this change. It's what the /questions page looks like. The homepage has never had any text of the question, as far as I'm aware. Here's a screenshot of what it looked like - i.stack.imgur.com/d2L1I.png
    – Catija StaffMod
    Jan 25 at 14:40
  • 1
    The intent is for the /questions page to change, eventually, so that it looks like the new homepage but with question text (and a differently filtered list of questions), right? I already didn't like that the votes/answers/views information was laid out differently between / and /questions. Right now, they are very different. I assume that later, they will be less different than now. I would like them to be as similar as possible. I would also like the / page to be more functional and personalizable, per my other comment. Jan 25 at 14:57
  • I added to the post to explain this in detail. Jan 25 at 15:22
  • +1. I've actually almost gotten used to the change, but the user and history data being on the same line I still find jarring -- I think your mock-up would fix this.
    – LShaver
    Jan 27 at 1:51
21

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.

example image

example gif

2
  • 6
    This has been fixed by partially reverting the label approach back to using a colored background. We lose info that way, but it gives us an opportunity to revisit how the watched styles are being added to the page.
    – Ben Kelly StaffMod
    Jan 25 at 19:35
  • 1
    Already reported by CodeCaster. Jan 26 at 1:50
21

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.

    enter image description here

    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

    Enter image description here

    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.

2
  • 4
    Re "de-emphasises the score": view counts are more important now because we all know that popular == good, right? /facepalm
    – l4mpi
    Jan 25 at 13:01
  • 1
    @l4mpi not even popular, just older most of the time.
    – Andrew
    Jan 27 at 4:47
19

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

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.

6
  • 5
    The first question on the screenshot isn't watched. That page has always shown a small number of non-watched posts. But the new "watched" tag design is atrocious, and causes a lot of empty space.
    – interjay
    Jan 25 at 11:08
  • 1
    The current “Watched” badge is certainly way too prominent. I see the same as you: virtually every item I have in my Top Questions is “Watched”. And that’s fine, but it’s not necessary for every item to YELL this at me in yellow. Jan 25 at 11:32
  • 2
    @interjay I think you found yet another problem with the tag: it can possibly be misattributed to the previous post at a glance. Says a lot about the visual clarity.
    – Passer By
    Jan 25 at 11:34
  • 2
    OMG. This is sooooooo bad. I'm looking for interesting questions. All I can see is an avalanche of "Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched Watched" tags. Jan 25 at 11:54
  • Unfortunately based on the post they are trying to unify the layout and content across the multiple different layouts - each layout which before had served a different workflow or use case...
    – Andrew
    Jan 25 at 17:51
  • 1
    Marking as duplicate of this resolved post.
    – Ben Kelly StaffMod
    Jan 25 at 19:44
18

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

first "C" is uppercase for list view

first "c" is lowercase for flair within a 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.

4
  • 6
    Nice catch! This is the intended behavior and will roll out everywhere as we get each different area migrated. Behind the scenes, we have a highly reusable PostSummary component that will unify all our different implementations. A sub-component of that is a UserCard component, which will also be used when e.g. showing a question. The goal is a single unified implementation used everywhere. Obligatory XKCD
    – Ben Kelly StaffMod
    Jan 12 at 19:10
  • 4
    Oops, forgot the second question - Uppercase C is preferred here as it is being treated as a proper noun. "Community wiki" is the post owner / author / whatever in this case. As for the lowercase asked, I don't see where that one is uppercase. In that case, it is read like a sentence / sentence fragment depending on layout, so lowercase is the way to go.
    – Ben Kelly StaffMod
    Jan 12 at 19:14
  • 3
    @BenKelly "Asked" is uppercase on the question page itself (like just below the question title and above the voting arrows on this page here). Jan 12 at 19:22
  • 7
    @Randal'Thor Ahhh, I see it now. Not in the user card, but elsewhere. I hadn't considered that. I'll put this on the list of things to consider when we finally remove the mobile views for the question view.
    – Ben Kelly StaffMod
    Jan 12 at 19:24
17

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.

16

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?

3
  • 4
    It is definitely possible to remove the post excerpt - we'll be doing this on views that previously already did so (such as the home page). In the spirit of maintaining data compatibility, we are not currently planning on removing excerpts from screens that currently have them (and vice versa). This is always subject to change, but that's the current plan.
    – Ben Kelly StaffMod
    Jan 19 at 15:40
  • 4
    In regards to data density, I just did an informal test locally. All tests were done on MSE, in the Chrome web tools, with the device viewport set to iPhone SE, with the view scrolled so the top of the first question is at the top of the page. On the old mobile views, I get ~6 posts on home and /questions/tagged/foo. On the responsive versions I get 4.5 and 2.75 posts respectively. On greatest hits I get 3 posts with excerpt and 4 posts without. The biggest vertical space takers are (in order) - Post excerpt, wrapping titles, wrapping badges, stats moved to the top (vs left), user info.
    – Ben Kelly StaffMod
    Jan 19 at 15:46
  • @BenKelly The UI already adapts to narrower widths -- when the viewport is 980px it decides to put the statistics above instead of to the left of the answer. You could consider using a similar technique: to hide the post excerpt only on a small (i.e. mobile-like) viewport where the density is at a premium.
    – ChrisW
    Jan 25 at 5:44
16

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?

  1. 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?

  1. 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?

  1. 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.
  2. We have no unified place to put an action menu.

I don't understand either of these justifications.

2
  • The first sentence is partly incomprehensible. E.g, is a word missing? Can you fix it? And what do you mean by it? Can you elaborate? Jan 26 at 12:38
  • 3
    I'm sorry I can't see what you mean. If I had to clarify the statement I would say that none of the reasons given under 'Why we’re making these changes' specifically address an issue that effect the user experience. I emphasise user experience because in the end, the changes that have been made have had an overlay negative effect on how real people use the site, that should always be the primary motivation.
    – Ambo100
    Jan 26 at 16:28
15

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.

enter image description here

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):

enter image description here

3
  • 7
    Yup, that one is a known issue. The markup for that link(s) is generated elsewhere and reused, so we opted for a suboptimal layout for now. This is next on our list of items to fix. The markup is the same across browsers, but FF isn't buying into our uh... "inventive" css we're using to collapse the rendered <br /> tag.
    – Ben Kelly StaffMod
    Jan 12 at 21:56
  • @BenKelly It should break before the 'user percentage' so that it's consistent throughout. Currently: i.stack.imgur.com/YkNHK.png - Should be: Community wiki 16 revs, 7 users<br />37% Sonic the Anonymous Hedgehog --- So the 37 is under the 16.
    – Rob
    Jan 12 at 22:46
  • 4
    @Rob We were trying to go the other way with it - not breaking at all, but FF was having none of our nonsense. We're planning on changing the (fairly confusing) text here to something much easier to read anyways, so this is just a stopgap fix/bug.
    – Ben Kelly StaffMod
    Jan 12 at 22:47
15

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

Watched

2
  • 13
    This really proves that the "feature" was rushed out in response to this answer
    – Phil
    Jan 25 at 7:31
  • 2
    @Phil Not specifically. Staff forgetting to make translation strings available has been a recurring problem for years. Jan 25 at 8:45
15

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.

1
  • Marking as duplicate of this resolved post.
    – Ben Kelly StaffMod
    Jan 25 at 19:43
15

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

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

enter image description here

enter image description here

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:

enter image description here

(Image created courtesy of this bug.)

4
  • It's worth mentioning that it also overrides the "required-tag" (bug, feature-request etc.) style. Jan 28 at 11:34
  • Maybe for ignoring it is not so bad, because if you ignore the tag then you may also not be interested in whether it is a moderator-only tag - if it was red then you could complain "the red color attracts attention to ignored questions" similar to the problem with the ignored label. But for watched tags it should indeed be red.
    – Marijn
    Jan 28 at 14:51
  • 1
    @Marijn Looks like that's the design they went with. Watched stays red, ignored greys out. Jan 28 at 19:54
  • @BenKelly is this [status-complete] now? Seems fixed. Feb 8 at 13:28
14

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:

annotated screenshot of current homepage showing the whitespace in question

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:

quick mockup of alternative spacing

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

14

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

screenshot of tooltips in post summary

1
  • 4
    Some of our many post summary designs do not have consistent tooltips, including the design this unified component based on (the most frequently used version, which is currently still live on /questions). The QuestionMini view that preexisted had some low quality tooltips that exactly matched the text. I've readded (not yet live) these tooltips to the component used here.
    – Ben Kelly StaffMod
    Jan 25 at 17:10
14

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.

screenshot of vanilla question list

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:

screenshot of custom style question list

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

enter image description here

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

5
  • 6
    As a heavy daily user I feel they were fine before with just the question highlighted and all tags having same default color. The rainbow displays are hard to visually scan
    – charlietfl
    Jan 27 at 22:20
  • I sort of agree @charlietfl The background is sufficient. But I imagine there is some reasoning as to why the tags need visual variation.. possibly when there's no background on mobile?? But, well, there's the icon there too. So??
    – Scott
    Jan 27 at 22:22
  • 3
    My guess is the only reason is they are experimenting - with no user tests at all. They originally forgot to do any watched tag highlighting at all and now they've gone overboard
    – charlietfl
    Jan 27 at 22:28
  • @charlietfl it's also pretty obvious nobody tests the designs / colours in dark mode
    – Phil
    Jan 31 at 5:55
  • The more I look at this new layout... the more I dislike it and miss the old one.
    – Scott
    Feb 1 at 11:15
14

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.

14

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):

Screenshot of Home page of Academia SE showing titles broken using hyphens.

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.

5
  • Previously reported here: Hyphenation in titles makes it difficult to read quickly. Feb 11 at 20:36
  • 4
    @BenKelly I don't think this is a feature request, I think this is a sort of bug (although not the "it's broke" kind, but rather a "we didn't think about that for our style guide" bug). Titles should not use hyphens to handle overflow. Even excessively long words with no reasonable place to break them should just be wrapped without a hyphen in a title.
    – ColleenV
    Feb 11 at 22:34
  • 2
    Hyphenation is particularly problematic in german.SE: german.meta.stackexchange.com/questions/1694/… In the scope of this site, hyphenation is problematic, as question migth come in English, German language or even mixed languages (titles of English questions with German words or clauses in the title make up the biggest part). Hence, hyphenation of titles in german.SE is broken. Easiest fix would be to not hyphenate the titles at all. Apr 29 at 17:24
  • 2
    If you're going to hyphenate, at least do it correctly. This seems to be fixed now, but in the tex.stackexchange thread earlier today, i saw "\loggin-gall", Of course, TeX commands shouldn't be hyphenated at all, but that is just execrable! May 12 at 19:31
  • 1
    @barbarabeeton And I expect the well known “the-rapists” and “wee-knights”… ;-)
    – egreg
    May 12 at 20:37
13

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:

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

7
  • Yes, I know, I spend too much time on Stack Exchange but that used to be nice, better than ... you name it.
    – Rubén
    Jan 27 at 18:28
  • 3
    I think the question highlighting AND tag highlighting is a bit much -- should just be one. The tag highlighting makes more sense to me. Question highlighting creates problems for dark mode and custom site designs down the road.
    – LShaver
    Jan 27 at 20:33
  • I don't want to contradict you Ruben but personally I think the color on the watched tags looks great, speaking for myself I like it. I do give my watched tags lots of attention and now it's easier to distinguish if it's the question's primary tag I'm watching (which can be broad) or a rarely used minor tag. It works a lot better this way drawing my attention from the listing to questions that are about rare topics.
    – bad_coder
    Jan 27 at 21:34
  • 2
    @bad_coder Opinions are welcome (that is the purpose of discussion, don't you think?). By the way, my first contact to the "update 2" tag highlighting was on a moment that the Web Apps homepage had a lot of questions having watched tags... if the homepage had only one, perhaps I didn't dislike it so much (at least not no soon). I agree that that this tag highlighting could be perceived differently on another page, including the homepage of other site, where the watched tags appears rarely.
    – Rubén
    Jan 27 at 23:17
  • 2
    My take on it: on any page, you want to read what actually matters: content. But with every single item, you’re (potentially) greeted with a barrage of brightly colored labels which don’t matter to the user all that much in this list. On an individual list item basis, these labels may make sense as they tell a user which knows nothing about Stack Exchange, what a given list item is or has: is closed, contains watched tags, has a bounty, what have you. This only makes sense in isolation, not in the actual use case. This is what needs to be (re-)considered in the design process. Jan 28 at 1:25
  • 3
    The colored tags force you to read the tags on every question due to their brightness and high contrast, especially on dark mode. When you are greeted with a page that has a multitude of yellow, attention-grabbing rectangles on almost every line, it disrupts your focus on reading the titles. Maybe make it optional?
    – mcy
    Jan 28 at 6:22
  • "It looks that the gold/yellow color of the watched tags was removed" - I'm pretty sure they will apply this change again soon, since they keep doing changes without ever updating anyone or asking anyone. So better wait with the thanks. Jan 30 at 9:12
12

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:

screenshot greatest hits larger

A smaller resolution:

screenshot greatest hits smaller

2
  • 3
    Maybe put the stuff that's already in the right sidebar for other pages (i.e. filters, tag watching widgets, hot network questions)? Jan 13 at 21:13
  • 5
    When transitioning the post list to the new design, I did a few light touch changes to this page to give it a similar layout to the other pages under /questions (it already kinda did, but was broken). @CaveJohnson is on the right track, in that the other pages have more "stuff", so the gap isn't as apparent. I'll see how big a lift it is to add the rest of the sidebar to this page as well, but no promises if that would be a whole project in itself.
    – Ben Kelly StaffMod
    Jan 14 at 15:00
12

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>
1
  • 1
    OMG yes please. This is the one thing preventing my userstyle from re-arranging the stats column order
    – Phil
    Jan 25 at 13:46
11

Unexpected behavior when removing tags from watched and ignored.

I was able to create this interesting situation:

enter image description here

  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:

enter image description here

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

enter image description here

Refreshing the page corrects the coloring to your settings.

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

1

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .