#MOUSELESS FIREFOX UPDATE#
#MOUSELESS FIREFOX CODE#

Var ke圜aptured = (e.ke圜ode ? e.ke圜ode : e. * To simulate a Shift+Tab event, a flag is recorded every time the shift key * class '-open' as an indicator flag caused timing/bubbling issues. * necessary to use a flag instead of reading the class '-open' because using the * flag is used to indicate the open status of a Select2 widget. * To prevent conflicts with multiple Select2 widgets opening at once, a second * active, then the automatic focus script does not happen.

* a flag is added to each element that the users clicks on.

#MOUSELESS FIREFOX CODE#

To prevent the code from overriding the user's focus choice * Users that click elsewhere on the document will cause the active Select2 If the next form field is a Select2 widget, the widget

* The following code moves focus to the next form field when a Select2 'close' Respond to suggestions on Tweet about the update.

#MOUSELESS FIREFOX UPDATE#

Update the download links in ueberdosis/mouseless-landingpage. Manually upload the Mouseless-.dmg to Gumroad. * the user can use to select a value from Select2 and to move Manually upload Mouseless-.dmg,, Mouseless-.zip and latest-mac.yml (find them in distelectron) to the DigitalOcean space. * tabbing from one form field to another. * This code was written because the Select2 widget does not handle * WARNING: untested using Select2's option To use this Web Console you will need an updated controller with some JSONP REST API improvements (Juha is going to commit this to the controller trunk but at present a version is available here, if you are using a special branch then merging my REST API changes into the branch you are using should work fine).While its not a perfect solution, the following is what we are using to simulate normal keyboard navigation on an HTML form that contains a Select2 element.

I tend to keep a pre-compiled WAR version of the latest commit here to save you compiling. After a little bit more work I will be pushing WebConsole 2.0 to the community for some alpha testing and you're more than welcome to try this out as it stands right now (committed code is changing quite frequently but I only commit in a usuable state), the branch I am using for development is the one you pointed to above and it will try and load a default controller and panel configuration (if one isn't defined then you will be prompted to enter the Controller URL and a Default Panel Name - unfortunately no Controller Discovery or panel selection at this moment but I will be adding this very shortly):. This is a complete re-write from the ground up and doesn't share any similarities with the WebConsole 1.0. I have been busy writing WebConsole 2.0 for the past few months and a working alpha version is pretty much there. Which version of the GWT Console should I be working with? Have folks had much success with the GWT console so far? Any hints of things to do for troubleshooting? I have begun to look at the Java code, using Eclipse and Google's GWT Eclipse plugin. So far, I have not been able to get past the initial screen on either. I've done some legwork, trying out the GWT Console from both and. The Mouseless Browsing add-on ( ) works by modifying the current web page's DOM tree to insert little numbers next to links, text boxes, etc., intercepting numbers typed by the user and causing links to be clicked on, fields selected, etc. I'm looking to combine the GWT Console and the Mouseless Browsing Firefox add-on to enable someone who uses their computer via an eye-scanning device to control the lights in his house.

Mouseless firefox