Support extension instrumentation
Need a way to support both built-in and custom JS extension instrumentation. Really two parts:
- rework things to use enum lookup wherever possible (to bring in enums from extensions)
- instrumentExtension method to apply rewriting to extension methods
Special cases still required for extensions that modify resources - not sure there is a way around that.
While it would be great if full extension instrumentation would work, for now I'd actually settle for a warning for extensions that are not supported. I've been banging my head against the wall trying to figure out why VAO didn't work at all, until I tried disabling inspector...
Otherwise: fantastic tool, couldn't live without it! ;)
Vote for the warning, or at least a note in the readme - I too have been trying to debug VAOs.
Note: using chrome extension version 1.13