-
Notifications
You must be signed in to change notification settings - Fork 45
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
Stop disabling target element pointer events #245
Stop disabling target element pointer events #245
Conversation
c98732f
to
76bba0d
Compare
Side note: Whenever |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember we were not going to just remove this stuff, but allow a clickable: false
to be passed to enable it?
Okay, I was experimenting with the I can refactor this, though, after some of our discussion about keeping things in |
@rwwagner90 @chuckcarpenter Thinking about how to document this... this might be a good opportunity to clean up the README and only document the extra step options (while linking to docs for Shepherd's step options. Also, what you think about |
I still kind of like |
Let's keep all the docs for now.
I'd like a simpler name. |
|
I think I'm okay with |
76bba0d
to
1864d8d
Compare
@rwwagner90 Just updated and rebased around implementing a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We've got some code climate issues, but we can fix those later. Thanks!
I got started on a branch in
shepherd
that will allow for adisableAttachTarget
step option.In the meantime, though, we can get started with the corresponding change here.