Reece H. Dunn

I'd be happy to simplify the option set to `{"method": "html", "html-version": "5"}` and any other vendor/implementation supported values with the description saying that `5` can refer to any of...

The intention w.r.t. parsers like TagSoup and HTML tidy is that they are intended to be vendor-specific extensions. The mentions in the spec are non-normative notes/examples. I can update the...

Given we are simplifying this, I suggest just using an implementation defined version of HTML 5 - 5.2 and WHATWG HTML Living Standard. That will then take care of parsing...

I think it makes sense to keep the option. The spec should have links to the relevant Living Standard sections, and I've also detailed the issue in https://github.com/qt4cg/qtspecs/issues/75 (although the...

I've had a look at implementing this as a custom Python node and ran into issues with allowing any types on inputs that forward the actual type to the corresponding...

The things in the use cases I listed above are things I'm considering on grouping. I've been organizing the through data in workflows into data buses that move through the...

For reference, I've created https://github.com/rhdunn/comfyui-bus-plugin which has a collection of these different node types that I'm finding useful in my own workflows. One advantage I've noticed with this approach is...

For example, this is a workflow of mine where it will be helpful (see the top output line): 

So we are proposing making `return` a reserved computed node constructor keyword like is done for function calls? I think that makes sense. Thus, we are proposing: 1. making StringLiteral...

As noted in the meeting, the `type` and `record` keywords should be added to the reserved function name list.