3 ms·

I keep seeing reports of pages that work in Chrome but not in FF. What puzzles me is that people usually hold this against FF instead of holding it against Chro

I keep seeing reports of pages that work in Chrome but not in FF. What puzzles me is that people usually hold this against FF instead of holding it against Chrome. The very few times I have experienced such a thing, a peek at the console tells me that FF is blocking the page from doing something insecure or otherwise harmful. It reminds me of ActiveX stuff. Junky webcams still ship with an ActiveX control to embed video into their html page. When it doesn't work in FF or Chrome, some people think IE6 is a superior browser. I don't know the reason behind your various broken pages. It could be something is wrong with FF. But it could also be that something is _right_ with FF. If you don't know which, why are you complaining about FF?

V-2 8y ago
> I don't know the reason behind your various broken pages. It could be something is wrong with FF. But it could also be that something is _right_ with FF. If you don't know which, why are you complaining about FF? I'm not complaining about FF. I'm complaining about my experience using FF. I'm not attributing blame, only stating facts. Even if it's something wrong with the websites as you say, what matters to me is whether I can use them or not. And by the way, quietly blocking the page without any sort of a message or warning to the user would be more evidence of bad UX in my book. I shouldn't have to go the console to find out how the browser decided to protect me, if that's the case.