Firefox To Remove UI Dark Pattern From Screenshot Tool After Months of Complaints (zdnet.com) 127
After months of user complaints, Mozilla will remove a misleading "dark pattern" from its page screenshot utility. From a report: The problematic feature is the "Save" button that appears when Firefox users take a screenshot. The issue is that the Save button doesn't save the screenshot to the PC, as most users would naturally expect, but uploads the image to a Mozilla server. This is both a privacy violation, as some users don't appreciate being tricked into uploading sensitive images saved on remote servers, but also an incovenience as users would still have to download the image locally, but in multiple steps afterward.
Well that's just downright suspicious (Score:5, Insightful)
Why would anyone want to upload a screenshot to Mozilla's servers? Usually when you take a screenshot it's because you need to use it locally, as in sending the file to someone, or archiving it.
It seems odd that they'd implement this ability at all; a bit shady even. Surely if you need to upload a screenshot to Mozilla to report a browser bug, it makes more sense to just send the image file you just saved locally.
Re: (Score:1)
Its primary pull is greater respect for user privacy and what the user wants.
You're being sarcastic, right? Or maybe you live in some alternate universe.
Respect for user privacy? A company that takes hundreds of millions of dollars from Google every year? Shirley you jest.
What users want? LOL.
Mozilla has spent the last 6+ years destroying everything that made Firefox popular in the first place. Ripping out features that users like, and cramming in more useless unwanted crap. And every complaint from users has been met with a response that is nothing more than a thinly veiled F
Re: (Score:1)
"use it locally, as in sending the file to someone"
Sending a file to someone is pretty much the opposite of using it locally.
Re:Well that's just downright suspicious (Score:4, Interesting)
Here's the thing, though. Since they already have the "take screenshot and upload it on a dedicated server" code in place, all they need is to ask the user when taking a screenshot:
"Do you want to save this screenshot locally on your device (default choice) or upload it to the Mozilla servers?"
Re: (Score:2)
Re: (Score:2)
Presenting a choice might confuse the poor consumer, oops I meant, User.
Re:Well that's just downright suspicious (Score:5, Informative)
Here's the thing, though. Since they already have the "take screenshot and upload it on a dedicated server" code in place, all they need is to ask the user when taking a screenshot:
"Do you want to save this screenshot locally on your device (default choice) or upload it to the Mozilla servers?"
It looks to me like they don't even need to do that.
I never even knew that this feature existed (it's hidden under a '...' menu that I've never opened in all these years). So I pulled it up, and I see that there are already two separate buttons: A small "Download" button and a large "Save" button. (The latter has a tiny "cloud" icon in it, which I guess is a subtle clue and/or IQ test.)
All they really need to do is change the word "Save" to "Upload to cloud", and also change the color and size of the "Download" button to make it equally prominent to the save button. It could be purely styling changes with no change in the code logic.
Re: (Score:3)
But maybe that would be too fucking honest, or more accurately, not at all dishonest like the current naming.
Fun fact: Clicking download doesnt download anything, so its a fucking lie, and why would they lie here? I'll give you a fucking guess... its to support the other lie.
Re:Well that's just downright suspicious (Score:5, Insightful)
Why would anyone want to upload a screenshot to Mozilla's servers?
This is a torn issue. There's A/B testing that shows there's users wanting to take a screenshot and share it. Mozilla is trying (well actually was trying) their hand at being that person who does the sharing as opposed to say imgur or something. This next part being only my opinion, I have reservations about Mozilla being the share folks, they ought to just stick to the browser but I totally understand some of the rationale behind why they'd want to be in the mix. I don't agree with those opinions but again that is just me speaking here.
Usually when you take a screenshot it's because you need to use it locally, as in sending the file to someone, or archiving it
Well, sending it to someone for some users is providing a shorten link to a web address. I get it, that's not everyone, but reading the boards I think I recall them indicating having use case numbers that indicated that some folks are link sharers. I don't know the specific numbers as that's not obviously in any of their notes they post to the blog/maillist/boards.
It seems odd that they'd implement this ability at all; a bit shady even.
Again my opinion only, I kind of agree with you there. However, they were (maybe they will in some other incarnation later?) testing out services. What the ultimate goal for services should be pretty obvious, but from mailinglist, I've not heard anything about monetizing services. Again, I don't like it, but I get Mozilla needs cash too. I'll try not to get too political here with things like, "Well if they didn't spend ____ then..." It's mixed bag with me and my opinion here that's worth two cents. So I again, I agree 98% of the way let's say.
Surely if you need to upload a screenshot to Mozilla to report a browser bug, it makes more sense to just send the image file you just saved locally.
I don't think the screenshot feature is there to facilitate bug reporting. When it was announced, the feature was mostly there to address some use cases from users.
I do want to point out that a patch was accepted the same day of the issue being raised on Github. However, there was some A/B testing and some discussion about if ditching the upload function altogether should be the course of action. I think that the end of the Test Pilot program settled the debate, which is the servers that were receiving the images. Again, I just want to make sure you absolutely understand, I agree with you, but I can also see why Mozilla might want to test out services and see what the general feel is for that. I don't think it's been glowing reviews everywhere for any of the Test Pilot programs or at least that's my feel I get having read the mailinglist for the last several months now, but also I caution anyone to take anything I say with a grain of salt. I definitely will welcome Mozilla focusing more on Rust/Firefox than these Test Pilot things.
Re:Well that's just downright suspicious (Score:4, Insightful)
This is a torn issue. There's A/B testing that shows there's users wanting to take a screenshot and share it.
Well, sending it to someone for some users is providing a shorten link to a web address. I get it, that's not everyone, but reading the boards I think I recall them indicating having use case numbers that indicated that some folks are link sharers.
However, there was some A/B testing and some discussion about if ditching the upload function altogether should be the course of action. I think that the end of the Test Pilot program settled the debate, which is the servers that were receiving the images.
(For others, all three of those quotes are taken from separate parts of parents post)
All this pretty much boils down to keeping "Save" work the same way "Save" did and always has worked, in firefox and anything else.
Adding a separate button, perhaps "Share" or "Upload" or even "Publish" shouldn't be so beyond their programmers abilities.
Had they not changed, nay broken, expected functionality and just simply added the new feature with a new button/label to indicate what was actually happening, I doubt anyone at all would have cared, complained, or had any issue.
I quoted the parts above because I seriously doubt a single one of those people being tested wanted the "Save" button to do this.
Not the people who want local copies and expect "Save" to actually save, and not even the ones that wanted a link to give to others who would expect a "Share" button to do that and avoid a "Save" button.
If their UI people can't manage more than a single button existing (which I could believe) changing the word to actually describe that buttons function should be well within their grasp.
Of course in that case people wanting a local save would likely complain they removed that feature, but that wouldn't be beyond their standard operating procedure, and certainly wouldn't have resulted in such drama.
I agree they should be focusing on what they claim to be good at, but if they want to try their hand at an image hosting service, more power to them. Those of us not wanting it would simply ignore that feature and the new button to use it. :P
We managed to ignore Pocket just fine after all
But not adding a button with a proper description, or replacing the existing Save button, is just outright misleading to everyone, and no matter the actual case is really hard for a user to accept was anything but intentional and for nefarious purposes.
For those wanting a local copy, Save is now broken and has potential serious problems with what happens.
For those wanting a link, they aren't going to even bother clicking Save since that doesn't ever give you a link, and they will still think Firefox can't do the thing they want despite the misleading button actually doing so.
Re: (Score:2)
their UI people
These aren't "UI" people, they're "UX" people. The difference is that one cares about things like usability and understandability, and the other wants to make some kind of artistic statement, rejecting existing UIs as passé and in need of change simply because they are old.
Re:Well that's just downright suspicious (Score:4, Interesting)
It seems like a lot of companies are pulling this crap, And I don't know why either. I have worked as a developer for such companies, and they don't know why they are doing it either.
It is like all the PC users who use this software that is installed on their system, is for the most part massively overpowered, and can handle these requests perfectly fine by themselves. Adding a server component adds complexity to the host software, and adds headache at the server side too as now we have to make sure all this data is extra secure. Because it is traveling over the internet and not just bouncing around the PC memory.
This will fix that ... (Score:4, Informative)
Update your "about:config" settings or edit your "user.js" file - problem solved.
// Disable Firefox Screenshots
user_pref("extensions.screenshots.disabled", true);
user_pref("extensions.screenshots.system-disabled", true);
user_pref("extensions.screenshots.upload-disabled", true);
Re: (Score:1)
Yeah, that and a 410K patch that alters 917 files in 113 directories and you'll have a Firefox that's nearly as good as it was five years ago.
Re:This will fix that ... (Score:5, Insightful)
Well, let' see here, I figure about 1% of Mozilla's users are technically proficient enough to try this, or even be all that aware of the problem or that there might be a fix for it, Of that number, about 1% are going to be able to figure out this incredibly intuitive procedure. Yeah, this solves the problem.
It's on open display, in an unlit basement with a door marked "Beware of The Leopard", at the bottom of a locked file cabinet. Really, I don't see how there's any problem at all.
Re: (Score:2)
There won't be any problems if you know where your towel is.
Re: (Score:3)
Of that number, about 1% are going to be able to figure out this incredibly intuitive procedure. Yeah, this solves the problem.
Well... It gets easier when your first instinct to any Firefox "feature" announcement becomes: Google "firefox disable [feature]"
It's on open display, in an unlit basement with a door marked "Beware of The Leopard", at the bottom of a locked file cabinet. Really, I don't see how there's any problem at all.
When it comes to Firefox, the word yellow is always wandering through my mind in search of something to connect with...
Re: (Score:2)
Update your "about:config" settings or edit your "user.js" file - problem solved.
// Disable Firefox Screenshots
user_pref("extensions.screenshots.disabled", true);
user_pref("extensions.screenshots.system-disabled", true);
user_pref("extensions.screenshots.upload-disabled", true);
My god, that is so obvious! I should have thought of doing it in the first place!
Re: (Score:2)
Seriously, I'm surprised that "Firefox" is still a front-page brand on Slashdot in 2019.
Re: (Score:3)
Re: (Score:3)
Or just ... you know ... not use the screenshot function?
Re: (Score:2)
I have added your lines to my "Firefox telemetry and data collection denial" user.js script.
I recommend everyone use the following settings for their user.js:
https://gist.github.com/MrYar/... [github.com]
Re: (Score:2)
"dark pattern" (Score:5, Insightful)
Using the term "dark pattern" while discussing a UI design is about the stupidest and confusing thing you could do. I was literally thinking there was some visual element that was dark. How about call it "deceptive", "misleading" or "confusing"? Sheesh. Your job is to write. Take a little pride in your work and think about what your words actually convey.
Re:"dark pattern" (Score:5, Informative)
Dark pattern is the accepted term for deceptive user interfaces and has been for a around a decade. It exists as a bucket term because of the large number of methods used.
Re: "dark pattern" (Score:1)
Never heard of it before this Slashdot story. Go outside some more.
Re: "dark pattern" (Score:5, Insightful)
Never heard of it before this Slashdot story.
Nor have I. But I guess we have exposed ourselves as not being 'hip'. The Web is more and more about being hip, not actually getting anything productive done.
Re: (Score:3)
One can't be expected to know every term used in every field, or even in one field. For being called "hip" this website has been around for nearly a decade calling out and shaming shady practices: https://darkpatterns.org/ [darkpatterns.org]
Re: (Score:3, Informative)
You're right, it's an obscure phrase that people only used briefly on obscure websites years ago.
https://www.theverge.com/2013/... [theverge.com]
https://techcrunch.com/2018/07... [techcrunch.com]
https://mashable.com/article/f... [mashable.com]
https://www.forbes.com/sites/t... [forbes.com]
https://www.howtogeek.com/fyi/... [howtogeek.com]
https://arstechnica.com/inform... [arstechnica.com]
https://www.abc.net.au/news/sc... [abc.net.au]
https://gizmodo.com/dark-patte... [gizmodo.com]
https://phys.org/news/2018-04-... [phys.org]
https://www.extremetech.com/in... [extremetech.com]
https://venturebeat.com/2018/0... [venturebeat.com]
https://sdtimes.com/addiction/... [sdtimes.com]
https://9to5mac.com [9to5mac.com]
Re: (Score:2)
years ago
So why are most of your links with dates in the URL from 2018?
Re: (Score:1)
That's the joke.
Re: (Score:2)
Re:"dark pattern" (Score:4, Interesting)
It's a stupid choice, and is confusing. I agree with Dan East, ANYTHING else would have been better. Some options:
Evil Pattern
Manipulative Pattern
Sucky Pattern
Theiving Pattern
Crappy Pattern
Shitty Pattern
Lying Pattern
Why even include "pattern"??? Why not
Evil UI
Lying GUI
Corrupt Design
Immoral Interfaces
Seriously, DARK PATTERNS seems almost interesting or a curiousity of emo designers. Not the evil treacherous vile scum shit fuck that it is. Seriously, don't defend this really really shitty choice.
My paranoia says this label was chosen for the _express_ purpose of diminishing the danger and horrendous effects it has on people.
Dark patterns can suck it. We need a new phrase.
Re: (Score:3)
Evil Pattern
Manipulative Pattern
Sucky Pattern
Theiving Pattern
Crappy Pattern
Shitty Pattern
Lying Pattern
Dishonest Fuck Pattern
Re: (Score:3)
It's confusing, especially because of the rise of the "Dark mode GUI" thing that's been going on for the last few years.
Re: (Score:3)
Re: (Score:3)
Re: (Score:2)
Could that be because you're a good developer and not a shady shit working for Facebook? It's not really a new term. There's even been a website around that publishes a continuously rolling hall of shame for the past 10 years: https://darkpatterns.org/ [darkpatterns.org]
Re:"dark pattern" (Score:4, Informative)
I've never heard the term either and it is losing relevance.
It peaked in Nov 2005, it is about 34% as popular now.
https://trends.google.com/tren... [google.com]
Re: (Score:2)
Accepted term amongst whom? UI/UX experts who sniff their own farts? I have never encountered this shit in my too many years.
Re: (Score:1)
Dark pattern is the accepted term for deceptive user interfaces and has been for a around a decade.
BULLSHIT!
Re: (Score:1)
When it comes to misleading images on buttons of software, I think we'd rather use the term "decepticons."
Re: (Score:1)
Never heard of it until today, cockwad.
Re: (Score:3)
It exists as a bucket term.
Did you just make up a term, while trying to define a made-up term? I just looked for "bucket term" on Google and didn't find it. Even urbandictionary doesn't have it. Next you'll tell me that it's a perfectly cromulent word.
Re: (Score:1)
This kind of thing happens to me constantly. Google accuses me of being a robot on a regular basis.
Re: (Score:1, Informative)
Or you could, you know... use terminology [wikipedia.org] in the standard way it has come to be used [darkpatterns.org] throughout the industry. [arstechnica.com]
Re: (Score:3)
I suppose if I bought a domain name (like https://darkpatterns.org/ [darkpatterns.org]) I'd try to make everyone feel like a dweeb for not standardizing on my trademark.
Wait! Could this be some kind of trick?
Re: (Score:2)
Oh look, a self-serving definition:
Re: (Score:3)
Re: (Score:2)
Re: (Score:1)
Because the practice of referring to this as a 'dark pattern' is deceptive, misleading and confusing. The average user will look at the headline, and try to remember the last time the UI looked a bit too dim.
"Nope. I guess this doesn't apply to me." And go on saving screen shots to Mozilla servers.
Re: (Score:1)
Maybe they should've put the term in quotes, but then they could be accused of using "scare quotes". A term I imagine you also hate. Along with things like "fast follow" and "disk drive".
Re: (Score:1)
Oh wait, they DID use quotes.
Re: (Score:1)
I thought "asshole design" was the accepted nomenclature.
Mozilla actually listens to complaints? (Score:5, Funny)
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
fall of FF (Score:1)
Mozilla sucks (Score:5, Insightful)
But at least they have a very diverse board and an uncompromising CoC!
Re: (Score:1)
Mozilla has a special thing for very diverse broads with dicks. I think it's called "Rust"
Re: (Score:2)
Q: How do you know when someone programs in Rust (or Go)?
A: They'll tell you.
Re: (Score:2)
FTFY.
Re:print screen button? (Score:4, Informative)
The Firefox Screenshot Tool can capture the whole page -- including sections of the page that can't dimensionally fit on screen.
How the mighty have fallen (Score:3)
Why? (Score:1)
Re:Why? (Score:4, Informative)
No, your OS cannot screenshot a full webpage including all parts beyond the vertical and horizontal scrolls.
Re: (Score:1)
Re: (Score:2)
Never knew that (Score:2)
What is the advantage of this button? (Score:2)
Or SnagIt, or Greenshot, or the Windows Screen Snipping Tool.
Re: (Score:3)
Allegedly.