Search in header gives too deep results

Contribute Bug

AI-generated summary

Jagster reports a bug where the header search feature on Discourse (when set to ‘Search field in site header’) displays overly deep results that can’t be scrolled, hiding options like ‘more…’ and saved searches. The issue occurs on iPad (latest iPadOS) using DiscourseHub and Safari, persists in safe mode, and isn’t caused by theme/component conflicts. Jagster considers it a bug due to inconsistent behavior compared to the search icon next to the avatar, though acknowledges it may also be a UX issue. They also humorously note AI-generated Finnish titles in the Translator feature, while praising the frontend translation effort. sam acknowledges the report and notes that chapoi is tracking and working on improvements. chapoi confirms the issue and has made changes aimed at resolving it.

1

When setting Search experience: Search field in site header this happens:

The image shows a screenshot of a Finnish-language online forum with various discussions and topics, prominently featuring discussions about target speakers and punks. (Tekoälyn laatima kuvateksti)
The image shows a screenshot of a Finnish-language online forum with various discussions and topics, prominently featuring discussions about target speakers and punks. (Tekoälyn laatima kuvateksti)1640×2360 273 KB

It can’t be scrolled, I can’t reach more…, there isn’t way to see saved searches.

iPad (newest iPadOS) and DiscourseHub, but it was problematic in Safari too.

I don’t know if this comes from AI, or something else, but I know it is not conflict between themes and/or components, plus safe-mode did same.

I count this an bug, because it doesn’t work as expected, and differently than when seach icon next to avatar is in use. But yes, it could be an Contribute > UX glitch too.

(As much I like that you are developing Translator I don’t like when AI suggests tittles on Finnish… or should I give a try :joy: But big kudos that you have translated big part of fron end too)

4 Likes
2

Thanks for reporting @chapoi is tracking this and working on improvements here, stay tuned.

2 Likes
7

Hey,

Thanks for the report. Made some changes that hopefully avoid the issue

1 Like