Skip to content
This repository has been archived by the owner on Nov 19, 2018. It is now read-only.

Remove dependence on Polymer #55

Closed
rnicholus opened this issue Apr 4, 2015 · 2 comments
Closed

Remove dependence on Polymer #55

rnicholus opened this issue Apr 4, 2015 · 2 comments
Milestone

Comments

@rnicholus
Copy link
Owner

Now that the WC polyfill has been split off into webcomponents.js, there is probably little reason to use Polymer anymore. I'd love to strip any Polymer-specific code out of ajax-form for users who do not want to depend on Polymer in their projects (such as myself).

@rnicholus rnicholus modified the milestone: 1.7.0 Apr 4, 2015
@rnicholus rnicholus mentioned this issue Apr 4, 2015
rnicholus pushed a commit that referenced this issue Apr 28, 2015
TODO:
- Fix DOM mutation detection /validation code
- Fix custom events in IE
- finish converting tests

#55
rnicholus pushed a commit that referenced this issue Apr 28, 2015
TODO:
- Fix DOM mutation detection /validation code
- Fix custom events in IE
- finish converting tests

#55
rnicholus pushed a commit that referenced this issue May 5, 2015
TODO:
- Fix DOM mutation detection /validation code
- Fix validation tests

#55
@rnicholus
Copy link
Owner Author

Reminder: test mutation observer logic

@rnicholus
Copy link
Owner Author

I'm going to call this one done and ready to be part of 2.0. I'd still like to squeeze in a file-input and late-added input validation test, but the invalid event handler i've registered for these tests does not fire in the context of my unit tests, even though it appears to fire IRL.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant