Dietrich, Le 21 oct. 2015 à 01:37, Dietrich Ayala <[email protected]> a écrit : > I'm not totally sure that we're falling on the right sword by not making the > Web work for our users at whatever cost, while working in parallel to change > things through other channels.
It's exactly what we are doing. Trying to fix things where we can for the users. See the aliasing of some CSS/JS properties, innerText, etc. I could explain a bit more what's happening on this front for the last year, if interested. On the other hand, the UA string is a tad more difficult than it seems at first. When changing a UA string specifically for solving a simple issue, we often create in the same shot plenty more issues. So let's say, we modified the UA string so we receive the beautiful icon, and then we are sent to JS codepath, server side template, CSS targeted to the WebKit/Blink users and it becomes a real mess. We know what we fix, not what we break. http://www.otsukare.info/2013/11/08/ua-override -- Karl Dubost, Mozilla http://www.la-grange.net/karl/moz _______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
