Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was closed and archived. Please ask a new question if you need help.

Why are you so damned desperate to ruin the background color and/or display of standalone images?

more options

You ruined the background of standalone images many versions ago. We had to fix it ourselves in the omni.ja file. You made that file proprietary compression in the next version, so we had to fix it ourselves in the userContent.css file. Now you've damaged it again. Why the continued desperate effort to keep breaking something that wasn't broken, and more importantly, why work so damned hard to prevent people from fixing it when you do break it?

You ruined the background of standalone images many versions ago. We had to fix it ourselves in the omni.ja file. You made that file proprietary compression in the next version, so we had to fix it ourselves in the userContent.css file. Now you've damaged it again. Why the continued desperate effort to keep breaking something that wasn't broken, and more importantly, why work so damned hard to prevent people from fixing it when you do break it?

All Replies (4)

more options
more options

There would be no need to install yet another add-on to make up for these incompetent Firefox developers if they wouldn't continue to intentionally damage/disable the ways we already use to accommodate their incompetence. The question was not: "What add-ons can we install to work around the incompetence of the developers?" The question was: "[W]hy [do the developers] work so damned hard to prevent people from fixing it when [they] do break it? "

more options

A little research shows me that someone named Carlo Alberto Ferraris is responsible for breaking Firefox's standalone images. My apologies to the developers in general for my accusation of incompetence. It's Carlo Alberto Ferraris who is incompetent in this case. His bumbling and selfish mistake was addressed in another blog a couple years ago... "You've succeeded after three years of effort in hijacking the browser to make it less useful for most users. Congratulations. I hope you're tremendously proud of yourself. Go take a hike."

more options

The proper place to submit feedback to Mozilla is here - https://input.mozilla.org/en-US/feedback

Since this is a support forum and this thread doesn't involve a support issue I am going to lock this thread.