> Also, how does this play into the converged future? The default UA depends on the form factor. The "like Android" token is present only on mobile devices. This is not dynamic yet, but will be eventually.
> And finally, sites really should not be using the User-Agent to > decide what data to send in response. But they do (an overwhelming majority of websites and webapps out there anyway). While I agree with your statement, it’s only wishful thinking and won’t help solve the problem with a finite amount of time and resources. Note that Mozilla is advocating for detection of the "mobile" keyword only to identify mobile devices. While not ideal, this is already a huge step forward compared to the current situation. But in practice it is a very tedious and time consuming process, with limited results. The approach we’re taking with webbrowser-app in Ubuntu is a pragmatic one given the constraints and user expectations. It certainly isn’t the cleanest solution, and it does have a number of drawbacks. Realistic suggestions to improve the situation are very welcome. I’m fine with leaving this bug open (we can actually use it as a reference to explain the rationale behind the current approach), although I hope you understand that given how complex the situation is there’s very little chance it will ever be "fixed". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328183 Title: User-Agent string results in poor UX on web To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1328183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
