touch-packages team mailing list archive

Thread
Date

[Bug 1542375] [NEW] Get rid of the formFactor context property

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>
Date: Fri, 05 Feb 2016 15:38:10 -0000
Reply-to: Bug 1542375 <1542375@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

The Ubuntu.Web plugin exposes a 'formFactor' context property, whose
value is either "mobile" or "desktop".

It relies on QGuiApplication::platformName() to determine the so-called "form factor". With convergence, this approach is flawed, because the same device can change from a phone to a desktop and back to phone during the lifetime of the application.
Form factor is not even a concept that should be used for dynamic layout of the application.

This property is not (and has never been) publicly documented, so it
should be fine to remove it.

In most cases, where the value of that property was used, we can use one of the following:
 - wide VS narrow mode
 - presence of a mouse/touchpad/touchscreen/keyboard
 - can a given QML plugin be dynamically loaded

** Affects: webbrowser-app (Ubuntu)
     Importance: High
     Assignee: Olivier Tilloy (osomon)
         Status: In Progress

** Branch linked: lp:~osomon/webbrowser-app/remove-formFactor

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1542375

Title:
  Get rid of the formFactor context property

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu.Web plugin exposes a 'formFactor' context property, whose
  value is either "mobile" or "desktop".

  It relies on QGuiApplication::platformName() to determine the so-called "form factor". With convergence, this approach is flawed, because the same device can change from a phone to a desktop and back to phone during the lifetime of the application.
  Form factor is not even a concept that should be used for dynamic layout of the application.

  This property is not (and has never been) publicly documented, so it
  should be fine to remove it.

  In most cases, where the value of that property was used, we can use one of the following:
   - wide VS narrow mode
   - presence of a mouse/touchpad/touchscreen/keyboard
   - can a given QML plugin be dynamically loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1542375/+subscriptions