lp:~artmello/oxide/oxide-handlekeyboardevent

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1313727: Deliver input events that aren't consumed by a renderer back to the webview

High

Fix Released

Link a bug report

Related blueprints

543. By Arthur Mello on 2014-04-29

Add code to map WebEvent KeyCode To QKeyEvent KeyCode

542. By Arthur Mello on 2014-04-29

Fix function signature

541. By Arthur Mello on 2014-04-29

After creating the new QEvent post it on the event queue

540. By Arthur Mello on 2014-04-28

Add HandleKeyboardEvent to the content::WebContentsDelegate.
This will convert the internal events back to QEvents

539. By Chris Coulson on 2014-04-28

Add a couple of extra options that are used on Chrome for Android

538. By Chris Coulson on 2014-04-28

Fix the comment - BrowserProcessMain isn't reference counted anymore

537. By Chris Coulson on 2014-04-25

Update Chromium to 36.0.1951.5

536. By Chris Coulson on 2014-04-25

When fetching the texture ID, we wait on a sync point in the GL command stream. We block the Qt render thread until this has been fetched, which works with minimal overhead on the desktop. However, when running fairly heavy webgl demo's on mobile we sometimes have to wait in excess of 25ms, which means that the frame rate for the whole application falls through the floor. Mitigate against this in a couple of ways:
- Don't post a task to the GPU thread event queue to add a sync point callback. Instead, implement a task observer that processes these after every task
- Don't dispatch SwapAcceleratedFrame until we have a texture ID. Unfortunately, this does mean posting one extra task to the UI thread per frame. Not sure if there's another way to do that

535. By Chris Coulson on 2014-04-25

Deprecate WebPreferences.touchEnabled and WebPreferences.databasesEnabled, as both of these are runtime-wide settings in blink

534. By Chris Coulson on 2014-04-24

We don't plan to implement InitAsPopup and InitAsFullscreen, as we have no use for popup RWHV's