5 ms·

And also also, why they block the ability to run devtools directly on mobile. It's an incredibly sad state of affairs that I have to use a chromium fork to do s

by Zuiii 4y ago

And also also, why they block the ability to run devtools directly on mobile. It's an incredibly sad state of affairs that I have to use a chromium fork to do something that was pioneered on Firefox. Why do Mozilla keep shooting themselves in the foot like this?

cma 4y ago
And why is mouse/keyboard and stylus support so bad on mobile? Most of the normal browsing hotkeys don't work, even though people can use that setup a good bit with tablets and foldables.
- ohgodplsno 4y ago
  Feel free to implement this in HomeActivity::onKeyDown. (https://github.com/mozilla-mobile/firefox-android/blob/ce68e6f88e8bbfe096f4843c6f393f259dde6248/fenix/app/src/main/java/org/mozilla/fenix/HomeActivity.kt#L746 https://github.com/mozilla-mobile/firefox-android/blob/ce68e...). Check for the appropriate modifiers on your key event + R, and call components.useCases.sessionUseCases.reloadUrl(). Why is it so bad ? Because noone uses a keyboard on mobile. Because if they had spent time implementing any other features that are used by 0.0001% of users, you'd have been complaining that Mozilla is wasting their money on not making a better browser.
  - Zak 4y ago
    Web developers are, indeed a tiny fraction of the overall userbase for web browsers. Why browser makers might want to cater to their needs anyway is left as an exercise for the reader.
    - ohgodplsno 4y ago
      Why browser makers might not want to cater to web developers wanting to use a keyboard on a platform that is used at 99.9% through touch controls, platform on which we both know they neither develop on (when is the last time you made a website on your tablet?) or even test on, is indeed left as an exercise for the reader.
      - Zak 4y ago
        Testing websites on actual mobile devices is generally advisable. Testing them in a niche browser, perhaps not so much, but more people will if that browser makes it easy.
  - cma 4y ago
    Tablets often come with keyboards.

by Zuiii 4y ago

cma 4y ago

And why is mouse/keyboard and stylus support so bad on mobile? Most of the normal browsing hotkeys don't work, even though people can use that setup a good bit with tablets and foldables.

ohgodplsno 4y ago
Feel free to implement this in HomeActivity::onKeyDown. (https://github.com/mozilla-mobile/firefox-android/blob/ce68e6f88e8bbfe096f4843c6f393f259dde6248/fenix/app/src/main/java/org/mozilla/fenix/HomeActivity.kt#L746 https://github.com/mozilla-mobile/firefox-android/blob/ce68e...). Check for the appropriate modifiers on your key event + R, and call components.useCases.sessionUseCases.reloadUrl(). Why is it so bad ? Because noone uses a keyboard on mobile. Because if they had spent time implementing any other features that are used by 0.0001% of users, you'd have been complaining that Mozilla is wasting their money on not making a better browser.
- Zak 4y ago
  Web developers are, indeed a tiny fraction of the overall userbase for web browsers. Why browser makers might want to cater to their needs anyway is left as an exercise for the reader.
  - ohgodplsno 4y ago
    Why browser makers might not want to cater to web developers wanting to use a keyboard on a platform that is used at 99.9% through touch controls, platform on which we both know they neither develop on (when is the last time you made a website on your tablet?) or even test on, is indeed left as an exercise for the reader.
    - Zak 4y ago
      Testing websites on actual mobile devices is generally advisable. Testing them in a niche browser, perhaps not so much, but more people will if that browser makes it easy.
- cma 4y ago
  Tablets often come with keyboards.