linkhyrule5
New member
When composing a reply of sufficient length in any appropriate box -- conversation reply, reply box at the bottom of the thread, etc -- the page down and page up buttons jump to the bottom or top of the post, respectively, instead of jumping a single "page"/reply box height. This is very annoying when trying to compose long posts section by section, as it makes it difficult to navigate within the post without a scroll wheel.
This bug appears to only affect recent Firefox versions. Chrome, Edge, and latest Waterfox (running Firefox 56 or so) all were unaffected.
I suspect some handler script is trying to get their parent's height and getting the height of the iframe (the entire document) instead of the height of the iframe in the actual parent, but that's just my guess from poking around at fixing it when I thought it was a general Firefox bug.
Note: I'm not an admin, so I don't know the exact versions. However, it seems to affect both XenForo v1 and v2, as I've seen it on two different XenForo forums, as well as this forum itself. It also only started recently (around a month ago), so it's probably fairly recent.
EDIT: Belay that last point; it occurred to me that I in fact switched Firefox versions around then, so that data point is confounded. I have no idea how old this bug is, other than it's probably more recent than Firefox 56.
This bug appears to only affect recent Firefox versions. Chrome, Edge, and latest Waterfox (running Firefox 56 or so) all were unaffected.
I suspect some handler script is trying to get their parent's height and getting the height of the iframe (the entire document) instead of the height of the iframe in the actual parent, but that's just my guess from poking around at fixing it when I thought it was a general Firefox bug.
Note: I'm not an admin, so I don't know the exact versions. However, it seems to affect both XenForo v1 and v2, as I've seen it on two different XenForo forums, as well as this forum itself. It also only started recently (around a month ago), so it's probably fairly recent.
EDIT: Belay that last point; it occurred to me that I in fact switched Firefox versions around then, so that data point is confounded. I have no idea how old this bug is, other than it's probably more recent than Firefox 56.
Last edited: