# Zoek terugzetten naar oude live zoekpatroon

**URL:** https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845
**Category:** Feature
**Created:** [12 oktober 2021 om 13:04 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845 "2021-10-12T13:04:28Z")
**Posts on this page:** 8
**Page:** 2

<div class="post-metadata">

### Author: ![spirobel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/spirobel/32/170908_2.png) [@spirobel](https://meta.discourse.org/u/spirobel)
#### Post date: [13 oktober 2021 om 19:07 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/23 "2021-10-13T19:07:40Z")

</div>

> [@awesomerobot](#):
>
> there’s some reasoning behind every change

right now this reasoning is based on paradigms that are not verbalized for the most part. It is the result of intuition and the discourse with customers. This strategy will avoid regressions and catastrophes like the loss of a customer for the most part. But it has its limits. There is no clear scale against which progress can be measured. So pragmatic KPIs like “How many users complained about / praised the change?” and “did it achieve secondary goals like improved performance etc?” will decide if a change was a success or not.  
The issue is: potential users and potential customers cant complain.  
A user interface is like a language. Our ability to understand this language is influenced by the culture we got socialized in. If we don’t verbalize the underlying paradigms we employ while creating these user interfaces we will embed our culture into these systems. This means that they are easy to use for people like us but not necessarily in general.  
Benefits a design system might bring from an abstract perspective:

> Consistent appearance and interaction, maintaining a familiarity to the user, can reduce the difficulty of learning, cognitive and operating costs, and improve work efficiency.  
> [source](https://ant.design/docs/spec/values)

> [@awesomerobot](#):
>
> When it comes to this change specifically, what guidance could a design system have provided?

By having clearly defined categories of user interface components this confusion between “data display” components and a user action (for which a button might be used for example) would not have happened. If there was a page like [this](https://ant.design/docs/spec/buttons) where all the different UI components and their purpose was listed a rational discussion could be had. It would also be good if these discussions would be held in public and weren’t just communicated through git commit messages.

---

<div class="post-metadata">

### Author: ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [13 oktober 2021 om 20:10 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/24 "2021-10-13T20:10:18Z")

</div>

> [@RGJ](#):
>
> It would be fantastic if this advice would be shown in the placeholder, which now just says ‘Search’.

I just added a similar hint, but not in the placeholder. Given all the languages Discourse is translated in, a long string in the placeholder risks being cut off. Plus, as soon as you type, the placeholder is gone. Instead I went with a right-aligned hint in the search all topics/posts row:

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/4/f4dd424a86eda1a614bbea63099711dbc79a373c.png)

> [@Ivan\_Rapekas](#):
>
> the cross-reference link bug today

This is also fixed alongside a few more minor bugs.

> [@Slowhand](#):
>
> Maybe I’m remembering incorrectly, but it seems that after clicking on a topic, I would get the prompt to search in the topic without altering the search word.

I will be working on a better solution for this use case, it’s on my todo list.

---

<div class="post-metadata">

### Author: ![JonathanShaw](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jonathanshaw/32/532672_2.png) [@JonathanShaw](https://meta.discourse.org/u/JonathanShaw)
#### Post date: [13 oktober 2021 om 20:23 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/25 "2021-10-13T20:23:09Z")

</div>

My experience of the within-topic search experience on meta right now is that it seems weirdly broken.

When I want to search within a web page, I’n trained to press ctrl F, type, and press enter. I understand why Discourse needs to hijack /enhance that for long topics.

What happens now when I press ctrl F on meta and type ‘theme’ into the search box is:

1. it shows me a bunch of users (WTF) or tags (helpful)
2. if I press enter, it shows me a bunch of other topics (WTF, I’m trying to search within topic)
3. If I press “more” I lose the topic context altogether

My conclusion: you’re completely violating users trained expectations of how within page search works on the web.

Suggestions:  
(1) if the user has triggered search with ctrl F, default to within-topic search; but keep all topics search as default when the search is triggered in the way that other global navigation is.  
(2) don’t show users by default, as mostly people are searching for topics.

I’m honestly puzzled why you used a sledgehammer for this nut; I’d have thought the performance impact of per-character searching could be handled by a 500ms delay before triggering search.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [13 oktober 2021 om 20:28 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/26 "2021-10-13T20:28:40Z")

</div>

I am sorry, I am closing this for 2 weeks per:

> [@Revert search to old live search pattern](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/19):
>
> We have observed that pointless search work was the bulk of search work our servers did. Our servers did mountains of search work, on some sites it was the 2nd or 3rd most expensive route when it comes to total cost. Our servers are very very fast, we can eat a lot of this pain. Self hosters on the other hand were paying a price that was way too high. This is not in our plans, sure we will tweak and improve the design, possibly make the hinting richer and so on. However we have no plans to sa…

Please open a new topic for constructive feedback around new improvements for the new paradigm.

This discussion has gotten off the rails.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [13 oktober 2021 om 20:28 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/27 "2021-10-13T20:28:51Z")

</div>



---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [27 oktober 2021 om 20:29 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/28 "2021-10-27T20:29:31Z")

</div>

This topic was automatically opened after 14 days.

---

<div class="post-metadata">

### Author: ![Beckfield](https://avatars.discourse-cdn.com/v4/letter/b/ec9cab/32.png) [@Beckfield](https://meta.discourse.org/u/Beckfield)
#### Post date: [12 december 2021 om 05:07 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/29 "2021-12-12T05:07:21Z")

</div>

I’ve been trying to get used to this new search, and I have to agree with the OP — it’s not a step forward. It’s more difficult to use, and it’s a confusing UI.

---

<div class="post-metadata">

### Author: ![oshyan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/oshyan/32/212644_2.png) [@oshyan](https://meta.discourse.org/u/oshyan)
#### Post date: [30 december 2021 om 23:23 UTC](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845/30 "2021-12-30T23:23:50Z")

</div>

> [@Beckfield](#):
>
> I’ve been trying to get used to this new search, and I have to agree with the OP — it’s not a step forward. It’s more difficult to use, and it’s a confusing UI.

I feel the same, though I also want to be clear that I understand the points made by the team around the reasoning for it, and I recognize the change has other significant benefits. So it seems it is just a matter of getting it right, hopefully with further refinement on the new design. Unfortunately I don’t have any specific ideas for improvements at the moment, or I’d open a topic for the…

That said, I had this same thought:

> [@JonathanShaw](#):
>
> I’m honestly puzzled why you used a sledgehammer for this nut; I’d have thought the performance impact of per-character searching could be handled by a 500ms delay before triggering search.

While the team doesn’t necessarily have an obligation to answer, I hope they will nonetheless. 😁 Doesn’t seem seem to necessitate its own topic though.

[Vorige pagina](https://meta.discourse.org/t/revert-search-to-old-live-search-pattern/205845.md?page=1)
