Dave Dixon

I guess this case is actually covered if we have the ability to specify the DOM API implementation. Maybe a nice-to-have for this would be the ability to register the...

I was going to provide my own implementation of the DOM API which did the magic for the insert/append cases, otherwise called through to Polymer's DOM API. But thinking about...

Ok, I think I'm starting to get it. Seems like implementing IVirtualElement is for the case where you want to completely take over the DOM management from that point forward,...

That should do it.

I'm at a good spot in my project where I could tackle this, if you want some help.

As often happens, filing an issue got me thinking more deeply about my problem. We're making HTML custom elements based on freactive and Datascript. I had built some lenses to...

Not sure this is working as you planned. Here's the code I used to test: ``` clojure (ns freactive-sandbox.rx-test (:require-macros [freactive.macros :refer [rx debug-rx]]) (:require [freactive.core :refer [atom cursor]] [freactive.dom...

Here's the diff: https://github.com/aaronc/freactive/compare/develop...allgress:develop I am using develop HEAD.

I agree that inheritance is the right way to go, but I couldn't figure out how to override implementations in ClojureScript, since there's no `extend`. Do you know?

Actually, I think there is a case where you conceivably need to use `Polymer.dom` in a subtree, and that's to support style scoping in shady DOM. They do some tricks...