HTML5 fresh image showing broken homescreen

Description

On a clean boot of a fresh image of the HTML5 demo platform on the M3, we have been able to reproduce the problem mentioned by Scott, of a wrong rotated view of the web homescreen, using just half of the available resolution and overlapping the launcher.

We are investigating the possible cause for the issue, as it seems not completely deterministic (apparently reflashing the same image was showing the correct behavior).

Environment

None

Attachments

4
  • 13 Feb 2020, 11:49 AM
  • 13 Feb 2020, 11:49 AM
  • 13 Feb 2020, 11:36 AM
  • 13 Feb 2020, 11:36 AM

Activity

Scott Murray 
February 18, 2020 at 11:39 PM

I tested a build of latest master with your change, and it booted up to homescreen fine in landscape mode.

Lorenzo 
February 17, 2020 at 1:59 PM

We think so. Starting by default with the landscape resolution seems to avoid hitting this issue on a fresh image. However, we are still looking into why when in some cases showing the portrait HTML5 homescreen is not working as expected.

Jan-Simon Moeller 
February 17, 2020 at 1:30 PM

Should we pull this into icefish ?

Antia Puentes 
February 13, 2020 at 11:50 AM

When the bug happens, the homescreen thinks it is in landscape mode, as you can see in attached picture homescreen.jpeg (taken before the launcher is shown). The launcher however, has the correct orientation (portrait) and once it is launched, hides partially the incorrectly oriented homescreen bar (homescreen-and-launcher.jpeg picture).

This is easily confirmed using the webinspector, as you can see in the attached pictures webinspector-*.png

Antia Puentes 
February 13, 2020 at 11:15 AM

Setting the weston.ini to horizontal and adjusting the areas.json to horizontal parameters (done basically switching the width and height values) I do not see any anomaly.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Hardware Platform(s) Affected

Renesas M3

Affects versions

Priority

Created February 12, 2020 at 10:18 PM
Updated April 7, 2020 at 5:10 PM
Resolved March 2, 2020 at 9:03 AM

Flag notifications