You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 4, 2020. It is now read-only.
The a and area elements implement the HTMLHyperlinkElementUtils interface [0]. How are mixin interfaces like this usually included in this repo? It's not a proper element, just an extracted interface, so we can't make a new type in DOM.HTML.Types and check the tag name like this:
-- We can't do this, because an `a` element returns tag name of "HTMLAnchorElement".readHTMLHyperlinkElementUtils::Foreign->FHTMLHyperlinkElementUtils
readHTMLHyperlinkElementUtils = unsafeReadTagged "HTMLHyperlinkElementUtils
Yep, unsafeCoerce is fine here - it's not an upcast, so it won't fail, and since it's an interface there's no corresponding class we can unsafeReadTagged for.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
a
andarea
elements implement the HTMLHyperlinkElementUtils interface [0]. How are mixin interfaces like this usually included in this repo? It's not a proper element, just an extracted interface, so we can't make a new type inDOM.HTML.Types
and check the tag name like this:But we could do this:
and put that interface's members in a
DOM.HTML.HTMLHyperlinkElementUtils
module, like thehref
function. Should we just do that?[0] https://html.spec.whatwg.org/multipage/links.html#htmlhyperlinkelementutils
The text was updated successfully, but these errors were encountered: