On Fri, Jun 6, 2014 at 6:46 PM, Elad Alfassa <elad@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Jun 6, 2014 at 7:37 PM, drago01 <drago01@xxxxxxxxx> wrote: >> >> On Fri, Jun 6, 2014 at 6:20 PM, Elad Alfassa <elad@xxxxxxxxxxxxxxxxx> >> wrote: >> > >> > >> > Even after the GTK3 port is done, High-DPI and touch input support won't >> > be >> > supported (at least, not anytime soon). How can we advertise high-dpi >> > and >> > touch input support as features of our product if our default web >> > browser, >> > arguably the most important app for most users, doesn't support them? >> >> This is not really true. >> >> HIDPI works really well (I have a hidpi laptop here) just not out of >> the box already. Firefox has a scale factor that you can set. It is >> set to -1 by default it should just be >> set to whatever the xsettings value is (which shouldn't be that hard to >> do). >> >> > Allow me to answer your comment with three links, as you said it "shouldn't > be hard": > > http://xkcd.com/1349/ > https://bugzilla.mozilla.org/show_bug.cgi?id=975919 > https://bugzilla.redhat.com/show_bug.cgi?id=1060770 Non of those links contradict what I said. So once again: 1) Firefox high dpi support works pretty well already if configured correctly (also stated in one of your bugs); "Perhaps. But a gtk2 build works pretty well on my high DPI laptop running Fedora 20." 2) To configure it correctly we just need to set one value 3) We already compute the desired value and export it through xsettings 4) Reading an x settings value is not rocket science Which part is wrong? None. > Also, high-dpi support is only one issue out of two I raised here, Where did I state this is the only issue? > My point in this thread is that Firefox should either be improved, or > replaced - the current situation is far from being ideal. We should improve it. The alternatives are worse (both epiphany and chromium). -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
