What do you consider a standard web browser?
If someone ships a browser with Tracking Protection (like Firefox), or with NoScript preinstalled (like Tor Browser), or with another adblocker preinstalled, is that a standard browser because the user didn't modify it?
Or is it based on the number of user. Is your standard browser really just Google Chrome, because Google has a lot of marketshare?
I ask, because I looked up the statistics, and they say between 25-45% of users have an ad blocker, depending on the country.
It seems pretty unfair to ignore your users completely, even if they wrote a long, detailed report. No?
It's like emailing an email provider asking why your desktop email client is displaying emails weird.
Certainly it's not a bug (on your part) that the user agent rendered the page as the user directed, but that isn't the actual complaint. The issue is that the page is over-complicated and fragile, proving unfit for purpose when faced with the slightest deviation from the default behavior of the top two or three most popular web browsers.
Note to self, don't use Photopea due to poor customer support.
You would think the customer support would at least tell them to remove/disable the add-ons instead of ignoring them.
Anyway, ad blockers are standard now and they usually share the blocking lists. Supporting them is just a matter of installing uBlock Origin in the browser you use to develop.
Maybe he's just so sick of hearing about errors or bugs from thousands of users, he's sabotaging his own product in hopes it will just die and he can move on.
Breaking this based on an ad blocker just loses you money.
That's false. Similar thinking to how the MPAA said that downloading a MP3 is a lost sale. There was never a sale to begin with, the user is not interested in a purchase regardless of whether the pirated content is available.
Here, the user will just go through the checkout again in a browser without ab-block or disable it. Why would they suddenly not need a power washer because they're running ad-block?
In fact, if anything, it'll train the user to disable ad-block when they're ready to checkout--from _ANY_ site since most of them are broken under ad-block.
https://www.vouchercloud.com/resources/consumer-psychology-t...
For website owners who are losing revenue, the mental process is simple: "If I change this webpage I will get more sales."
How difficult would it be for you to change the div name to not coincide with the characters most closely involved with one of the most contentious technologies around? And never have to deal with that potential conflict again?
> What kind of a mental process should a brain perform to conclude, that it is a bug in a website, and not in their extension, which is supposed to remove ads.
Well, if the extension looks for obvious ad-related layout, and your site just happened to use that name, then yes, you have a bug related to common usage patterns.
Even if you used the name before anything ad related, when the world changes around you, you can choose to adapt, or you can get offended and obstinate and fall further and further into a niche of your own creation.
A "popular" issue is, that people use an extension, which renames files saved by Photopea to .TXT. It is reported several times a week and every time, I tell people to disable an extension. They often argue, that it can not be caused by an extension, or even lie, that they disabled it and it did not help.
https://github.com/photopea/photopea/issues/3246 https://github.com/photopea/photopea/issues/3227 https://github.com/photopea/photopea/issues/3194 https://github.com/photopea/photopea/issues/3187 https://github.com/photopea/photopea/issues/3116 https://github.com/photopea/photopea/issues/3110 https://github.com/photopea/photopea/issues/3049 and so on.
https://github.com/photopea/photopea/issues/2294#issuecommen...
"Google docs offline" is an official extension from google which you get prompted to install when you go to Google Drive in Chrome without the extension installed. I don't think that caused anything and it looks like there was an actual bug you had:
> There really was a bug in Photopea. If you opened a file, whose name started with a dot . , like .myfile.psd, It was always exported as .TXT_ > I have fixed this bug. You can open files with any names now, and they should be saved under the right extension.
https://github.com/photopea/photopea/issues/3116#issuecommen...
It did seem like the issue was on your end and not the extensions though.
On the other hand you know how ad blocking works and if it’s not too much effort just change the class name?
If your website behaves like malware is it really the fault of antimalware software that blocks it? If there was a better way to detect malware, sure, but heuristics is the best we’ve got and they do sometimes break - if it’s not too much effort to make your website not behave like malware why not do it?
I fully agree with you about other, more intrusive site-modifying extensions, but ad-blockers are fairly lightweight and only target behavior that looks malicious, and it’s fairly easy not to trigger them.
Whenever someone reports a bug to me, I ask them if they use any site-modifying extensions. If they do, I ignore them completely, even if they wrote a long, detailed report.
Web authors make websites for standard web browsers. I do not consider a browser with site-modifying extensions to be a standard web browser, and it is not my job to test my website with all 1,000,000 extensions that exist on earth.
It all started six years ago, when my website contained <div id="ad" ... and somebody reported, that their adblock removes that element, but it is not the ad. What kind of a mental process should a brain perform to conclude, that it is a bug in a website, and not in their extension, which is supposed to remove ads.