Follow-up: Search filters: what is missing posts 91–120
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
post #91 answers the question as asked. The question underneath it is different.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
Coming back to post #91, because the follow-up matters more than the original answer.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
Performance: if pages are slow to load, timeouts occur, or the site is unresponsive, that is worth reporting with details (when, which pages, how slow).
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
post #95 is right about the mechanism and I think understates the practical bit.
Moderation decisions: if you disagree with a moderation decision, raising it here gives it visibility. Staff will reconsider if you make a substantive case.
I read post #95 twice before replying, because I had assumed the opposite.
Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.
Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.
On post #95 — agreed on the reasoning, with one qualification.
Guideline clarity: if the guidelines are unclear or seem to be applied inconsistently, post the specific situation so staff can clarify or reconsider.
Collapsed as off-topic by two members at trust level 3 or above
Coming back to post #99, because the follow-up matters more than the original answer.
Search and findability: if you searched for something and did not find it, report what you searched for and what you expected to find. That helps improve indexing and tagging.
Feature requests: if the site would work better with a feature it does not have (better search, different filtering, new section) suggest it here with the reasoning.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
Search and findability: if you searched for something and did not find it, report what you searched for and what you expected to find. That helps improve indexing and tagging.
This follows post #103 rather than contradicting it.
Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.
Bugs and friction: the parts of the site that do not work the way you expected. Report them specifically (what you did, what you expected, what happened instead) so they can be fixed.
Community norms: if you think a norm has drifted or is not being followed consistently, raising it here can prompt discussion and realignment.
Collapsed as off-topic by two members at trust level 3 or above
Picking up post #107: that is the part I would want checked first.
Navigation problems: if you cannot find something you expected to exist, or the path to it is unclear, report it. Site architecture affects usability.
Accessibility: screen readers, keyboard navigation, contrast, font size — if something is not accessible to you, report it. Accessibility matters.
Worth separating two things that post #108 runs together.
Performance: if pages are slow to load, timeouts occur, or the site is unresponsive, that is worth reporting with details (when, which pages, how slow).
post #114 answers the question as asked. The question underneath it is different.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
On post #112 — agreed on the reasoning, with one qualification.
Display issues: broken layouts, images not loading, text overlapping — report with the browser and device you were using. Display bugs are platform-specific.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.