I also just saw this https://blog.google/products/chrome/search-your-tabs-bookmar...
I think I like the shorter Firefox version better but this is maybe easier to remember at first
I'm sitting here, recalling all my chats and meetings and workshops with UX folk, and not once can I recall the topic of keyboard shortcuts or tab sequence being brought up. It was all about color, branding, spacing, user flow, "journeys", "experience", conversion funnels, and all things visual.
(function () { let sel = window.getSelection(); let Qr; if (sel && sel.toString().length > 0) {Qr=sel.toString()} else {Qr=prompt('Search Site for','');} let hna=window.location.hostname; if(Qr) { location.href='http://www.google.com/search?&q=site:'+encodeURIComponent(hna)+'+'+escape(Qr) }})();
You can attach to a keyboard shortcut with a launcher or applescript. https://<your servicenow base url>/text_search_exact_match.do?sysparm_search=%sWhile I love the flexibility and openness that Firefox brings, there is a resource issue for me on my macbook pro. I have to spend a lot of time in Google Meets for work, and video conferencing via Firefox seems to redline the computer... It sounds like a jet engine and I wind up thermal throttling to the point that my machine becomes completely unresponsive.
I'd love to stay with Firefox - especially for the cross-device tab sharing and search - but the need for something stable is superseding my want to use a non-Google browser.
Another member recommended disabling hardware acceleration so that is the first thing I'll try. If you have any other recommendations on how I can reduce the impact of the issue I'd love to hear them.
I would have assumed that offloading the video processing to the dedicated GPU would be a good thing, but hopefully that helps with the problem.
That irritating and horrible; but until they follow that trend to conclusion, it's not a reason to switch at all.
Everyone is there for a different minority used feature. By caring only about the feature used by the majority, you are actually satisfying no one.
That’s why product managers use persona on top of metrics. Nice products have niche features and some kind of personality. You don’t want to overfocus on them but stripping them all is a losing move.
Sigh, I've been using Firefox for almost 2 decades, and this is the first I've heard of this feature.
If you only focus on the most popular features you eventually narrow your product to one feature, so obviously there is a balance in there somewhere between focus and utility as well. Identifying why people use your product is as important as knowing what they use. Chrome does all the things I actually use from Firefox, but I use Firefox because when I ever need slightly more hackability it is there for me. That is at best, a once a year occurance.
I see this so much so, it's to the point that If I see you're using something else, I assume you're not a developer, and you're likely not a power user.
And to me the context menu option to unload tabs is a killer feature.
Have I missed something?
I still manage to use TST, but part of my reason for using Firefox is just because I don't want to use anything Chromium based.
Oh, and also I don't really want to support Mozilla either so I am experimenting with LibreWolf as my secondary browser and so far it has been great.
I use Brave and yet use some complex search engines such as making POST requests to APIs based on the search input and telling the browser to open a URL provided in the API's HTTP response.
Assumably Chromes does the same (ie without some prefix searches everywhere, with some prefix —or keypress— searches in a specific category). If Chrome doesn't do that, then Firefox's is the much better UX, otherwise they're equivalent.
What I would like most on the Chrome-based browser I have to use at work is history (^ keywords) and bookmark searching (# tag keywords, or * bookmark keywords) using "awesomebar" operators that Firefox has.
I'd really really like it if a form of search keywords could be used for forms that don't work as GET requests.
There is an honest but much, much more limited attempt top bring a something similar to Chromium: [2].
[1]: https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...
[2]: https://chrome.google.com/webstore/detail/tree-style-tab/oic...
I like TST, but I gave up on it because I could never get the top tabs hidden correctly, and all the information I could find on the internet was different levels of out of date.
Some of this may be platform specific to Windows (can't speak to window management buttons on other platforms), but hopefully it helps if anyone in this thread needs it or lands here later from search results:
/* Hide the tabs within TabsToolbar*/
.toolbar-items {
display: none;
}
/* Make the min/max/close buttons align to the right*/
#TabsToolbar {
display: flex;
flex-direction: row-reverse;
}
/* Hide the titlebar spacers, which push the buttons away from the corner */
.titlebar-spacer {
display: none;
}
/* Hide the sidebar header */
#sidebar-header {
display: none;
}
Stupid that this sort of fiddling is required when other browsers (like Edge and Brave) are doing native sidebar tabs, but I do like how compact Firefox's can be, plus being a tree instead of a flat list.Enabling userChrome.css files and finding where to put it is left as an exercise to the reader.
Consider just how many layers of JavaShit webdevs want to slap down on their websites these days, that "minor" performance difference adds up. Death by a thousand cuts, basically.
To this day I cannot fathom anyone willingly switching from Firefox to Chrome/Edge/any other Chromium-based browser. There are so many tiny features that are useful at least to myself, while a minor JavaScript performance advantage isn't something that important in the grand scale of things.