Change 683588 had a related patch set uploaded (by VolkerE; author: VolkerE):

[wvui@master] [typeahead-search][typeahead-suggestion] Wrap overlong words in title and footer

https://gerrit.wikimedia.org/r/683588

@Volker_E could you add some screenshots or a demo link for this?

Change 683588 merged by jenkins-bot:

[wvui@master] [typeahead-search][typeahead-suggestion] Wrap overlong words in title and footer

https://gerrit.wikimedia.org/r/683588

@alexhollender List items are caught and presented in https://doc.wikimedia.org/wvui/master/ui/?path=/story/components-typeaheadsuggestion--example-list-with-overlong-words

In T280982#7058554, @Volker_E wrote:

@alexhollender List items are caught and presented in https://doc.wikimedia.org/wvui/master/ui/?path=/story/components-typeaheadsuggestion--example-list-with-overlong-words

awesome, looks great. what are you looking for in terms of design review?

Waiting for next WVUI release.

Change 697700 had a related patch set uploaded (by Catrope; author: Catrope):

[mediawiki/core@master] Update wvui to 0.2.0

https://gerrit.wikimedia.org/r/697700

Change 697700 merged by jenkins-bot:

[mediawiki/core@master] Update wvui to 0.2.0

https://gerrit.wikimedia.org/r/697700

Test Result - Beta

Status: ✅ PASS
Environment: beta
OS: macOS Big Sur
Browser: Chrome
Device: MBP
Emulated Device: NA

Test Artifact(s):

QA Steps

✅ AC1: Search suggestions with long page names should wrap with word breaks.

Being bold.

Hm, doesn’t seem like a satisfying explanation to me; I always have this happen on dewiki, where content language and interface language are both German!

In T280982#7165594, @XanonymusX wrote:

I always have this happen on dewiki, where content language and interface language are both German!

Whereas I don't:

I moved this back to Needs More Work in the hope that our bug reports would lead us to a satisfying explanation.

So, your observation is actually easily explainable: the browser apparently does not know any working hyphenation for Hebrew specifically, just tried it on Firefox. Other languages work fine. While Chrome apparently does not provide hyphenation in this context at all. That’s why I already questioned the use of hyphens:auto several times; just use word-break as anywhere else and we should be fine on all browsers and in all languages.

EDIT: Seeing https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens, browser support for hyphenation is actually terrible. Please drop this (also from T171726) and consistently use word-break.

Hyphens are dependent on the languages enabled on OS/browser, correct. They are preferable over word-wrap/overflow-wrap solely for readability and skimmability and more widely for typographic reasons. MDN shows very well, why word-wrap: break-all doesn't play well in a language like German:

As long as it does not work in Chrome (the by far most widely used browser), it should not even be an option. And while in normal text it might be reasonable to use it, in the context of a diff (T171726) it does more harm than good, as readers won’t be able to distinguish between actual hyphens in the text and automatic hyphens. I guess in the search, hyphenation could be considered (but please consistently, not just in the footer), as users can directly see if they typed a hyphen themselves, but it needs word-break as fallback for Chrome and unsupported languages.

Also, my experiences with automatic hyphenation (mainly in MS Word) in German, English and Italian have not been very positive. Wrong hyphenation (which happens especially easily in long German composite words) amounts to a spelling mistake, and WP authors would not have the possibility to correct or prevent them; so imo it has been a good choice to not activate hyphens:auto for the main text area in Minerva so far …

@XanonymusX Sure, we've been very clearly adding hyphens in the past only around an acceptable outcome. One in-between solution I could see is to try out putting hyphens into @support parentheses and outside word-break: break-all. Possibly worth a try.

Updated word-wrap: break-all by word-break: break-all, which was original intention in comment.

Yes, but why would you go for break-all now? That one is the worst option available, as lined out in T171726 (at least for text, not sure if it would make any difference for mere search results). It needs break-word (and yes, as a fallback for hyphenation). There is also some confusion around whether to use word-break, word-wrap or overflow-wrap (Chrome does some weird things there), but that will need some browser testing. Search results and footer should act in the same way in any case.

@XanonymusX I came from a different type of typesetting in memory, you're right word-wrap: break-word; hyphens: auto; is the way to go.

And now I digged down further, the reason I wrote word-wrap is, that for supporting all browsers we need to combine both, once for Firefox then for the Blink armada:

Change 709242 had a related patch set uploaded (by VolkerE; author: VolkerE):

[wvui@master] [typeahead-search] Wrap those results

https://gerrit.wikimedia.org/r/709242

Ideally, the result would be wrapped in the language it's about, like lang=de and dir=ltr in the example above. But that's out of reach for this task.

Change 709242 merged by jenkins-bot:

[wvui@master] [typeahead-search] Wrap those results

https://gerrit.wikimedia.org/r/709242

How far are we on this? The search suggestions footer still does not wrap correctly on Chrome, in any case.

@XanonymusX this is blocked on the next WVUI release which is unfortunately delayed due some rather important conversations. Hopefully we can get to this within the next 2 weeks.

Change 715153 had a related patch set uploaded (by VolkerE; author: VolkerE):

[mediawiki/core@master] Update WVUI to v0.3.0

https://gerrit.wikimedia.org/r/715153

Change 715153 merged by jenkins-bot:

[mediawiki/core@master] Update WVUI to v0.3.0

https://gerrit.wikimedia.org/r/715153

@Edtadros this looks like a pass to me (compare with T280982#7165420).
I'd recommend using https://he.wikipedia.beta.wmflabs.org/wiki/%D7%A9%D7%99%D7%97%D7%94:%D7%90%D7%95%D7%9E%D7%91%D7%A8%D7%98%D7%95_%D7%94%D7%A9%D7%A0%D7%99,_%D7%9E%D7%9C%D7%9A_%D7%90%D7%99%D7%98%D7%9C%D7%99%D7%94%D7%90%D7%95%D7%9E%D7%91%D7%A8%D7%98%D7%95_%D7%94%D7%A9%D7%A0%D7%99,_%D7%9E%D7%9C%D7%9A_%D7%90%D7%99%D7%98%D7%9C%D7%99%D7%94 for testing Hebrew however on the beta cluster. You'll get different results than using uselang.