831–840 of 1001 posts
Google will keep locking down Chrome and using corporate talk to hand wave it away, only recourse is to leave. First it’s “sign in” with obtuse ways to turn it off. Then block Adblocking, once again with obtuse ways to disable... the end goal is pretty obvious, get the majority of Chrome users to turn on ads and tie their real names to their Chrome browser. Of course let “power users” (who’ll turn that crap off anywa…
It is so clear to me that we need to support and promote mozilla and Firefox. They're not perfect, but they, wikipedia, eff, archive.org (who else?) are such an important part of the Internet guardianship in the face of the monopolies, that it's our duty to support them. Doesn't hurt that Firefox is actually a great product.
> Doesn't hurt that Firefox is actually a great product. Arguably. On these threads there is always a handful of complaints about the state of Firefox, mostly on macOS. On my machine, I can’t even launch Firefox in headless mode without the fans turning on, which never happened on Chrome. While I haven’t benchmarked it, for normal browsing it does feel slower than Crome. But what kills it for me is their crippled App…
I don't understand why Mac users use Chrome. Safari seems to be out of fashion: people just assume that it should not be used for some reason, even though it is actually a great browser. I use Safari for both my own browsing and for development (a fairly large ClojureScript application), and it is by far the best browser on the platform by all measures (speed first and foremost). The only place where Safari falls sho…
Tab management is worse on safari vs chrome. Until recently, there were no favicons in tabs so it was hard to differentiate, and once you have a lot of tabs you have to scroll, while on chrome there is no scrolling and you can use favicons to see all of your tabs at a glance. FF has tab scrolling, but you also have tree style tabs which is better than chrome when you have a lot of tabs. Container tabs are also a big…
This will show an overview of all your tabs at once. Just start typing to find a particular tab by name.
A two-finger pinch-in gesture will also trigger the Tab Overview.
Another fun one: use Command-Option- and Command-Option- to make text larger or smaller (as opposed to zooming the entire page).
To view other shortcuts, click the View menu in Safari, and then hold down the Option key.
Earlier quoted context omitted.
People keep saying this, but I don't see how Safari dev tools are all that bad. My needs are quite simple, but by and large things appear to work in a way very similar to Chrome. What would be the main things you usually do with the dev tools where Chrome shines and Safari sucks? I'd like to understand what I'm missing by developing on Safari.
The safari dev tools used to be the exact same as chrome. Then they were redesigned and everything was moved to different places. I’m sure they still work fine, it’s just a learning curve to understand where everything was moved. It’s a matter of opinion but IMO the Firefox and chrome tools both have a more intuitive UI as well. Edit: just to be clear this is what I liked https://webkit.org/blog-files/inspector-eleme…
Can you please make the popped up bookmark dialog box much much bigger? Please!
When clicking the star icon at the end of the address bar, the bookmark dialog box pops up. But it is too small! It only shows very few folders and choices. In order to locate a desired bookmark folder, people have to click and scroll many times. The whole dialog box is $^%&*& too small! Please make it bigger to show much more folders! Like three times bigger! Chrome has the same problem. Firefox can do better!
Also, please make the last used bookmark folder as the default folder at the next time when the bookmark dislog box opens, because people often bookmark many related/similar pages consecutively in one short period of time. Thank you. I love Firefox.
The easiest solution is to install Windows in VirtualBox and do it there, with Firefox Sync on.
Earlier quoted context omitted.
No it isn't, there isn't any specified threat model anyway. What we're talking about is whether malicious extensions are something attackers want to use. Having to package an entire browser is a win - it's super noisy and means there's a huge binary to lug around.
>No it isn't, there isn't any specified threat model anyway. Well, yeah, in the sense that Mozilla people don't really think through what threat model they're protecting against here. >What we're talking about is whether malicious extensions are something attackers want to use. Having to package an entire browser is a win - it's super noisy and means there's a huge binary to lug around. The vast majority of that bene…
Attacker has code execution on your system and wants to maintain persistence and exfiltrate sensitive browser data. Sounds reasonable for Mozilla - at least, it's not totally nuts of them to consider this in their threat model.
One avenue, and a popular one, is to then sideload a malicious extension. An attacker who can disable the extension check can do this easily. An attacker who can't has to resort to other means - packaging a separate payload to host the extension.
Does that sound reasonable? I don't want to argue, just to explain my perspective on this issue based on the attacks I have seen.
I think link forgot to mention a step 4. Step 4: Spend weeks getting used to new shortcuts, finding equivalent extensions/plugins and getting used to their dev tools.