should createContextualFragment be added in Document / DocumentFragment?

[caub]

instead of in Range prototype, I think it could be great to just do document.createContextualRange('<br>')

[annevk]

It would help if you started with a problem statement, before going to what the solution might look like. See also https://whatwg.org/faq#adding-new-features.

[caub]

Hi, right, sorry

Basically I often need this feature 'isomorphically' (browser + node) (example: writing a module parsing html, filterXSS, etc..), jsdom has a convenient JSDOM.fragment(str) static helper.

I wonder a bit why it was added in Range.prototype, it doesn't even return a Range. So the current way to access createContextualFragment in DOM is not practical, maybe you would agree

[annevk]

It's a legacy API that all browsers were forced to adopt. I don't recall reading about the design history.

[caub]

I think there's some work concerning <template> that could make html parsing easier. Thanks, I knew Range and editing APIs are more than 15 years old, but I was wondering if this particular method could be extracted in a more accessible class/object

let's close it, maybe and thanks again