Corsthat compete with the sophisticated graphics capabilities of desktop apps. Google currently hosts an online showcase to illustrate the potential of the technology. A spokesperson from The Khronos Group, which published the WebGL 1.0 specification in March, said last month that browser vendors are still working to make their WebGL implementations conform with the specification. The group's spokesperson also addressed Microsoft's concern about denial-of-service attacks that could arise from shaders and geometry designed to crash graphics hardware. "Browser vendors are still in the process of supporting the GL_ARB_robustness extension, so it is expected that the previously reported denial-of-service issues are still present," Khronos' spokesperson said. "It is expected that the reported denial-of-service issues will be solved with the integration of this extension.
Even as the WebGL security issues get ironed out, the changes in Chrome 13 have not completely eliminated the possibility of utilizing cross-domain media elements. Assuming the hosting image server allows it, a Web developer can employ a specification known as CORS (Cross-Origin Resource Sharing) to present images and videos that come from other domains. "Unfortunately, this new restriction in WebGL means that some existing
No comments:
Post a Comment