3 ms·

Yes. Have you ever read a NIST standard?

by badrabbit 7y ago

scarface74 7y ago
So before Apple, Google, and Mozilla release a browser they should have to go through an approval process?
- zzo38computer 7y ago
  My suggestion, though, is different. If NIST has such an approval process, then, Apple/Google/Mozilla/anyone else doesn't have to go through an approval process, but if they do go through such process then they can put on their product, the sign "Approved by NIST as web browser compliance". However, I am not so sure that such a thing is even necessary at all. I think the use of the web browser should be reduced in order that this is not necessary.
  - scarface74 7y ago
    Yeah because being approved by NIST will carry as much weight to consumers as being W3C compliant...
    - jonathankoren 7y ago
      Do you believe that consumers even know that the W3C exists?
      - scarface74 7y ago
        That’s kind of my point....
- badrabbit 7y ago
  By an organization for use by the public at large? Yes!! Devs can still make browsers explicitly for other devs or for non-public use. If society depends on your product to function then your product must be regulated. Imagine google auto-updates chrome to stop supporting http or something, imagine the economic chaos. The whims of Googlers are not something the public should rely on. Everything from their standards compliance to their change control should be regulated,same goes for mozilla.
  - detaro 7y ago
    And in this case, both Firefox and Chrome behaved according to spec. What would regulating browsers have helped?
    - badrabbit 7y ago
      Perhaps stanrdizing the QA process would have prevented this? The problem I was addressing is this issue falling inline with a pattern set by google. They wouldn't test only against Google if Google's whimsy divergences didn't mean it cost too much to support anyone elss in your QA.
      - detaro 7y ago
        Maybe I'm underestimating Twitters developers, but in this case I honestly doubt Twitter had a QA process testing if things remained in browser cache at all, until someone pointed out that there is a problem. If they had thought about it as a problem, adding the cache header would have been easier to implement and test for than browser testing somehow.

Yes. Have you ever read a NIST standard?

scarface74 7y ago

So before Apple, Google, and Mozilla release a browser they should have to go through an approval process?

zzo38computer 7y ago
My suggestion, though, is different. If NIST has such an approval process, then, Apple/Google/Mozilla/anyone else doesn't have to go through an approval process, but if they do go through such process then they can put on their product, the sign "Approved by NIST as web browser compliance". However, I am not so sure that such a thing is even necessary at all. I think the use of the web browser should be reduced in order that this is not necessary.
- scarface74 7y ago
  Yeah because being approved by NIST will carry as much weight to consumers as being W3C compliant...
  - jonathankoren 7y ago
    Do you believe that consumers even know that the W3C exists?
    - scarface74 7y ago
      That’s kind of my point....
badrabbit 7y ago
By an organization for use by the public at large? Yes!! Devs can still make browsers explicitly for other devs or for non-public use. If society depends on your product to function then your product must be regulated. Imagine google auto-updates chrome to stop supporting http or something, imagine the economic chaos. The whims of Googlers are not something the public should rely on. Everything from their standards compliance to their change control should be regulated,same goes for mozilla.
- detaro 7y ago
  And in this case, both Firefox and Chrome behaved according to spec. What would regulating browsers have helped?
  - badrabbit 7y ago
    Perhaps stanrdizing the QA process would have prevented this? The problem I was addressing is this issue falling inline with a pattern set by google. They wouldn't test only against Google if Google's whimsy divergences didn't mean it cost too much to support anyone elss in your QA.
    - detaro 7y ago
      Maybe I'm underestimating Twitters developers, but in this case I honestly doubt Twitter had a QA process testing if things remained in browser cache at all, until someone pointed out that there is a problem. If they had thought about it as a problem, adding the cache header would have been easier to implement and test for than browser testing somehow.