answered
2017-06-22 09:18:11 +0300
WrbGL is insecure technology with direct access to hardware with no security boundaries. Therefore it is GOOD thing that it is missing. I quote here transcript of https://www.grc.com/sn/sn-300.htm
WebGL, on the other hand, provides by virtue of its functional requirements" - so this is not a mistake, this is the way it was designed - "access to the graphics hardware. Shader code, while not written in the native language of the GPU, is compiled, uploaded, and then executed on the graphics hardware. Render times for medium to complex geometry can be difficult to determine ahead of time from the raw data, as it is hard to generate an accurate value without first rendering it - a classic chicken-and-egg issue. Also, some data can be hard to verify, and security restrictions can be difficult to enforce once out of the control of the WebGL implementation.
"This might not be such an issue, except for the fact that the current hardware and graphics pipeline implementations are not designed to be preemptible or maintain security boundaries. Once a display list has been placed on the GPU by the scheduler, it can be difficult to stop it, at least without causing obvious, system-wide visual corruption and instabilities. By carefully crafting content, it is possible to seriously impact the OS's ability to draw the user interface, or worse. The difficulty in verifying all content and maintain security boundaries also have potential impact on the integrity of the system and user data."
