| Yair_rand | |
| Jan 14 2013, 5:04 AM |
| F10255: ulsbug.png | |
| Nov 22 2014, 1:13 AM |
If a user using a ltr language starts typing in rtl characters into the search, or a rtl language user starts typing ltr characters in, ULS doesn't adapt the direction of the search field, making the autocomplete text overlap the regular text strangely.
Version: unspecified
Severity: normal
Whiteboard: ux
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=50787
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T57683 Bugs caught by mw.loader.inspect() (tracking) | |||
| Resolved | Nikerabbit | T58292 Make ULS more lightweight | |||
| Open | Feature | None | T27815 Allow user to set the language preference when creating an account | ||
| Open | None | T161517 Allow anonymous users to change interface language on Commons with ULS | |||
| Open | None | T5665 Auto-detect interface language for anonymous users on Wikimedia projects | |||
| Open | None | T58464 Allow anonymous users to change interface language on Wikimedia wikis with ULS | |||
| Open | Feature | None | T49802 [New UserLogin] Supersede language selection bar with UniversalLanguageSelector | ||
| Duplicate | Nikerabbit | T15097 Deploy ULS/UniversalLanguageSelector to all Wikimedia wikis (tracking) | |||
| Open | None | T45951 ULS search autocomplete doesn't handle RTL well: doesn't adapt direction, autocomplete text overlaps regular text |
(In reply to comment #0)
Thanks for the report. It would help us to better identify the problem of text overlap if you could attach a screenshot or the exact steps of reproduction preferably with a suggested string. Thanks.
Created attachment 11963
LTR language name in RTL context
Steps to reproduce:
Alternatively, have a rtl language selected and type an English string, for example "Eng" (pictured in screenshot).
Attached:
This will require some magic with mixing placeholders and content with different direction. I'm not even sure that it's possible.
Another option is to add automatic direction detection - it's usually not perfect, but could work in this case.
p.selitskas wrote:
I cannot reproduce this behaviour in Chrome 29, Firefox 23.0.1 and Internet Explorer 10 @ Windows 7.