4 ms·

But they don't decide what browser their customers use.

a3n 10y ago
Then suggest that they detect browsers, and put up a little non-distracting version of your thumbnail explanation to their customers. :) If this is truly distracting or breaking to your clients' customers, then someone is going to have to do or say something.
- Ezhik 10y ago
  The terrible truth is that consumers don't give a shit about standards, freedom, and the greater good. They just want the website to work with the least amount of effort possible.
  - pawadu 10y ago
    Lets turn this around: The terrible truth is that some web devs don't give a shit about web standards. They just want the site to look good on their iMac with Safari. So now we have huge webkit emulation layers in all major browser...
  - Ygg2 10y ago
    Or to turn it around: The terrible truth is that Chrome don't give a shit about standards, freedom, and the greater good. They just want to write their code with the least amount of effort possible, standards be damned.
pawadu 10y ago
I don't understand your logic here. Are the costumers using Chrome? Then devs should test on Chrome too. Are the costumers NOT using Chrome? Then what is the problem??
- flukus 10y ago
  The problem is that it was tested and working in chrome, until they decided to remove that feature.
- codedokode 10y ago
  The consumers are using different browsers. People who write HTML are often not very competent and cannot make page display properly everywhere. I use Chromium (because unlike Chrome it is open source). Video playback doesn't work even on twitter and vimeo (who can afford to hire good developers) let alone smaller websites. But it works on Youtube (not always, some videos require flash) and Wikipedia. UPD: That is why I think people sould learn from Wikipedia developers and not some hipster guys explaining how to connect Redux to Angular2 using ES7.
  - gcp 10y ago
    Video playback doesn't work even on twitter and vimeo This is because they use H.264, a patented but common video codec. Chrome includes a licensed decoder for it, but Chromium cannot include that because it's open source. Firefox "solves" this by relying on installed system libraries (for video) and a licensing hack by Cisco (for WebRTC). Your experience is a pretty good illustration that Chromium is not the open source version of Chrome.
    - codedokode 10y ago
      Chromium might not support H.264 but it supports VP8 and some open source codec Wikipedia uses. So the problem is with developers relying on proprietary codecs.
      - gcp 10y ago
        H264 isn't proprietary, it's patented. Anyway, like my own post here, what you say is factually right but besides the point. Users expect H264 to work or the web will break. Like -webkit prefixes.
- TazeTSchnitzel 10y ago
  > Are the costumers using Chrome? Then devs should test on Chrome too. I do test on Chrome! The context is Chrome removing standardised features with no warning years down the line, breaking existing deployed content. What do you expect a web developer to do in that case? No amount of the Chromium team being hostile to web developers will stop people from using Chrome. Yet so long as the Chromium team are breaking websites using standardised features without warning, the web developer's life will be pain.

a3n 10y ago

Then suggest that they detect browsers, and put up a little non-distracting version of your thumbnail explanation to their customers. :) If this is truly distracting or breaking to your clients' customers, then someone is going to have to do or say something.

Ezhik 10y ago
The terrible truth is that consumers don't give a shit about standards, freedom, and the greater good. They just want the website to work with the least amount of effort possible.
- pawadu 10y ago
  Lets turn this around: The terrible truth is that some web devs don't give a shit about web standards. They just want the site to look good on their iMac with Safari. So now we have huge webkit emulation layers in all major browser...
- Ygg2 10y ago
  Or to turn it around: The terrible truth is that Chrome don't give a shit about standards, freedom, and the greater good. They just want to write their code with the least amount of effort possible, standards be damned.

pawadu 10y ago

I don't understand your logic here. Are the costumers using Chrome? Then devs should test on Chrome too. Are the costumers NOT using Chrome? Then what is the problem??

flukus 10y ago
The problem is that it was tested and working in chrome, until they decided to remove that feature.
codedokode 10y ago
The consumers are using different browsers. People who write HTML are often not very competent and cannot make page display properly everywhere. I use Chromium (because unlike Chrome it is open source). Video playback doesn't work even on twitter and vimeo (who can afford to hire good developers) let alone smaller websites. But it works on Youtube (not always, some videos require flash) and Wikipedia. UPD: That is why I think people sould learn from Wikipedia developers and not some hipster guys explaining how to connect Redux to Angular2 using ES7.
- gcp 10y ago
  Video playback doesn't work even on twitter and vimeo This is because they use H.264, a patented but common video codec. Chrome includes a licensed decoder for it, but Chromium cannot include that because it's open source. Firefox "solves" this by relying on installed system libraries (for video) and a licensing hack by Cisco (for WebRTC). Your experience is a pretty good illustration that Chromium is not the open source version of Chrome.
  - codedokode 10y ago
    Chromium might not support H.264 but it supports VP8 and some open source codec Wikipedia uses. So the problem is with developers relying on proprietary codecs.
    - gcp 10y ago
      H264 isn't proprietary, it's patented. Anyway, like my own post here, what you say is factually right but besides the point. Users expect H264 to work or the web will break. Like -webkit prefixes.
TazeTSchnitzel 10y ago
> Are the costumers using Chrome? Then devs should test on Chrome too. I do test on Chrome! The context is Chrome removing standardised features with no warning years down the line, breaking existing deployed content. What do you expect a web developer to do in that case? No amount of the Chromium team being hostile to web developers will stop people from using Chrome. Yet so long as the Chromium team are breaking websites using standardised features without warning, the web developer's life will be pain.