-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Namespace support #143
Comments
Might be a duplicate of #140 but that issue focuses entirely on CSS while this one entirely on the DOM |
Thanks for making the issue. I'm really curious about being able to run plotting libraries server side like this: import { DOMParser } from "https://deno.land/x/deno_dom/deno-dom-wasm.ts";
import * as Plot from "npm:@observablehq/plot"
const document = new DOMParser().parseFromString(
`<html>
<body>
<div id="root" />
</body>
</html>`,
"text/html",
);
Plot.barY(alphabet, {x: "letter", y: "frequency"}).plot({document}) which inevitably needs
|
Awesome! Really looking forward to it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like Namespaces are not currently supported.
Namespaces are not too common but are still sometimes found useful, e.g. when working with SVG, OOXML or other non-HTML XML formats.
Would it be possible to add support for this feature and implement functions such as
createAttributeNS
,createElementNS
,setAttributeNS
etc. so that deno-dom can be used in libraries that build and manipulate exotic (or not so much) XML formats?The text was updated successfully, but these errors were encountered: