Basically this task is to follow-up with the change from , and do the same in WAM or chromium, instead of letting the compositor perform the activation by default at start-up.
This means that chromium should gain v3 for agl-shell protocol and with it to use the events from the compositor to activate the application at the first start-up.
if this is fixed could you please close this? Do you need this open for the CEF version?
Marius Vlad
December 13, 2022 at 2:54 PM
I have an implementation for this as well, but it is not using any of the logic in chromium to actually make use of it.
https://paste.debian.net/1263932/ what is missing is to use these calls to deliver events either to Chromium itself or to WAM. Probably easier to just let chromium handle.
The changes added by in the following would probably need to be modified as to use these events:
Similar to what we did in homescreen, https://gerrit.automotivelinux.org/gerrit/gitweb?p=apps/homescreen.git;a=commit;h=52c767388614e2ec6fa26851840bf01d97c5d49e
we would let the client perform the activation rather than the compositor doing it by default.
Basically this task is to follow-up with the change from , and do the same in WAM or chromium, instead of letting the compositor perform the activation by default at start-up.
This means that chromium should gain v3 for agl-shell protocol and with it to use the events from the compositor to activate the application at the first start-up.