Open
Bug 1259604
Opened 10 years ago
Updated 3 years ago
Confluence search textbox resets its horizontal scroll-position as you type (and after you type), keeping you from seeing what you're typing
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox48 | --- | affected |
People
(Reporter: dholbert, Unassigned)
Details
Attachments
(2 files)
STR:
1. Visit some Confluence instance, e.g.
https://demo.stiltsoft.com/ (no login required)
...or:
https://mana.mozilla.org (requires MoCo login)
2. Type "This is my long search term", or some other longish search term into the box in the upper-right corner of the page.
ACTUAL RESULTS:
While you're typing, and when you're done typing, the textbox continually updates its autocomplete dropdown, and *with each update, the textbox's horizontal scroll position is reset to the beginning. So your cursor (where you're currently typing) gets continually clipped, and you can't really see the text that you're typing as you're typing it.
EXPECTED RESULTS: Textbox's scroll position shouldn't be continuously reset; it should follow your cursor and keep up with your typing.
Chrome 51 (dev edition) gives me EXPECTED RESULTS.
Firefox 48 (nightly) gives me ACTUAL RESULTS.
| Reporter | ||
Updated•10 years ago
|
Summary: Confluence search widget snaps end of search terms out of view, after populating its autocomplete menu → Confluence search textbox resets its horizontal scroll-position as you type (and after you type), keeping you from seeing what you're typing
| Reporter | ||
Comment 1•10 years ago
|
||
| Reporter | ||
Comment 2•10 years ago
|
||
| Reporter | ||
Comment 3•10 years ago
|
||
Note: in Chrome, the widget does reset its scroll position (as in Firefox) **if it loses focus**, e.g. if I click somewhere else on the page.
So our problem might be that the page thinks the widget is losing & regaining focus (and it resets the scroll position each time), or something like that.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•