Problem:
If user open 2 (or more) browser-tabs with different extended-search value then $_SESSION[“something”] will fire wrong value into $rsnew[“date”].
Thanks for the pointer but for my specific case I think I’ll better use client session-storage and add some logic into Row_Inserting.
I’ve been SO-ing this problem for hours, turns out this is server vs. client kind of problem. Working server-side for client-side problem could cause more problems than it solved. There’s no way for server to know “tab-identity” of client.
The appropriate approach, surely then, is to work client side.
Local/Session storage does not secure by nature. Cookie does. So I think this problem should be solved by cookie.
The solution I provided is designed to resolve your exact issue: multiple tabs open in the same browser
With this solution, the server DOES know the identity of every relevant tab or window, and ensures that the correct $_SESSION variables are used in relation to its activities (which includes search fields as well as master / detail data).