Is the experimental import for avoiding Polymer.dom documented anywhere?
I'd be interested in trying it out.
On Monday, May 18, 2015 at 8:46:20 PM UTC-4, Eric Eslinger wrote:
One of the really rad things about Polymer (0.5) and webcomponents is that
everything is just DOM. You can pretty
Jim,
You can find the experimental patching import here:
https://github.com/Polymer/polymer/blob/master/src/lib/experimental/patch-dom.html
It has not been tested extensibly and there are a number of caveats (e.g.
there is some performance impact, document.querySelector will traverse
shady
Just wanna make sure...
If I build a web-app that targets the Chrome browser, or any browser that
will have native Shadow DOM support, can I refrain from using the
Polymer.dom APIs, and use native DOM APIs?
On Tuesday, May 19, 2015 at 3:46:20 AM UTC+3, Eric Eslinger wrote:
One of the really
We have experimented with patching dom traversal and mutation api's, and
there's an experimental import in Polymer that does this. It can let some
libraries interoperate more smoothly with Shady DOM powered elements that,
for example, perform distribution. We're continuing to work on it and
On Wed, May 20, 2015 at 10:36 AM, jim.j.si...@gmail.com wrote:
Is the experimental import for avoiding Polymer.dom documented anywhere?
I'd be interested in trying it out.
It's not experimental, it's the same Shadow DOM polyfill that we've had for
a a long time:
On Wed, May 20, 2015 at 12:40 PM, razb...@gmail.com wrote:
Just wanna make sure...
If I build a web-app that targets the Chrome browser, or any browser that
will have native Shadow DOM support, can I refrain from using the
Polymer.dom APIs, and use native DOM APIs?
I would not do this. If
