This annoys me for some time: When you use ANY custom ccs it prevents reading bugs

[Calmon70]

I can somehow understand the reason because there might be people playing around with custom ccs, forget it and later report it as bug.

But come on: Hard blocking people reading simple bug descriptions just because simple CCS improvements for few games are used is way to harsh. I usually need to copy the bug link, go anonymous just to read it and ofc I can't comment any bug without removing for some time my custom ccs.

This is what you get when you use BGA feature custom CCS and try to access any bug: https://imgur.com/a/rf7stJW

(btw. I know I can use custom css with browser addons but I like the ingame feature works also on mobile!)

[Kayvon]

As a developer who receives over a hundred bug reports emails some weeks, I'm glad they enforce this. The vast, vast majority of reports are false reports that waste time. Lots of people don't understand the rules, don't read the forums to overcome common confusions, and insist volunteer developers provide top-notch customer service... for free. (In fairness, most people don't realize that we're not paid employees.)

If we had to chase down custom CSS changes on top of that? Not a chance. The interface blocks you from getting to the page where you can add comments. Sure, that blocks you from seeing the bugs also, but it's a small price to pay (the time to open a private window) to save developer time (already hours of time each week).

[wdspider]

Blocking reading of the bugs due to custom css turned on doesn’t actually help anything. If I am trying to report a bug and I get that error, 1of 2 things is going to happen:

1. I simply don’t post the error leaving the potential bug unreported

• I go through the hassle of turning the custom css off and report the bug

99% of the time it is going to be #1. Even when it is #2 1% of the time, it’s not like I’m going to go check if the bug still exists with the custom css turned off before I post.

[Tisaac]

Blocking reading of the bugs due to custom css turned on doesn’t actually help anything. If I am trying to report a bug and I get that error, 1of 2 things is going to happen:

1. I simply don’t post the error leaving the potential bug unreported

• I go through the hassle of turning the custom css off and report the bug

99% of the time it is going to be #1. Even when it is #2 1% of the time, it’s not like I’m going to go check if the bug still exists with the custom css turned off before I post.

You are missing the point. The question is exactly whether the bug is linked to the custom css or not. To give you an idea, i already got couple of times an issue with players that reported bugs i wasnt able to reproduce because they had the unofficial extension that does contain some css and that is not detected by bga so they can create bug reports. I cant tell you how many hours were wasted of getting a screenshot, device information, load a device emulator to load the page, inspect each elements and not finding anything, to start getting to the conclusion that it was actually this expansion that was the source of the issue. I dont want this kind of reports.
Now, eventhough i still think it's a great idea in general, i think it could be made differently because not all bugs are equals. If your bug is about the interface, missing buttons, etc .. then yeah, i want to make sure you dont have weird custom things. But if the bug is about a rule or a server error, then you should be able to report.
Also, i would also agree that being able to browse the existing bugs and upvote them shouldnt have any conditions, but rather only reporting a new one (and a lot more could be discussed about that to try to improve bug reports quality)

[Jellby]

In an ideal lollypop world, reports would automatically include (perhaps as an attachment) the custom CSS the user had active at the time.

[Tof63]

(btw. I know I can use custom css with browser addons but I like the ingame feature works also on mobile!)

Just in case : Kiwi Browser is a chrome-based mobile browser that lets you install chrome extensions.

[wdspider]

You are missing the point. The question is exactly whether the bug is linked to the custom css or not.

Yes, I understand that you may think the question is whether the bug is linked to custom css or not. My point that you are missing is that preventing one from reporting bugs when they have custom css enabled does not guarantee that reported bugs are not related to custom css. Even if I'm someone who is going to go through the hassle of turning my custom css off to report something (I am doubtful many are), it's even less likely that I'm someone who is going to go back through the game after turning my custom css off to verify whether the bug is still happening.

Regardless of your stance on this fallacy, it would be nice to be able to at least read / upvote existing bugs and suggestions without having to turn the custom css off.

In an ideal lollypop world, reports would automatically include (perhaps as an attachment) the custom CSS the user had active at the time.

This is somewhat hard to do when game devs are unpaid volunteers but completely agree.

[RicardoRix]

Yes this is close to completely redundant.

- You want to report a bug.
- You remove the custom css.
- You report the bug.
- You put the custom css back again.

Where you can't even see bug reports is a pure "computer says no" situation.

It almost pushes you into using the chrome extension, or just not using a feature of BGA.
And all because 1 time, 1 person posted a wrong bug report because of custom css.

[Tof63]

To give you an idea, i already got couple of times an issue with players that reported bugs i wasnt able to reproduce because they had the unofficial extension that does contain some css and that is not detected by bga so they can create bug reports.

Sorry to read that, but I don't understand why you never told me about that?
Please send me a link to the report next time it occures. You can also send me link to the previous reports if I can do something to fix an issue.
Btw the extension displays some warnings when you try to report a bug (telling the player to check if the issue does not come from the extension), and if you put custom css you get an extra warning too.
I always told that i dont want to give extra work to game developpers, so I'm really really sorry to read such things

[theAudsMustBeCrazy]

I have been frustrated by this, too.

I read the reply by one of the developers, and s/he made a good argument. I figured this must have been the case, otherwise they wouldn't have coded this annoyance this way. But the explanation was well articulated and made sense.

I love my custom CSS, though, so I guess I just won't be able to see bugs and won't be much help when I'm testing alpha games.