Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×

[bug in outdated jquery-ui script] up/down keys don't work in the chat textarea on the editor page because of jQuery UI Autocomplete 1.9.0

1400461029

Edited 1400461082
Hi there. On the editor page <a href="https://app.roll20.net/editor/" rel="nofollow">https://app.roll20.net/editor/</a> up/down keys don't work in the chat textarea. That's because of a bug in jQuery UI Autocomplete - <a href="http://bugs.jqueryui.com/ticket/8911" rel="nofollow">http://bugs.jqueryui.com/ticket/8911</a> which was fixed in jQuery UI 1.10.3. Could you please update the jQuery UI script version to 1.10.3+, if it doesn't break anything?
At some point we do need to update jQuery/jQuery UI since we are now a couple versions behind, but honestly it always takes a long time because there are lots of regressions, and since we are usually doing fine in terms of functionality it's not a high priority. That being said, I can confirm this issue in Firefox. My guess is most people aren't noticing it because the only things I think you typically use the up/down keys for the in chat box is a) re-doing the last command, and b) navigating the auto-complete box, both of which are still working fine. Just out of curiousity, what are you needing to use the up/down keys for? Are you typing multi-line chat messages?
1400462363

Edited 1400462428
&gt;Are you typing multi-line chat messages? Yes, sometimes when I typed roleplaying messages (multi-line or one-long-line) and want to edit it before sending, I find it quite hard to navigate in it without up/down keys.
I backported this fix so it should be fixed now. Thanks for tracking down the specific bug, made it much quicker to fix it :-) It's on Dev now and will go live to everyone on the 28th.
Riley D. said: I backported this fix so it should be fixed now. Thanks for tracking down the specific bug, made it much quicker to fix it :-) It's on Dev now and will go live to everyone on the 28th. Thank you for that.