Hi everyone, We at Mozilla have put a great deal of thought into our UAs for our mobile products, and have a reasonably good understanding of the trade- offs involved. Obviously your situation is different if you are building on WebKit, but we are very happy to share our experience and suggestions with whoever makes this decision. Drop me an email - [email protected] - if you are interested in that.
And it is a _big_ decision - because once you choose something, you are stuck with it. If you keep tweaking it, you'll break something every time you fix something, and it will get very frustrating. Getting this wrong could seriously affect the market acceptance of your product. We'd love to have people from Ubuntu join us in our evangelism efforts to make the web more multi-browser friendly. I would strongly recommend that you implement an override mechanism as a "safety valve" for sites which you can't persuade to fix themselves. It's not a magic bullet for compatibility problems, but it can help. Gerv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179596 Title: browser needs its own UA string To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1179596/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
