You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When hovering over the first line (the one that is instantiated with the <use> SVG element, Errors are repeatedly thrown from wrappers.js:30, with the following callstack:
wrapper.js:30:
function assert(b) {
if (!b)
throw new Error('Assertion failed');
};
wrapper.js:290:
function wrap(impl) {
if (impl === null)
return null;
assert(isNative(impl));
return impl.polymerWrapper_ ||
(impl.polymerWrapper_ = new (getWrapperConstructor(impl))(impl));
}
event.js:190:
function dispatchOriginalEvent(originalEvent) {
// Make sure this event is only dispatched once.
if (handledEventsTable.get(originalEvent))
return;
handledEventsTable.set(originalEvent, true);
return dispatchEvent(wrap(originalEvent), wrap(originalEvent.target));
}
This is solved by adding the noscript tag to the Polymer element or replacing the lines with direct instantiation (<line>).
Is Polymer scanning the <use> and digging out the href for something?
The text was updated successfully, but these errors were encountered:
<svg:use> more or less duplicates shadow dom and custom elements. SVGElementInstance uses its own parentNode, firstChild, lastChild, previousSibling, nextSibling and childNodes which are all SVGElementInstance and SVGElementInstanceList respectively. The good thing though is that these are immutable so we do not need to support appendChild etc.
I have the following component, which creates an SVG three line icon used for menus in modern UIs:
When hovering over the first line (the one that is instantiated with the
<use>
SVG element, Errors are repeatedly thrown fromwrappers.js:30
, with the following callstack:wrapper.js:30
:wrapper.js:290
:event.js:190
:This is solved by adding the
noscript
tag to the Polymer element or replacing the lines with direct instantiation (<line>
).Is Polymer scanning the
<use>
and digging out thehref
for something?The text was updated successfully, but these errors were encountered: