[scoped-custom-element-registry] Integrate and test with shady-dom/shady-css polyfill

[kevinpschaaf]

Task: The scoped-custom-element-registry polyfill is currently only tested to work on browsers implementing the native web components specs (Custom Elements & Shadow DOM). This task is to investigate and make changes necessary to integrate and test the scoped registry polyfill when loaded in conjunction with the ShadyDOM & ShadyCSS polyfills.

ShadyCSS currently scopes element CSS by tag name; the ability to have multiple tag names scoped differently would require some sort of integration of this polyfill with ShadyCSS to add an additional scoping class/attribute per registry.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.