Firefox does not install on Android on a chromebook with no touchscreen
Firefox app does not follow Google best practice guidelines - see
https://developer.android.com/distribute/best-practices/engage/optimize-for-chromebook.html
"Best practices
Update your app's manifest file. Account for some key hardware and software differences between Chromebooks and Android devices. For example, adjust the settings so that the android.hardware.touchscreen feature is not required. Also ensure that none of the sensors are required if you want to run on any Chromebook regardless of the sensors it supports. "
The FF manifest file still contains ""android.hardware.touchscreen" set to "Yes" - it should be set to "no" so that Firefox can be installed on Chromebooks having non-touchscreen screens. I would have thought this would be the work of a moment for a developer. And it would help to bring Firefox right into the heart of Chrome territory! ;)
Tất cả các câu trả lời (3)
The Android Firefox is not being made with Chromebooks in mind as it is made for actual Android tablets and phones.
There is only two bugs for Android Firefox on Chromebooks. So Chromebooks is not a priority. Bug 1387936 - Chromebook running Play Store listed as "not compatible with this version." Bug 1335510 - Touchpad scrolling doesn't work on Chromebook
Thanks for your prompt response.
Bug 1387936 - Chromebook running Play Store listed as "not compatible with this version."
This is in essence what I'm reporting - the code change necessary to fix this is to set "android.hardware.touchscreen" to "Yes" - End of bug, and I doubt whether that would cause any problems for phone or tablet users who almost by definition have touchscreens anyway.
Google are thinking in terms of Chromebooks becoming replacements for tablets, from what I read. It seems to me worth FF keeping up with this trend, especially as the effort required should - I repeat, should - be minimal. If I could install FF on my Chromebook then I could see whether the other bug you mention applies, and whether I can see a possible cause - it shouldn't happen (judging by other apps on CB which are fine).
And of course, it must be tempting to take FF into the heart of 'enemy' territory, But maybe you guys have minds above such pettiness! :)
A "C-" workaround is to download Firefox and run with screensize enlarged and Request Desktop Site = Off. 4-way arrows do work and permit somewhat jerky scrolling. Bookmarks functions/actions are unavailable. Chromebooks were the fastest growing device type in 2016, 2017, 2018 to date in part because unlike most tablets, they have USB 2.0,3.0, and 3C ports for unlimited storage offline, provide typing as well as mouse and touchscreen navigation, are cheaper, and are administrated easily en masse for schools, libraries, and many service organizations. Not making Chromebooks a FF priority is like countries preparing to fight WWII by focusing on WWI technologies.