hi pedalpete, your solution does work perfectly fine, sorry for not
making that clear. but if we look beyond the initial implementation we
begin to see a problem: this solution requires two separate pieces of
code to be maintained to handle certain modifications.
for instance, if the link needs to be changed so that it opens in a
separate window, both the <a> tag and the jq code need to be modified;
and keep in mind these two pieces of code may reside in two different
files. many developers will find the first instance (either the <a> or
the jquery), change it, and move it back to production and think the
problem was completely resolved, then not understand why sometimes
users are going to the right page and sometimes they are still going
to the old one.
so your proposed solution does resolve the issue originally raised,
however, there are long term issues with it and i would like to see if
there is a better solution that does not introduce the maintenance
problem stated above.
i appreciate your feedback and hope that i've made my point, however
inelegant, a little clearer!
On Jan 13, 6:38 pm, pedalpete <p...@hearwhere.com> wrote:
> Hi Bill,
>
> I'm still learning lots, and was hoping you could better explain what
> was wrong with my solution (as it seems the other solutions are FAR
> more complicated.
>
> What I was trying to acheive was to just disable the link for
> javascript enabled browser, and keep it enabled for those without
> javascript.
>
> As the link is inside the cell, and the javascript action is triggered
> on any click within the cell, I believe my recommendation should work
> well in all instances.
>
> I believe with .unbind('click'), the click on a link will not be
> interpreted at all, and that the JS will always take the action.
>
> I may be misunderstanding what is happening under the covers, but what
> I recommend does not unbind after a click, it would unbind the clicks
> at load time if I've got it right.
