Re:Firefox Android now supports tampermonkey
by Zuiii on Friday February 17, 2023 @05:30AM
(#34833032)
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?
[ Parent
| on HN ]
Re:Firefox Android now supports tampermonkey
by cma on Friday February 17, 2023 @07:47AM
(#34834001)
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.
Re:Firefox Android now supports tampermonkey
by ohgodplsno on Friday February 17, 2023 @08:51AM
(#34834609)
Feel free to implement this in HomeActivity::onKeyDown. (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.
Re:Firefox Android now supports tampermonkey
by Zak on Friday February 17, 2023 @10:06AM
(#34835481)
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.
Re:Firefox Android now supports tampermonkey
by ohgodplsno on Friday February 17, 2023 @10:45AM
(#34835957)
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.