Some sites broken by preferences about user.js

[earthlng]

@Atavic, I'm a big fan of your "Better safe than sorry" campaign but please don't flip off the few users who want to help out and contribute. @crssi is not asking for help or moaning that we broke his facebook, instead he traced down the problem with specific sites/services to a specific pref, which IMO is valuable information.

@crssi, please keep participating here, I appreciate your input and we can use every help we get. Thank you

[earthlng]

• sendSecureXSiteReferrer will be removed soon and we are looking into improving the referer prefs anyway, so I don't think we need to add this to the warning list. Agreed?
• dom.indexedDB.enabled is in the warning list already and has a WARNING
• full-screen-api.enabled - is pretty self-explanatory, no need for a warning IMO, but @Thorin-Oakenpants you have the last word.

If we can agree that we don't need to do anything for this issue, let's close it.

[Atavic]

Better safe than sorry. Otherwise, you can change prefs for your own personal use.

[crssi]

I do, I find your work here very very good and I am using your user.js as a base, which doesn't mean that I agree with every settings... so I have some differences for sure. ;)
I am just trying actively participate to help you guys identifying some stuff out-of-the-box. Nothing more.

[bonbonboi]

In other words, I expect users to sort their own problems out re site breakage and not have several hundred issues made. We can't cover the top 1 million alexa sites! That said, I do expect people to report issues with major sites.

I agree, I don't think someone comes with an issue with some porn sites, lol since most of 'em sucks, but still reporting major, common, famous web sites are welcome. Plus reporting any web site included how the user solved its issue would be nice... I like to read the Issues section, kind of learning curve.