custom-attributes
custom-attributes copied to clipboard
matthewp
Defining custom attributes that provide rich mixin behavior
The DOM already has global attributes and it may want to reserve the no-hyphen space for future builtins. Any thoughts on this?
custom attributes don't work in shadow roots (MO subtree observation doesn't move into shadow roots)
(Continuing from https://github.com/matthewp/custom-attributes/issues/3#issuecomment-457880460) When we register a custom attribute, it only works in the root light tree, and the functionality doesn't carry over across ShadowDOM boundaries into shadow roots. After...
This also prevents from modifying the custom attribute's `this.value` when disconnected, so that the old value can be used in the disconnected logic (because the value wasn't changed, the attribute...
Another issue I have is that if a user defines a custom element _**after**_ defining a custom attribute, then if the attribute tries to use any of the element's APIs,...
This [DOM issue](https://github.com/whatwg/dom/issues/522) is giving me a hard time, because I'm trying to detect attributes on custom element construction so that I can detect side effects of custom attributes, and...
We could keep the global build as `attr.js` and add an `attr.mjs` as an ES module build... or just get rid of the global build. Thoughts @bedeoverend ?
If more than one library import `CustomAttributesRegistry` and instantiate it on `document`, is this okay? Or should `new CustomAttributesRegistry(document)` return the existing registry for the given `document` if it already...
Currently custom-attributes doesn't specify what browsers it supports, so thought it might be worth discussing what to aim for. I've been using it in https://github.com/simplaelements/simpla-paths and that's been running well...
