3 ms·

Honestly though; I bet you use chrome, didn't even bother to see if this worked in Firefox, and saw this as an opportunity to trash another browser based on you

by ZoF 13y ago

Honestly though; I bet you use chrome, didn't even bother to see if this worked in Firefox, and saw this as an opportunity to trash another browser based on your knowledge that <blink> support was deprecated. I use Chrome, I like it better than Firefox, I also knew blink was deprecated in FF and had the same thought(would this work in firefox?) because I hadn't bothered to check if this was done using CSS or the <blink> tag. Although I didn't consider commenting on it. Unless you're using a version of firefox older than 24 this is a pretty weird statement.

chrismorgan 13y ago
Anyone who knows me knows that I am a rather solid Mozilla/Firefox fan. I have Chromium installed for verification that things work with my web development, but that's all I use it for. I much prefer Firefox. It was only when I read the comments that had been made here that I remembered that Firefox had removed <blink> support and checked it in Chrome to see what had been intended. I did not actually check at that point that it had used <blink> but assumed. This was an error. As it happens, I run Nightly and for whatever reason the animation is not functioning there. I presume it's faulty browser detection on their part or the lack of a prefix-free version or some such thing.
- ZoF 13y ago
  Good to hear. Sorry for being a dick; it just seemed like you were trying to make an anti-FF statement based on prior knowledge and nothing else, glad to hear it was just their nightly build not functioning properly. For what it's worth, I prefer FF as a company, but I like Chrome for syncing tabs and the developer tools.
  - chrismorgan 13y ago
    CSS animations work fine in Nightly. I'll say with certainty 0.95 that it'll be Google's fault. As a corollary, the AdWords management interface detects Nightly as an old browser rather than a very new browser.
    - ZoF 13y ago
      Thinking about it I agree it does seem infinitely more likely to be something on Google's end.

by ZoF 13y ago

chrismorgan 13y ago

Anyone who knows me knows that I am a rather solid Mozilla/Firefox fan. I have Chromium installed for verification that things work with my web development, but that's all I use it for. I much prefer Firefox. It was only when I read the comments that had been made here that I remembered that Firefox had removed <blink> support and checked it in Chrome to see what had been intended. I did not actually check at that point that it had used <blink> but assumed. This was an error. As it happens, I run Nightly and for whatever reason the animation is not functioning there. I presume it's faulty browser detection on their part or the lack of a prefix-free version or some such thing.

ZoF 13y ago
Good to hear. Sorry for being a dick; it just seemed like you were trying to make an anti-FF statement based on prior knowledge and nothing else, glad to hear it was just their nightly build not functioning properly. For what it's worth, I prefer FF as a company, but I like Chrome for syncing tabs and the developer tools.
- chrismorgan 13y ago
  CSS animations work fine in Nightly. I'll say with certainty 0.95 that it'll be Google's fault. As a corollary, the AdWords management interface detects Nightly as an old browser rather than a very new browser.
  - ZoF 13y ago
    Thinking about it I agree it does seem infinitely more likely to be something on Google's end.