Should this extension be used everywhere that Chrome allocates multisampled renderbuffers (for example, potentially in GPU rasterization), or only for WebGL's back buffer ( https://cs.chromium.org/chromium/src/third_party/blink/renderer/platform/graphics/gpu/drawing_buffer.cc )?

For uses outside of WebGL, it would be interesting to see if tuning the quality/storage samples improves performance on Ganesh's multi-sampled path rendering with good quality.

We are more interested in WebGL uses for Grunt https://cs.chromium.org/chromium/src/third_party/blink/renderer/platform/graphics/gpu/drawing_buffer.cc,  
with samples = 4, storageSamples = 2  for this bug.


Said that, extension can be used for anything related to MSAA quality and behavior.

recommended setting are:
samples = 16, storageSamples = 4
samples = 8, storageSamples = 4
samples = 8, storageSamples = 2
samples = 4, storageSamples = 2

It can be used when wants high MSAA quality (e.g. 8x or 16x), but the number of intersecting primitives is low. 
 
The extension gives the memory footprint and bandwidth usage of 2x or 4x MSAA with the quality equivalent to higher AA modes 
as long as the number of primitives contributing to a pixel is <= storageSamples.

Will suggest to use this issue for Grunt WebGL performance and might take another uses separately. 
Was also wondering if keeping EQAA enablement for Grunt in a flag will be good idea? 

Whom would be a good owner for this?