Page MenuHomePhabricator

Auto scrolling badly breaks when writing "over the edge" (end of page)
Open, MediumPublicBUG REPORT

Description

There seems to be a major bug with auto scrolling that starts when one is writing "over the edge" of the currently visible browser viewport.

Steps to reproduce:

  • Visit a permalink of a topic (problem might be exclusive to topics as I can't reproduce it right now on a whole board)
  • Click "Reply" or the reply box at the bottom
  • Now start entering blank lines (just keep repeatedly pushing the enter key)
  • At some point the lower edge of the input field reaches the bottom of the currently visible browser viewport
  • Keep entering newlines (or maybe also some text from time to time to be able to better observe the problem)

Expected behaviour:

  • Flow should keep the active line (therefore the last line if you followed the steps above) in sight, therefore at the bottom of the page.

Actual behaviour:

  • At some point (soon after reaching the original end of the page) the automatic scrolling goes totally crazy.
  • It starts with the text jumping around by some pixels every time one is entering a character
  • Soon after the whole page is jumping around by multiple lines whenever entering a character
  • the active line is only quickly in the visible browser viewport when entering the character; quickly after the viewport is jumping back up the page and the active line is hidden.

The above occurs for me on Windows 7 using Firefox 27.0.1


Version: unspecified
Severity: major
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=61938
https://bugzilla.wikimedia.org/show_bug.cgi?id=58657

Details

Reference
bz61937

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:56 AM
bzimport set Reference to bz61937.
bzimport added a subscriber: Unknown Object (MLST).

[Confirmed]
Regarding this, and bug 61938 - I believe the "scroll-to" code is currently being overhauled. (Or was recently, and these are fresh bugs). I'll nudge the relevant devs, in case this is part of a work-in-progress.

Also, much thanks for these exemplary detailed and clear bug summaries. They're greatly appreciated. :)

Not seeing this on Chrome, so it may be FF-specific (since I know Quiddity is also on FF).

Aklapper changed the subtype of this task from "Task" to "Bug Report".Feb 15 2022, 9:39 PM
Aklapper removed a subscriber: wikibugs-l-list.