I guess several of our WAP problem sites are legacy, old and not much visited. Some of them are maintained and may be popular, but have an unfortunate UA sniffing pattern and think mobile non-Android non-iOS browsers are WAP browsers - if any of them are popular enough to care about, we can handle them with the existing UA spoofing mechanism. So I think implementing some automatic UA switching magic isn't worth the time. -Hallvord
On Tue, Mar 31, 2015 at 12:19 AM, Richard Newman <[email protected]> wrote: > > > > One idea Brad tossed around was "if WAP received, then re-request with > > Chrome/iPhone UA to get HTML content (+ record telemetry if that fixes it > > or if we still get WAP after that)". I wouldn't mind attempting to write > > the patches for this, if we think it's worth the time. > > > > > This seems like a fine idea. For Fennec we could go so far as to request > with desktop mode, either instead of or as well as another mobile UA. > _______________________________________________ > compatibility mailing list > [email protected] > https://lists.mozilla.org/listinfo/compatibility >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
