Ben Navetta

Sorry about all the delays - I've been busier than expected with work. @dpinart do you think those behaviors are something that would make sense to include in the plugin?...

Instead of using `on-content-scroll`, you can use Aurelia's `content-scroll.trigger="scrollHandler($event)"`. In theory, `.delegate` should work as well, but I've been having some issues with it.

I just had it working with `content-scroll.delegate`. What version of Aurelia are you using? ``` html Hello, World! ``` As for the `paper-input`, I'm not sure where this is actually...

For `change` in particular, there might be something about the [shadow DOM spec](https://github.com/PolymerElements/paper-input/blob/444102ca23bf0631beda2babe4457edac2f7e2c4/paper-input-behavior.html#L524-L536) that Polymer is accounting for.

It looks like Webpack itself doesn't support Polymer yet, based on webpack/webpack#547. There's a polymer-loader for Webpack that might help. If I recall correctly, not using aurelia-html-import-template-loader appeared to work...

@dpinart thanks! I'll add something to the README

I'd guess that's because aurelia-polymer doesn't have the aurelia build configuration in its `package.json`, so the bundler doesn't know about the `au-custom-attribute-select` file (which would probably be another ticket)

Hi @HIRANO-Satoshi, I'm no longer using Aurelia or Polymer, so unfortunately I'm not familiar enough with Polymer animation to know how to fix it.

Your condition for `checked.bind` should be `$parent.selectedAnnotationOption === option` to compare the selected option to the option for each radio button. `$parent.selectedAnnotationOption` will be a string that evaluates to true,...

I think this and a lot of the other selection issues like #12 and #17 come down to PolymerElements/iron-selector#42, where it's not looking into nested elements, either the `` or...