Don't be so dismissive. Apart from anything, that breaks one of the HN guidelines for discussion.
Not having access to built-in and user-defined (Applescript/Automator) Services is not trivial; these are a powerful part of what makes macOS unique and a major reason why I continue to use macOS. Their lack of availability is entire down to using faked-up menus rather than proper widgets.
Having widgets behave improperly is also an accessibility issue. There are multiple accessibility APIs built into the system that practically every macOS app built using Cocoa or Carbon hook into automatically; apps that use non-native widgets that don't take enough care to (a) perfectly emulate the behaviour of native widgets or (b) sufficient expose themselves to the built-in accessibility APIs not only make for an unexpectedly unpleasant experience but also potentially are showstopping for people with disabilities.
> But to my eye they look damn close to native and they seem to work perfectly fine
In other words, it's not a problem for you, so it shouldn't be a problem for anybody else.
It's under the Firefox menu. I use it frequently to trigger an Automator service for TTS, which pipes the text through a sed script to fix common mispronunciations. I use this stuff too.
Should it be in the right click menu? Yes. Is firefox crippled by it's absence? No, because that functionality still exists, just in a different location (and if you have your services bound to keyboard shortcuts it becomes a complete non-issue.)
I stand by what I said. I'm not being unreasonably dismissive. Many mac users on this forum in particular have a habit of blowing the slightest defect completely out of proportion. Maybe they're trying to emulate Steve Jobs' infamously toxic approach to critique. Calling firefox "garbage" because of defects these minor is a prime example.
I’ve used Firefox since Chrome started threatening to block ad blockers. I have stopped recommending it.
This specific bug confused the hell out of not only my parents, but also multiple nieces and nephews in their teens. (They thought it crashes.) These age groups both spend most of their time on mobile. When a desktop app behaves unusually, it’s a massive burden.
Not fixing these bugs seems to be a cultural problem at Mozilla, albeit one that’s getting better.
Forgive me for being incredulous, but what are they using it for? While I use Services, I'm not under the impression that it's particularly common. Perhaps Mozilla haven't prioritized the matter because they, like myself, are wrong about that? (And maybe calling Firefox garbage isn't the best way to correct their cultural blindspot?)
That's the stuff I've noticed in the couple of days I've been using Firefox.
I never even noticed that it's not native until I read your comment, and looking carefully at it now the only difference I can notice is the corners are square (and that is certainly nothing worth complaining about.)
Maybe I'm just an oblivious idiot, but it sure seems to me that a lot of MacOS users on HN love to blow trivial matters completely out of proportion. Application lags for a split second? "Utter garbage, the developers should be shot, I'm going back to Safari." Where is the perspective? If there is something glaringly broken about these context menus, by all means correct me. But to my eye they look damn close to native and they seem to work perfectly fine.