Re:Chrome dev on WebGL security and Microsoft bullshit
by masklinn on Tuesday June 21, 2011 @05:45AM
(#2678058)
> Running a plugin is different from using a feature in the browser - people often disable the plugins and are conscious about plugins being an attack surface so the admins often deploy policies disabling use of plugins.
1. It's not hard to expose a way to disable WebGL support, especially for admins. And no, overall people do not often disable plugins and they're not very conscious about plugins being an attack surfaces (though admins may be).
2. Are you saying it's OK to ship technologies known to be broken as long as it's in a plugin? Do you really think that makes sense?
1. It's not hard to expose a way to disable WebGL support, especially for admins. And no, overall people do not often disable plugins and they're not very conscious about plugins being an attack surfaces (though admins may be).
2. Are you saying it's OK to ship technologies known to be broken as long as it's in a plugin? Do you really think that makes sense?