Home/ Questions/Q 716551
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T05:18:43+00:00

$(#table_exams tbody tr).click(function (event) { window.location.href=# +$(this).attr(exam_ID); window.location.href=/medilab/prototypes/exams/edit?examId= + $(this).attr(exam_ID) +&referer= + referer; row_select(this);

  • 0
    $("#table_exams tbody tr").click(function (event)
        {
            window.location.href="#" +$(this).attr("exam_ID");      
            window.location.href="/medilab/prototypes/exams/edit?examId=" + $(this).attr("exam_ID") +"&referer=" + referer;     
            row_select(this);
        });

 $(document).keypress(function (event) {
            if(event.keyCode==13) $(row_selected).trigger("click");

        });

I have a little problem with this only in chrome…When user goes back chrome ignores the last href hash that my script added..but when i do a doubleclick its ok…
IE and Firefox work great…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would try location.hash which is a bit more consistent in behavior, like this:

    window.location.hash="#" +$(this).attr("exam_ID");      
window.location.href="/medilab/prototypes/exams/edit?examId=" + $(this).attr("exam_ID") +"&referer=" + referer;

    Chrome tends to optimize the callstack, it’s tracing engine knows the location.href is only set in a way that results in an action in the last set…this prevents that tracing optimization from happening (jQuery has similar issues here, there’s specific code in the Sizzle engine to cope with the fact Chrome does this).

    • 0