One suggestion we had on that issue is to enable it in
`capybara/rails`, but even that seems wrong to me. It seems like
people should consciously make the choice to do this funky thing. It
doesn't make sense, imo that Capybara behaves differently than a
browser would by default.
On Thu, Jul 19, 2012 at 6:19 PM, Jo Liss <joli...@gmail.com> wrote:
> Hey Jonas, hey list,
> Just a quick note on Capybara 2: The biggest upgrade pain point
> (besides making matchers non-ambiguous, which is good) is a minor
> feature: Non-GET links in RackTest with Rails (e.g.
> data-method="delete"). I think they went away at some point (not sure
> which commit), and I agree it's reasonable, but the compatibility
> breakage is being pretty painful.
> This is especially so when there is an additional data-confirm="Are
> you sure?", because then I have to not only set `js: true`, but also
> stub out window.confirm.
> Just wanted to post this in case you want to re-add it, Jonas. I'm
> personally on the fence about it.
> Jo Liss