Remove Xlib dependency in chromium_impl/ui
authorArnaud Renevier <a.renevier@samsung.com>
Tue, 12 May 2015 20:19:50 +0000 (13:19 -0700)
committerYoungsoo Choi <kenshin.choi@samsung.com>
Tue, 10 Jul 2018 06:57:09 +0000 (06:57 +0000)
commit5bef4bf7c6d3e4f96c03d6f37ee285713c4c4bdf
treeb0bc3230b6aa66ab64f9f03c36d76878832c09d6
parenta97d597da699c319b3d26cac5ce6c0f7309b4df9
Remove Xlib dependency in chromium_impl/ui

We remove Xlib dependency, or rely on ecore-x instead.

We stop implementing ScreenEfl::GetCursorScreenPoint and
ScreenEfl::GetWindowUnderCursor.
Those methods are only used with toolkit view, which is not enabled for
our port. Those methods are also left unimplemented in android or ios.

In ScreenEfl::GetPrimaryDisplay, we use ecore-x methods instead of X11
methods.

In MakeWebKeyboardEvent, we hardcode all windowsKeyCode results, as is
currently done in quicksilver. This method is fragile, and won't work
currently on all layout keyboards. But it will still give better
results than the current behavior (where most keys are discarded, and
result in a 0 keyCode).

Additionally, we also set event.modifiers, which also used to implement
KeyBoardEvent.location.
Reviewed by: Antonio Gomes, Piotr Tworek

Change-Id: I1763ed7e43b2f216916abf75be56d0ca9ba2a84c
Signed-off-by: Arnaud Renevier <a.renevier@samsung.com>
tizen_src/chromium_impl/content/browser/renderer_host/web_event_factory_efl.cc
tizen_src/chromium_impl/ui/gfx/screen_efl.cc
tizen_src/chromium_impl/ui/ui_efl.gypi