Re: Chrome WebVR avaliable only on secure origins

While I agree with the motivations of creating a more secure web...it seems odd to have special implementation restrictions for WebVR as opposed to any other media delivery. Certainly at the very least if HTTPS only turns out as a requirement there needs to be a flag aka Tony's

--allow-file-access-from-files


Personally I thinks it's overkill and overly prescriptive, the whole issue of HTTPS should be dealt with at the HTTPS level independent of content types and existing CORS restrictions treat all content uniformly. Onward...Sandy



Sandy Ressler
High Performance Computing and Visualization Group
National Institute of Standards and Technology
100 Bureau Drive, STOP 8911
Gaithersburg MD, 20899
(301) 975-3549 Fax: (301) 975-3218
sressler@nist.gov      @sressler