Today, Bungee Labs announced our official move to support Google’s new browser, Google Chrome. See “Bungee Connect: First Platform-as-a-Service to Offer ‘Write Once, Run Anywhere’ Support for All Major Browsers, Including Google Chrome” for details.
Shortly after Google released the Chrome beta, our test team went to work to identify exactly what worked and what didn’t. They found that Google Chrome loaded and ran Bungee-powered applications with only a few issues, which we detail below.
Security, Bungee Connect and Google Chrome
More on the Bungee Connect security can be found in the FAQ.
The issues that we have identified for Bungee-powered applications running in Google Chrome are as follows:
- Focus Issues (Some Controls Require Extra Click)
There will be on-screen elements that you must click once in order to set focus to that item. Although you may see button ‘flyover’ effects happen. Typically, this happens when you move between different regions of the application window. We have yet to find a case in which this blocks an application’s intended functionality, but we definitely confirm that the issue is a nuisance that needs to be fixed.
- Drag & Drop Issues
Drag/drop is not 100% predictable right now. Sometimes it works perfectly, but occasionally a ‘move’ action happens where the program is set to ‘copy.’ Sometimes, you can’t even initiate a drag operation (although this is sometimes just a focus issue, as described above). So far, this particular issue is perhaps the most serious we have seen.
- Modal Dialogs Sometimes Non-Modal
Occasionally, a dialog pop-up may allow an end user to interact with the main application when it is not supposed to. Certainly this is better than having non-modal dialogs get forced to be modal, but it still can result in multiple problem scenarios, such as a key dialog getting lost behind a main application window, or critical workflow data not getting entered when it is needed.
- Default Action Broken on StyleButtons
Lastly, we found a minor annoyance with how Google Chrome handles our StyleButton control. If a StyleButton has been flagged as “Default” (meaning it’s the default action for the Enter key), it doesn’t matter…you either have to click it with the mouse or tab over to it.
The Bungee Connect IDE is a Bungee-powered application, so it experiences the above issues. However, there is one issue that particularly affects developers using Bungee Connect with Google Chrome:
- Cannot Drag Controls onto Forms
The previously-mentioned issues with drag & drop affect form construction consistently: you can’t add controls to a form in Google Chrome. (Although you can add Bungee Logic statements to a function. But you can’t re-arrange them. Go figure.) This is pretty much a showstopper for using the IDE with Chrome.
We intend to fully support the use of Bungee Connect’s IDE from Chrome before year-end.