You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've just spent about an hour debugging why my ajax link doesn't work. I had an anchor:
<ahref="#">Foo</a>
And I was dynamically changing its href after click on another element. I was using .prop() to change anchor's href. After changing it to .attr(), ajax started working.
Really a WTF. My question is: Is it a bug or a hidden feature with no warning?
The text was updated successfully, but these errors were encountered:
I've been digging a bit and maybe found a root of the problem.
The difference between .prop() and .attr() seems to be that prop returns absolute URL, even though it's set as relative. After doing what I said in first post (getting link by prop and putting it to another anchor), this then makes the following condition in validation extension to fail:
Hi, I've just spent about an hour debugging why my ajax link doesn't work. I had an anchor:
And I was dynamically changing its href after click on another element. I was using .prop() to change anchor's href. After changing it to .attr(), ajax started working.
Really a WTF. My question is: Is it a bug or a hidden feature with no warning?
The text was updated successfully, but these errors were encountered: