Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox 56: Last Stop Before Quantum

hacks.mozilla.org

Post reply on HN
Print view View original

121–130 of 190 posts

Re: Firefox 56: Last Stop Before Quantum

#121

Post by oblio »

pseudalopex wrote: post #112
oblio wrote: post #12

Earlier quoted context omitted.

It's because of the killer combo of increased sandboxing, multi-process architecture and performance constraints. I think they couldn't keep everything together with the degree of access old plugins had to Firefox internals. So at some point they had to rip off the band aid.

Multiprocess already shipped. One of the reasons extension developers are frustrated is that Mozilla told them to make their XUL extensions multiprocess-compatible and then told them they'd have to throw that work away.

Notice how I carefully avoided your strawman. There were several reasons for their action. I listed what I believe are the 3 main reasons.

Re: Firefox 56: Last Stop Before Quantum

#122

Post by NikolaeVarius »

wj wrote: post #119
NikolaeVarius wrote: post #39

Earlier quoted context omitted.

I like bitwarden at a high level, but there are tons of things that feel extremely janky with it. Also for some reason, Firefox keeps complaining that bitwarden is freezing its UI thread.

I'm not in love with LastPass so am curious as to what you don't like about Bitwarden?

It seems to lag on Firefox. Multiple times I've gotten notifications from Firefox Dev that Bitwarden is causing my page to not render (which was true).

Can't change hotkey for auto-fill login form in Firefox.

No Support for standard notes (yet I guess).

UI renders very slowly on FF and has tons of strange inconsistencies.

It definitely has the FEEL of a somewhat younger open source project while LastPass was much more refined.

I'm debating if I should bother learning C# for the sole purpose of trying to fix some of these issues, because it is maddening enough where I actually use Chrome when i do things that require logins.

Re: Firefox 56: Last Stop Before Quantum

#123

Post by tmzt »

AdmiralAsshat wrote: post #88
DerfNet wrote: post #69

Earlier quoted context omitted.

honest question, why would anyone use an in-browser screenshot tool when screenshot tools already come pre-installed in basically every operating system? can Firefox's screenshot tool be disabled? I'd like to switch back from Chrome due to Big Brother concerns but not if Firefox is making questionable choices like this.

If you consider Firefox Screenshots from the perspective of a Support tool, this makes alot of sense. Customer wants to file a support ticket or bug report, needs to include a screenshot. Screenshot taken, they paste the link into the ticket, done. They never leave the browser. Outside of the browser, fire up the screenshot tool, crop whatever you want to show, save it, upload it to imgur or website of choice, attach…

    cat verysecret.csv | cut -f 1 -d ' ' |fpaste -z -x -a
Wait, I meant paste.

Re: Firefox 56: Last Stop Before Quantum

#124

Post by zakk »

k__ wrote: post #106

The Quantum performance is amazing. But I cant get my nightly to remember my logins.

> The Quantum performance is amazing.

Agreed! I am astonished, and I switched back to FF after many, many years.

> But I cant get my nightly to remember my logins.

Quantum is in beta now, did you try that?

Re: Firefox 56: Last Stop Before Quantum

#125

Post by saberworks »

ianbicking wrote: post #117
saberworks wrote: post #46

Frustrated by the new "screenshots" tool. The "save" button automatically uploads your screenshot up to mozilla servers. The "download" button saves it to your computer. It seems completely backwards. The "save" button should save it to my computer (there's no reason call something a "download" when it's already local). The "download" button should be replaced with an "upload & share" button that sends it to mozilla'…

Hi, Screenshots developer here – We've gotten similar feedback about the Save and Download buttons, we added the cloud icon in part to make that clearer. I feel like there's a ticket about it as well, but I not able to find it. We're planning on adding a Copy button, and we'll probably do some user research on the buttons generally to make sure the choice is clear. We did have a full page screenshot feature, but it d…

Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it?). It's very clear based on the design of the interface that your primary goal is to get people to upload their screenshots to your servers. The "save" button is the only one with a label. The others are icons only. The "save" button is 3x as big as the other two. The "save" button is the only button with any color (the others are black & white). Also note that the current "save" feature (which uploads the screenshot to mozilla servers) actually does the opposite of saving them because after 2 weeks they will be deleted.

I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right? And when they hit "save" in microsoft word or whatever, they think the document is going to microsoft servers?

"Save" means put it in my local storage.

"Download" means copy some file from a remote server onto my local storage.

"Upload" means copy it from my local storage to a remote server.

I also just realized that clicking the "save" button clobbers whatever is in my clipboard.

https://screenshots.firefox.com/oFTVibyVnGx7LPAl/news.ycombi...

Re: Firefox 56: Last Stop Before Quantum

#126

Post by saberworks »

saberworks wrote: post #125
ianbicking wrote: post #117

Earlier quoted context omitted.

Hi, Screenshots developer here – We've gotten similar feedback about the Save and Download buttons, we added the cloud icon in part to make that clearer. I feel like there's a ticket about it as well, but I not able to find it. We're planning on adding a Copy button, and we'll probably do some user research on the buttons generally to make sure the choice is clear. We did have a full page screenshot feature, but it d…

Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it?). It's very clear based on the design of the interface that your primary goal is to get people to upload their screenshots to your servers. The "save" button is the only one with a label. The others are icons only. The "save" button is 3x as big as the other…

After using it to actually upload that shot, I just realized it captured and shared much more than just the screenshot. It captured and shared the page title and domain of the page I took a screenshot of. That seems like quite the security risk given that I wasn't notified such was going to be shared. Imagine if I'm working on a dev server or a private place on a public server. It seems that when people want to share a screenshot, they want to share just the screenshot in many cases.

Re: Firefox 56: Last Stop Before Quantum

#127

Post by opencl »

51Cards wrote: post #35
pricechild wrote: post #3

I've been following https://utcc.utoronto.ca/~cks/space/blog/web/Firefox56AddonW... It's surprised me the amount some people rely on addons for their workflow and the amount of effort they will be going through to resist this change come 57. For my usage, I've found Firefox Klar/Focus (which I believe already include the speed improvements from 57+?) on Android and have been extremely impressed.

I'll be doing the same, staying on 56 for quite awhile. This transition has been very poorly managed by Mozilla. I understand the advantages to Quantum but they have left a very large percentage of their extension developers hanging. Web Extensions is not mature enough for many of the large extensions to be ported but despite that they are proceeding with this transition anyhow. If I was an affected extension develop…

Not sure if you're aware of the Extended Support Release of FF but it seems better than staying on 56: Firefox 52 ESR will continue getting security patches up through June 2018.

Re: Firefox 56: Last Stop Before Quantum

#128

Post by wj »

NikolaeVarius wrote: post #122
wj wrote: post #119

Earlier quoted context omitted.

I'm not in love with LastPass so am curious as to what you don't like about Bitwarden?

It seems to lag on Firefox. Multiple times I've gotten notifications from Firefox Dev that Bitwarden is causing my page to not render (which was true). Can't change hotkey for auto-fill login form in Firefox. No Support for standard notes (yet I guess). UI renders very slowly on FF and has tons of strange inconsistencies. It definitely has the FEEL of a somewhat younger open source project while LastPass was much mor…

Thanks. Will probably wait for LastPass to release the firefox plugin for 57 then. Will check Bitwarden again in a few months.

Re: Firefox 56: Last Stop Before Quantum

#129

Post by ianbicking »

saberworks wrote: post #125
ianbicking wrote: post #117

Earlier quoted context omitted.

Hi, Screenshots developer here – We've gotten similar feedback about the Save and Download buttons, we added the cloud icon in part to make that clearer. I feel like there's a ticket about it as well, but I not able to find it. We're planning on adding a Copy button, and we'll probably do some user research on the buttons generally to make sure the choice is clear. We did have a full page screenshot feature, but it d…

Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it?). It's very clear based on the design of the interface that your primary goal is to get people to upload their screenshots to your servers. The "save" button is the only one with a label. The others are icons only. The "save" button is 3x as big as the other…

> I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right?

More or less, yes, if more people understand one design than another, then the one that more people understand is the right one. We're generally shooting for more than a majority though, we'd want most people to understand the interface, and would also take negative reactions into account.

In our past studies we found people generally understood the buttons well enough, and specifically it was obvious after first use what was happening. But we only compared the current buttons to one other option (which didn't compare well), so it wasn't a very thorough test.

There's more overhead in updating this interface than some others, since we have to get updated translations (to more strings than just the button) and change all our onboarding, which is why we've kind of left it be until we can look at the full set of buttons more closely.

Re: Firefox 56: Last Stop Before Quantum

#130

Post by andrepd »

greggyb wrote: post #71
andrepd wrote: post #25

Earlier quoted context omitted.

Absolutely. I won't be upgrading and I'm already looking for alternatives, as long as crucial parts of my workflow (tree tabs, session manager) have no adequate replacement. The ugly redesign is also a thorn in my side.

https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta... has a 'Compatible with Firefox 57' badge, and I've been using it with no issues. I've always been satisfied with the built in session management (restore last session on open) and don't have any feedback on the other.

Not only is the new Tree Style Tabs a step backwards from the old, I'm also not running that addon, but this one: https://addons.mozilla.org/en-US/firefox/addon/tab-tree/ I find it lighter and more responsive.

As for the session manager, I need more features: saving and loading several sessions, etc.

Post reply on HN