To support a converged desktop scenario, the browser user agent string needs to be recalculated as the form factor changes. Currently it is set, according to a set of heuristics, at startup time, and not re-evaluated during the lifetime of the browser app.
There are some more aspects to that bug.
1. What are the heuristics for determining the form-factor, and which form factors to support? Ideally, this is an SDK API we can just re-use.
2. When should the UA be updated? Again, ideally this would be on form factor changes, based on a signal. So which service will deliver that signal?
3. The overrides need also to be dynamic as well, so how many sets are supported, ie depending on the set of form factors supported, we need as many overrides
4. This extends to not only webbrowser-app but more importantly webapp-container, where overrides are a lot more widespread, and not centrally maintained
5. When the UA and / or the form factor changes, parts of webbrowser-app or webapp-container may want to further react, for example to reload the page.
Status changed to 'Confirmed' because the bug affects multiple users.