Chat and javascript on top of the page f**ks up scrolling using arrow keys - Page 1
Forum section: electronics / general

author: Wartex
author_rank: Frequent Contributor
timestamp: April 15, 2012, 03:36:10 pm
content: subjArrow keys are ignored because chat windows is stealing the focus. It's really hard to browse on a laptop, I have to grab the scrollbar with a mouse pointer every time. If you press PgDn, you jump to the very bottom of the page as well.

author: baljemmett
author_rank: Unknown
timestamp: April 15, 2012, 05:45:31 pm
content: Might be browser-dependent -- it doesn't do that for me, using Chrome or (ancient) Firefox.

author: Wartex
author_rank: Frequent Contributor
timestamp: April 15, 2012, 06:27:08 pm
content: Quote from: baljemmett on April 15, 2012, 05:45:31 pmClick on chat window, then use arrow keys to scroll the page.

author: baljemmett
author_rank: Unknown
timestamp: April 15, 2012, 08:29:40 pm
content: Quote from: Wartex on April 15, 2012, 06:27:08 pmWell yeah, if you're going to give the chat window focus, then it'll take focus. If you click outside the chat window then you can scroll the rest of the page again...

author: Wartex
author_rank: Frequent Contributor
timestamp: April 15, 2012, 10:20:23 pm
content: Quote from: baljemmett on April 15, 2012, 08:29:40 pmIt regains focus via AJAX refresh when someone posts something. It also steals the focus because it's loaded AFTER the main page is loaded. The way your browser behaves is broken, I tried latest FF and Chrome and arrow keys don't work.

author: T4P
author_rank: Super Contributor
timestamp: April 15, 2012, 10:28:27 pm
content: Quote from: Wartex on April 15, 2012, 10:20:23 pmEh .... Mine does not act like that either ... 0.16.91.381

author: AntiProtonBoy
author_rank: Frequent Contributor
timestamp: April 16, 2012, 12:00:09 am
content: Speaking about the chat box, would it be possible to have new shoutouts added at the bottom of the scrolled box, as opposed on the top? It's counter intuitive to read lines from the bottom-up.

author: Mint.
author_rank: Frequent Contributor
timestamp: April 16, 2012, 12:05:30 am
content: Quote from: AntiProtonBoy on April 16, 2012, 12:00:09 am

author: baljemmett
author_rank: Unknown
timestamp: April 16, 2012, 12:32:48 am
content: Quote from: Wartex on April 15, 2012, 10:20:23 pmI see neither of those behaviours here. It refreshes via AJAX every second or two, in fact, but that doesn't interfere with page scrolling or focus for me at all.QuoteHmm, so my browser behaves exactly as one would expect it to behave with no odd consequences for scrolling, and your browser acts weird and interferes with your cursor keys --yet it's my browser's behaviour that's broken?

author: Monkeh
author_rank: Super Contributor
timestamp: April 16, 2012, 01:25:50 am
content: Quote from: baljemmett on April 16, 2012, 12:32:48 amIt does not work correctly in current Firefox. I will not use Chrome as it does not suit my purposes, I cannot and will not use IE. Thus the site needs to work in Firefox.

author: AntiProtonBoy
author_rank: Frequent Contributor
timestamp: April 16, 2012, 01:31:34 am
content: The index page scrolling is broken for me as well in the latest Firefox version. Works OK for other pages though. Interestingly, I decided to disable JavaScript and the index page still has the same issues. This behaviour is weird, perhaps there is something more going on than just a simple JS hiccup.

author: TerminalJack505
author_rank: Super Contributor
timestamp: April 16, 2012, 01:55:03 am
content: Quote from: Wartex on April 15, 2012, 03:36:10 pmMy browser (Firefox 11.0) behaves the same way. It's not a big deal, though. Adobe Acrobat Reader likes to join in on the fun too. If I have a PDF open in the browser then the scroll wheel doesn't scroll the tab I'm viewing. Instead it scrolls the PDF. Yay!

author: baljemmett
author_rank: Unknown
timestamp: April 16, 2012, 02:08:31 pm
content: Quote from: Monkeh on April 16, 2012, 01:25:50 amJust tried it with the latest Firefox I have installed at work (FF9) and indeed, it's broken. However, it never used to be broken -- FF3.5 and FF4 work fine, as does Chrome, as does IE (eww), as does whatever older Firefox version my netbook runs. I would humbly suggest, therefore, that the problem lies with recent versions of Firefox and so it might be worthwhile filing a bug with them.(The "the site needs to work with browser X" approach, where browser X suddenly and inexplicably demonstrates unexpected behaviour and "work with" is a euphemism for "work around a problem with", is pretty much the reason web development can be a gigantic pain in the arse when you try and do anything vaguely interesting. Has been for many years, and yet we never seem to learn...)

author: Monkeh
author_rank: Super Contributor
timestamp: April 16, 2012, 02:29:18 pm
content: Or perhaps the problem lies with functionality not implemented in older versions of Firefox and current versions of Chrome and IE.Either way, I don't consider 'works in IE' valid, as support for IE should not be a goal, requirement, or even interesting side note in web development. It should be abandoned, permanently, as a lesson to Microsoft and their users.