Ok. The (bottom->up) flow would be something like this:
void WaylandKeyboard::Key(..)
void WaylandConnection::DispatchUiEvent(..)
bool WaylandWindow::CanDispatchEvent(..)
bool WaylandWindow::DispatchEvent(..)
void ui::DispatchEventFromNativeUiEvent(..)
void PlatformDisplayDefault::DispatchEvent(..)
...
Do you see if happening upon keypresses?
-
Antonio
On 01/11/2017 15:53, Bo Gao wrote:
> Antonio,
> Thanks for the response. Yes, the commit is in the tree.
>
> -Bo
>
> On Wed, Nov 1, 2017 at 11:10 AM Antonio Gomes <
toni...@gmail.com
> <mailto:
toni...@gmail.com>> wrote:
>
> bcc: chromium-dev
> cc:ozone-dev
>
> I imagine you have something like
>
https://codereview.chromium.org/2639053002/ in your tree?
>
> On Wed, Nov 1, 2017 at 1:58 AM, Bo Gao <
bert...@gmail.com
> <mailto:
bert...@gmail.com>> wrote:
> > I've built content shell based on ozone-wayland (chromium
> 58.0.3063.110) and facing a weird issue where no keyboard character
> can be printed, but the keys like arrows, delete, enter and etc. are
> functional. Even ctrl+c then ctrl+v can copy paste text, but simply
> pressing a key doesn't work. I've tried some JavaScript keyboard
> test page, and it captures key down and key up events, but no text
> input data. Was thinking about any issue with keymap or text input,
> but couldn't find anything related. Does anyone have any
> suggestions? Thanks!
> >
> > --
> > --
> > Chromium Developers mailing list:
chromi...@chromium.org
> <mailto:
chromi...@chromium.org>
> <mailto:
chromium-dev%2Bunsu...@chromium.org>.
> <mailto:
ozone-dev%2Bunsu...@chromium.org>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Ozone-Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
ozone-dev+...@chromium.org
> <mailto:
ozone-dev+...@chromium.org>.