-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOM Api fails to select an element in a dom-repeat in polymer 1.1 #2276
Comments
I'm not able to confirm this issue. Here's a jsbin that confirms it's working (press the Test button and see the console output): http://jsbin.com/hizevocota/edit?html,console,output Would you mind providing more info about when you're calling this method? |
I'm calling this method from an on-tap handler, though the later doesn't really matter. Calling The elements which never appear in these queries are all from within a dom-repeat template, located here: When I try to fetch a particular element from within, the result is always undefined: The component which holds all of that html as its content is here: |
Hello, i have the same problem. A working demo with the bug can be found here: http://jsbin.com/razotukane/1/edit?html,console,output When you open the drawer and click on an item the console output should be 4 (the number of items). Instead it is 0. The function that can't find the elements is called from a tap event on one of the items that get rendered by the dom-repeat. If you go to the head element and change the polymer.html to the 1.0.9 version (already in comments), everything works as it should. It also works if you change from shady to shadow dom. |
confirmed. The http://github.com/m4b/silicon-hex-table when polymer was updated to 1.1. Further investigation confirmed, as mentioned above, that Pinning polymer to 1.0.9 returns the highlighting behavior as expected, and the nodes returned by Note: the element generated was fairly complicated, perhaps this had something to do with it? <template is="dom-repeat" items="[[_table]]" as="row">
<tr>
<td class="offsets">
<span>[[_getOffset(offset, index)]]</span>
</td>
<td class="bytes">
<template is="dom-repeat" items="[[_get(row)]]" as="col"><span id$="[[col.id]]" class="hex">[[_getHex(_bytes, offset, col)]]</span></template>
</td>
<td class="asciiheader">
<template is="dom-repeat" items="[[_get(row)]]" as="col"><span id$="[[col.hid]]" class="ascii">[[_getAscii(_bytes, offset, col)]]</span></template>
</td>
</tr>
</template> |
Ok, can confirm this problem now and it's definitely a regression. We're working on fixing it asap. |
Still experience this problem with Polymer 1.6.1 |
Edit: Sorry. Nevermind. xD It was another issue. |
Problem still persists with Polymer 1.7. |
Doing something like:
worked pretty well in polymer 1.0. Both elements in in the local dom as well as results from dom-repeat templates are selected. With polymer 1.1, the elements produced with dom-repeat are not selectable anymore.
The text was updated successfully, but these errors were encountered: