No browser screen shown up with WAM and Browser App with chromium68

Description

* Chromium68: https://github.com/webosose/chromium68 (branch: @15.agl.flounder)
* WAM: https://github.com/webosose/wam (branch @2.chromium68.5.agl.flounder)
* meta-agl-lge: https://github.com/webosose/meta-agl-lge (branch flounder.chromium68)

With the current recipe with chromium68, we can't see the screen updated from WAM and Browser App.

Environment

None

Activity

Walt Miner

February 11, 2019 at 11:11 PM

Close for FF 6.0.4 and GG 7.0.0

Julie Kim

December 19, 2018 at 3:13 AM

With the change above, we can run web apps and see the app screen with the upstream wayland port.

Julie Kim

December 18, 2018 at 3:05 PM

https://github.com/webosose/chromium68/pull/5

Maksim Sisov

December 18, 2018 at 1:07 PM

Updated: it turned out SetWindowSurfaceId was missed because it was silently implemented in interfaces and has never been propagated to WaylandWindow.

Maksim Sisov

December 17, 2018 at 3:20 PM

It looks like it’s related to the above issue. I can’t get browser working with ivi shell, but rather with xdg shell.

I’m able to run the browser within ivi shell environment with runxdg, it’s not a problem. But will it be suitable for running wam through runxdg?

Right now, updated chromium68 with upstream Wayland backend is able to be run through runxdg as a stand-alone browser, but not within ivi shell

Regarding to the system libwayland - it’s not the same Issue

Resize work item view side panel

Fixed

Details

Assignee

Maksim Sisov

Reporter

Julie Kim

Priority

Major

Created December 13, 2018 at 9:17 AM

Updated February 11, 2019 at 11:11 PM

Resolved December 19, 2018 at 3:13 AM

No browser screen shown up with WAM and Browser App with chromium68

Description

Environment

Activity

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Priority