19 ms·
17 year old Firefox feature request fixed
- clarifier123 6y agoWow, that's a feature that I've been really missing since I switched to Firefox from Opera.
- brundolf 6y agoWow, finally
- deleted 6y ago[deleted]
- w-m 6y agoNot to get too greedy, but maybe do the 21 year old “Use native context menus on Mac OS” next? https://bugzilla.mozilla.org/show_bug.cgi?id=34572 https://bugzilla.mozilla.org/show_bug.cgi?id=34572
- flukus 6y agoMaybe just do native UI's completely, especially now dropping XUL has broken everything.
- ripdog 6y agoThere's no way Mozilla is going to rewrite their entire UI layer for a single OS, much less a minority one.
- cle 6y agoLooks like it's in progress. Also native "rubberband" scrolling in macOS is in progress as well. Excellent!
- Klonoar 6y agoMaking it also respect dark mode in alerts would be nice.
- bartvk 6y agoYup, I'm waiting for that one as well. Open/save/print dialogs seem to be using native components, but I'm guessing they link to old versions of AppKit because they don't respect the system setting for dark mode either. But all in all, I'm pretty happy with Firefox. This is a very minor thing for me.
- ziftface 6y agoThis makes me very happy. It sounds dumb but I've considered switching from Firefox just because of the context menus.
- pseudalopex 6y agoWhy is jira.mozilla.com private?
- forgotmypw17 6y agoAlso, why is there a jira.mozilla.com at all, and why is there a jira.mozilla.COM?
- jaas 6y agoIt’s probably private because it is used for internal systems. It’s probably .com because it’s for Mozilla Corporation as opposed to Mozilla Foundation.
- seppel 6y agoStill interesting that they internally dont use bugzilla. I wasnt aware.
- dralley 6y agoI suspect the vast majority of bugs are exclusively using Bugzilla. Maybe they use Jira for roadmapping or security bugs.
- pseudalopex 6y agoOther open source projects plan in public. Bugzilla can restrict viewing security bugs.
- dralley 6y agoFew other open source projects are as large as Firefox.
- pseudalopex 6y ago
- Ninjinka 6y agoThat's older than me
- Lammy 6y agoI really miss Camino.
- wpm 6y agoNow that’s a name I’ve not heard in a long time.
- ArteEtMarte 6y agoYup, a long, long time ago, in a galaxy far, far away. For its time it was a great little browser. I was going to do some bug fixing on it. But then I saw that it required Corba ORB to build. So I let out a long, low moan and, shivering uncontrollably, filed that dream under never going to happen.
- ihuman 6y agoIs that talking about the right-click menus, or something different? The right-click menus look and act native to me.
- pseudalopex 6y agoIt's the right click menus.
- pfranz 6y ago99% of the time I use "Look Up" which is the top item in native macOS context menus (for selected text). It's really annoying when your browser is missing it. This is likely a separate ticket, but Firefox ignores macOS' built-in text replace which I use for expanding text like my email address.
- dstaley 6y agoThis is what the right-click menu looks like in Firefox on macOS [1]. Compared to the right-click menu from Safari on the same machine [2], you can see several differences. The most notable one is that the Firefox menu is not theme-aware, rendering a light-themed context menu even though the OS is in dark mode. Next, the padding around the menu is incorrect compared to a native menu. It also looks like the font is maybe a different size. Finally, the drill-down arrow on the Firefox menu doesn't match the native one. [1] https://ibb.co/0hRpSBB https://ibb.co/0hRpSBB [2] https://ibb.co/wwhCypT https://ibb.co/wwhCypT
- ziftface 6y agoI also want to add that the behavior is different: holding the right mouse button then releasing closes the native context menu, but doesn't close the Firefox context menu. Going into "mission control" closes the native context menu, but not the Firefox context menu. There are a few other differences as well. Basically, they are not at all the same.
- Hamuko 6y agoI've been following this and there's been a lot of activity there lately. Let's hope we get it before its 25th anniversary.
- dingaling 6y agoOr the eight-year-old "can't import certificates into mobile Firefox" which makes the browser unusuable in several contexts: https://bugzilla.mozilla.org/show_bug.cgi?id=868370 https://bugzilla.mozilla.org/show_bug.cgi?id=868370
- cassepipe 6y agoFantastic. There's hope. (Greed incoming beware). What about WebMIDI support for music web apps like Pianojacq?
- nonbirithm 6y agoObligatory dogpile, but I'm hoping for the day you can disable Ctrl-Q to prevent accidentally closing the browser with a single keystroke. It's impossible to do on Linux.
- IshKebab 6y agoYeah Chrome's "hold to quit" feature is genius. I wish VSCode had it too.
- fingerlocks 6y agoYou can hack it in VSCode by turning on the warn-before-terminal-closed feature, and making the terminal always load. Only drawback (maybe) is that every open project in VSCode warns when trying to close the entire app.
- deleted 6y ago[deleted]
- ryandrake 6y agoUggh. I pretty much never use Chrome on my Mac, but when I borrow someone else's computer and want to quit Chrome I always get bit by this one! No other application have I seen that makes you hold down ⌘Q to quit, except for Chrome. This is not conventional on Mac apps! It's probably configurable but why make it the default?
- IshKebab 6y agoBecause nobody would know it even existed if it wasn't the default and it's a great feature!
- scotu 6y agoI'm on mac, but I used to have the same problem also in other apps: I use a system wide app that makes you long press cmd-Q to quit any app (with an allow/block list): "SlowQuitApp". Just in case you never thought to try to find something similar (assuming ctrl-q is a common shortcut in linux, I forgot)
- clankyclanker 6y agoGood on them for actually tracking this feature request for over a decade and not just closing it after three weeks for “lack of interest.” Looking at you, every random GitHub project ever.
- leppr 6y agoHaving a revenue stream helps.
- Denvercoder9 6y agoDoes it? It's not like you're paying GitHub per open issue. I've literally had issues I filed that the maintainer verified as an actual bug be closed due to lack of activity. I can understand that an unpaid maintainer doesn't have the time or motivation to fix it, but closing issues you know are valid seems insane to me.
- acdha 6y agoIs it a human closing it or a bot? If you run an open source project there's a natural tendency to install a bot to auto-close all of the issues which people open because they didn't read the docs, want you to do free consulting for their business, have an irreproducible bug report, etc. and since most projects are short on labor that makes it somewhat inevitable that someone will enable the bot first and never get around to configuring it to, for example, not close an issue tagged as verified.
- Denvercoder9 6y agoA bot, but > someone will enable the bot first and never get around to configuring it to, for example, not close an issue tagged as verified. I don't understand this part. Aside from the fact that it's trivial to exclude certain tags (it's the same config file, and it's in the first example they give), doing this effectively makes your issue tracker useless as an issue tracker. Why not completely disable the issue tracker instead then?
- dragosmocrii 6y agoIf you're like me, and read the comments first, this change is about giving feedback on the scrollbar for a search. In other words, when you search for something, the scrollbar will give an idea how many results there are, and where on the page rhey are located. On another note, the comment uses IntelliJ as an example. Wow, that was 17 years ago! Happy to see my favorite editor be around for so long.
- smitty1e 6y ago> 17 years ago "Nearly half my age," said Emacs.
- hughw 6y agoWait is Emacs lying about its age again?
- wilsocr88 6y agoEmacs was released in 1985. That's 36 years ago. Half of that is 18. What am I missing?
- agumonkey 6y agoare we off by one ?
- intrasight 6y agoI was using Emacs in 1982, and it had been around for several years before that.
- herodoturtle 6y agoI love it when old-timers weigh in on HN comments. What do you use these days?
- 6y ago
- batisteo 6y agoI'd look for a ticket about the poor contrast of matches, either green or magenta.
- raymondgh 6y agoIt’s also interesting that the context of this bug has changed over the years. I’d be surprised to learn if we had gigantic single-page api reference docs 17 years ago
- wongarsu 6y agoOn the other hand the tutorials I remember following back in the days were quite long and all in one page, while today those tend to be split into annoyingly many pages.
- edoceo 6y agoFor more ad serves. F the modern web.
- iFreilicht 6y agoNah, docs in general are just very big these days, it makes quite a bit of sense to not load all of them into one single page. I do like that I can search all of pandoc's documentation with just Ctrl+F, but that's not reasonable for all software. Heck, even man pages are split up into many pages for more complex tools.
- Trufa 6y agoI am never really sure how this feature is helpful, I don't know if I'm being obtuse about the functionality that people give it. In the JetBrains software I use it all the time but only cause it's clickable.
- gdrift 6y agoOne of the most voted for issues is closed WONTFIX: single click selects all in address bar and search box. I use Firefox exclusively and this is the single most annoying change they made for no apparent reason. So annoying. https://bugzilla.mozilla.org/show_bug.cgi?id=1621570 https://bugzilla.mozilla.org/show_bug.cgi?id=1621570 https://bugzilla.mozilla.org/buglist.cgi?votes=133 https://bugzilla.mozilla.org/buglist.cgi?votes=133
- Spivak 6y agoEven if you disagree with the reason might as well give the devs’ stance on it. > it [single clicking not selecting all] was a special behavior only implemented for Linux, it was not consistent with Firefox on other OSes, and with other browsers on Linux itself. The prefs were causing broken edge cases complicate to handle, taking into account all the possible pref combinations (for example under certain combinations it was not possible to select a word), and having to execute more tests for them. Not removing the prefs would have not saved many resources, since we still need to maintain them. Why can’t you just have both options? > Most of the tests should then be able to run with both setups, everytime we touch something around that we'll have to check not breaking it, and so on. Yes, even the simplest pref skipping a line has a cost, and that's why they must be weighted with a benefit. > Apart from what I already said regarding the will to unify the behavior for the more commonly found case of users moving across OS and browsers, and the cost of options in general, I'd like to explain a further reason why it's not just matter of reintroducing a pref; the change we made here will allows us to experiment more broadly with the unfocused Address Bar contents, for both UX and security reasons. Keeping browser.urlbar.clickSelectsAll around would make experiments a lot more problematic, and at a certain point we may have to remove the pref regardless, because it would block landing improvements. So we'd end up causing you frustration twice. We totally understand your point of view on this matter, unfortunately sometimes changes must happen, to be able to evolve things.
- teknopaul 6y agoWontfixzilla with comments disabled is a clear statement. Is a wontfix with lots of comments more expensive, than a wontfix with comments blocked? Shame you cant "give the devs opinion" on bugzilla.
- dbg31415 6y agoCool, at that rate only another 16 years or so until they'll fix the fact that running a Zoom or Hangout call on Firefox turns your MBP into a toaster. Wish they'd focus on battery use! It's so crazy un-optimized. Run your next Zoom call on Firefox and put your laptop on your lap to test... Or just watch the battery meter plummet vs. other browsers.
- wtf77 6y agothere is always hope
- layer8 6y agoI hope they also finally allow black on yellow highlighting again (like pretty much every other browser), which hasn’t been possible since Firefox 3.5 in 2009. https://bugzilla.mozilla.org/show_bug.cgi?id=505089 https://bugzilla.mozilla.org/show_bug.cgi?id=505089 http://forums.mozillazine.org/viewtopic.php?p=7018785 http://forums.mozillazine.org/viewtopic.php?p=7018785
- slim 6y agobtw black on yellow is used for the <mark> tag. it makes sense to not use the same colors for firefox chrome
- ufo 6y agoDoes anyone know were we can find a screenshot of this new feature in action?
- bilekas 6y agoComment 6 • 15 years ago : > I'm going to take this bug so maybe someday I can do it. Way too hard for now, but it would be very nice to have. Now that's persistence!
- dsjoerg 6y agoSee! You just had to be patient!
- abridgett 6y agoI'm immensely grateful to the developers involved. I'm sure it wasn't easy but it's one of those features that I've always missed ever since chrome added it. It also shows the value of a decent bug tracking system.
- gamesbrainiac 6y agoI just love how the first comment is about how IDEA has this feature.
- zippercreatemy 6y agoPoor Keith, reported it 17 years ago and then vanished in 2005 missing out on the long journey of his feature request. https://bugzilla.mozilla.org/show_bug.cgi?id=259640 https://bugzilla.mozilla.org/show_bug.cgi?id=259640
- zippercreatemy 6y agoLooks like is now Software Engineer at Stripe. I hope someone lets him know his ticket is closed.
- efwfwef 6y agoso still not the fix for tree style tabs...
- jacquesm 6y agoGood. Can we have webmidi next?
- iFreilicht 6y agoDon't we already? I thought I used that before.
- jacquesm 6y agoNot on FF in the standard config. Chrome yes. Webaudio does work, maybe that confused you?
- account42 6y agoHopefully not. The less surface area browsers expose the better.
- jacquesm 6y agoI've got just the thing for you: https://en.wikipedia.org/wiki/Lynx_(web_browser) https://en.wikipedia.org/wiki/Lynx_(web_browser)
- ggm 6y ago17 years is pretty good. I had BSD gnats bugs 10+, which I would have loved to be fixed, but the BIOS in question (it was ACPI stuff) is long dead. However, similar bugs persist in modern hardware/software "layer 2" systems under the OS. They're just hard to fix, without NDA. The entire 802.11 blobs story, is about persisting "if we knew how the magic FPGA works we'd fix this" stories.
- notorandit 6y agohttps://bugzilla.mozilla.org/show_bug.cgi?id=915 https://bugzilla.mozilla.org/show_bug.cgi?id=915 It is older!
- Arnavion 6y agoThat was a WONTFIX, not FIXED.
- notorandit 6y agoTry reading carefully. It's we don't know how to fix and just wait until it will disappear.
- Arnavion 6y agoI read it just fine. Thanks for your concern though.
- deleted 6y ago[deleted]
- pjmlp 6y agoGreat, now maybe they can fix the size of adding bookmarks window. https://bugzilla.mozilla.org/show_bug.cgi?id=219972 https://bugzilla.mozilla.org/show_bug.cgi?id=219972 My favorite bug, 18 years old, closed without replacement.
- wasmitnetzen 6y agoThe bug you linked is about the properties window of an existing bookmark, which is resizable.
- pjmlp 6y agoI might have linked the wrong one, it doesn't change the fact that the window still isn't resizable and there is a bug of similar age buried in bugzilla.
- coldtea 6y agoThat's what I love about FOSS! If a program doesn't have the feature you like, it can always be added -- 17 years later.
- jobigoud 6y agoI love this about the internet in general. It could have been possible for the person that implemented the change to be born after the request was even made. All the while the discussion thread was maintained alive, while that person would be going to school and learn to code. Similarly you can post a very specific question on a forum and it's possible the person that will answer it casually many years later as if they were just continuing the discussion wasn't even born when you posted the question. These extremely asynchronous interactions between strangers are something unique. I wonder what's the current record for longest lived discussion thread like this, or the question-answer pair with the longest interval. A bit like the open-ended questions in academia that are answered decades later.
- __michaelg 6y agoStill sad that https://bugzilla.mozilla.org/show_bug.cgi?id=14328 https://bugzilla.mozilla.org/show_bug.cgi?id=14328 was closed 2 years ago after being open for 20 years.
- zecg 6y agoNow Mozilla, bloody Firefox for Android cannot save the page anymore - not as MHTML, not as PDF. How can such a basic function just disappear?
- charcircuit 6y agoBecause not many people use it. I don't think many people have the desire to save a whole web page. For other unseen you can probably just get away with taking a screenshot, sending the tab / sharing the link, or using an archiving site to save it for later.
- yosito 6y ago"Because not many people use it" was the excuse Google gave for killing RSS.
- pwdisswordfish6 6y agoGoogle Reader ≠ RSS.
- baud147258 6y agoRSS is dead? * check own RSS feeds * Nope, still alive
- zecg 6y agoI certainly don't use it since it's gone, I have to save pdf on desktop and then rsync it to the phone.
- nashashmi 6y agoI used that all the time. Saving an entire webpage as just one single file with all images and resources embedded was a terrific way to archive pages and resources in research. Of course pdf was works great too but you lose the flow of a browser.
- firexcy 6y agoI also find this painful and have switched to iceraven, a fork of Firefox Android that supports arbitrary addons, and use SingleFile to save webpages as html files.
- iggldiggl 6y agoOf course, there used to be an add-on that added this functionality, but was subsequently killed by the 57 update.
- nashashmi 6y agoThis was a feature that appeared in chrome way back when and was what made me switch. Always felt Firefox search was inferior because this was missing.
- mschaef 6y agoNit-picking here, but language is important. Not sure I like the idea that a "feature request" can be "fixed". It's a feature, not a bug. It's a request, not some sort of obligation of the development team. Still though, it's good to see a process work over a 17 year long period, in an industry where things oftentimes seem to be thrown out in a matter of a few years.
- Railsify 6y agoI wonder what Keith Lea is up to these days. Someone should let him know this is implemented!
- firexcy 6y agoGlad they finally add this. Used to be a painful lack compared to chromium-based browsers. During the long wait I've found this amazing addon called HighlightAll [1], which allows you to search multiple keywords and highlight them with different colors; the position will also be labelled on the scroll bar. Super helpful for researching/consuming long articles. [1]: http://jgoudey.free.fr/highlightall/ http://jgoudey.free.fr/highlightall/