This bug was fixed in the package oxide-qt - 1.0.0~bzr475-0ubuntu1
---------------
oxide-qt (1.0.0~bzr475-0ubuntu1) trusty; urgency=medium
* Update to r475
- Update to Chromium 35.0.1916.6
- If WebView.newViewRequested isn't implemented, navigations should happen
in the originating view
- Refine WebView.newViewRequested and WebView.navigationRequested API's
(LP: #1300891)
- Improve the form factor detection (LP: #1301678)
- Add WebView.javaScriptConsoleMessage signal to allow the application
to intercept console messages from content (LP: #1291389)
- Improve the LoadEvent API
- Fix an abort when setting WebContext.sessionCookieMode on a context
that has no path (LP: #1301650)
- Expose the default WebContext via Oxide.defaultWebContext() (LP: #1297552)
- Send fake keydown and keyup events when composing text with an
input method (LP: #1300382)
- Bump the API version to 1.0
-- Chris Coulson <[email protected]> Fri, 04 Apr 2014 19:28:27
+0100
** Changed in: oxide-qt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300382
Title:
input events not being flushed in browser until pressing hardware keys
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1300382/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
