6 ms·
I'm waiting for Firefox to start using a native context menu on macOS instead of the garbage that they are now using and which doesn't behave anything like any
by Hamuko 7y ago
I'm waiting for Firefox to start using a native context menu on macOS instead of the garbage that they are now using and which doesn't behave anything like any other context menu on macOS.
It's luckily on Bugzilla, so I can keep monitoring progress daily.
https://bugzilla.mozilla.org/show_bug.cgi?id=34572 https://bugzilla.mozilla.org/show_bug.cgi?id=34572
- user_50123890 7y agoTicket opened 20 years ago, damn.
- ziftface 7y ago> i can't argue, but it's a time thing You have no idea
- 0-_-0 7y agoI remember the time when I never came across anything on the Internet that was older than 3 years
- michaelbazos 7y agoThat would be the first three years of the Internet.
- 0-_-0 7y agoI'm pretty sure it was after 1972 :P
- bashinator 7y agoWow, that predates OS X.
- aasasd 7y agoYup. > Does this bug affect OS X? If not, it should be WONTFIX. > It does affect Mac OS X.
- steveklabnik 7y agoThere was a very old ticket that was closed recently when a component was re-written in Rust. I can't find a link right this second, but if you could have told the future, it's kinda amusing. "Sorry, we'll fix this, but first we have to invent a new programming language. We'll get back to you in a decade." Frankly, I think it's pretty amazing that bugs this old end up getting fixed. Not many projects live even live that long, let alone keep up their infrastructure...
- hnick 7y ago> Frankly, I think it's pretty amazing that bugs this old end up getting fixed. Not many projects live even live that long, let alone keep up their infrastructure... Our internal dev team has changed their feedback/requirements system 3 times in the last few years. Motion without moving...
- majewsky 7y agoI once fixed a bug in Kolf (the KDE mini-golf game) which was about the ball glitching through walls if you hit them in the right angle. The patch that fixed the issue was rather huge, since I ripped out the home-grown collision detection and replaced it with a standard 2D physics library. Sadly, my patch broke some custom levels which relied on the glitch. https://xkcd.com/1172/ https://xkcd.com/1172/ is more true than you'd expect.
- ziftface 7y agoI couldn't agree more. Firefox is the only browser I use on the desktop, and I do think it's the best. But the lack of native context menus is annoying. Also, other native features are missing. Like the rubber banding and pinch to zoom, although that one works okay if you switch the config entry.
- brailsafe 7y agoThis was posted not only before OSX, but before Firefox. This was just Mozilla.
- icedchai 7y agoSo what would a native context menu actually do for me?
- Hamuko 7y agoAllow the context menu to close when releasing right-click outside the menu for example. There's a ticket for that as well. https://bugzilla.mozilla.org/show_bug.cgi?id=101472 https://bugzilla.mozilla.org/show_bug.cgi?id=101472
- masklinn 7y agoServices is one which annoys me a lot. I have a few around text edition and formatting, not having them in firefox is quite inconvenient.
- catalogia 7y agoIn which ways is the Firefox context menu "garbage"? How does it behave differently? 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.
- Hamuko 7y agoThey don't close when you release right-click, they don't contain services, they don't select the word you are on. That's the stuff I've noticed in the couple of days I've been using Firefox.
- dkonofalski 7y agoOne of the things that I use a lot that isn't on there is the "Look up" function/service to get the definitions of words from the dictionary, wiki, etc. Super useful and I miss it so much after switching from Safari.
- jeremiahlee 7y agoIf you hover the cursor over the word and hit command control d, you’ll get the definition in Firefox.
- dkonofalski 7y agoThat's helpful. Thanks. Would still like for it to be in the context menu, though, but this will do in a pinch.
- 7y ago
- pier25 7y agoNot only context menus, any type of alert is garbage.
- saint-loup 7y agoI see people (legitimately) complaining about the longstanding lack of support for Mac OS native widgets but personnally I'm equally annoyed with the new behavior of menus. The standard of basically every OS is that hovering the pointer over an item opens a submenu (if there's one). In Firefox, I have to click, for instance to open "Help" in the burger menu. The sub-menu then appears by replacing the parent, instead of forming a cascade near it. It's non-standard and it's slower. The only rationale I can see for it is avoiding complex mouse paths and accidental closing of menus for absolute beginners, but still. It's not like it's not an old, solved HCI problem (see question 8). https://www.asktog.com/columns/022DesignedToGiveFitts.html https://www.asktog.com/columns/022DesignedToGiveFitts.html
- lucideer 7y agoOn the click-vs-hover issue, I actually very much like Firefox's approach, and wish it were more widely used. W.r.t. it being an "old, solved HCI problem", it isn't. The link you post actually posits positioning solutions to problems inherent to the hover approach. It doesn't discuss hover-vs-click at all, and while these positioning strategies still apply to some degree with the click approach, the problems they solve are much less severe there (namely, the submenu doesn't disappear if the user takes the wrong cursor route to a submenu item).
- tzs 7y agoThere are a couple of other non-native things Firefox does that annoy me. 1. It has its own certificate system. That would be fine if it used that in addition to using the MacOS built in system, but it seems to use it exclusively. 2. It has its own spell checker, which is orders of magnitude worse than the one provided by the native MacOS spell check API. I can't think of any program I've used in the last few years on Mac or Windows that had a worse spell checker. LibreOffice is open source and its spell checker is fine as far as I've seen--definitely way better than the one in Firefox--so that if Mozilla for some reason needs to have the same spell check on each OS and so can't use the native MacOS one, they could still bring it up to par by copying from LibreOffice.
- pilif 7y ago> LibreOffice is open source and its spell checker is fine as far as I've seen Curious. Both LibreOffice and Firefox use Hunspell
- aembleton 7y agoand Chrome according to [1]. I guess LibreOffice has a more comprehensive dictionary. 1. https://hunspell.github.io/ https://hunspell.github.io/
- Groxx 7y ago>1. It has its own certificate system. That would be fine if it used that in addition to using the MacOS built in system, but it seems to use it exclusively. fwiw Chrome does this too. It's effectively standard practice for browsers - OSes routinely have very out-of-date cert stores, and don't regularly remove revoked ones. Browsers ship it separately because it's such a major security concern for browsing.
- tzs 7y agoChrome on MacOS does use the Mac's built-in system. Going to the privacy settings (chrome://settings/privacy), and clicking "Manage certificates" just launches the MacOS "Keychain Access" application. To get Chrome on MacOS to use my employer's self-signed root certificate, I just had to import it with "Keychain Access" and then both Chrome and Safari used it. It may also have its own built-in certificate system, but for user-added certificates, it uses the built in MacOS system.