https://bugzilla.wikimedia.org/show_bug.cgi?id=23772
Jesús Martínez Novo <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Jesús Martínez Novo <[email protected]> 2012-09-30 12:46:42 UTC --- When you do a GO-search and the search engine redirects you to the article with that name, it could send an additional cookie (with a short expiration time, like 1 minute or so) with the target fullpagename and the original search term. Then the client JS may scan for the existance of such cookie and when it matches the fullpagename with the current fullpagename of the article then display that message (and optionally make the cookie expire so the message isn't printed again on page reload during the 1 minute the cookie will remain on the client). This solution won't interfere with caching and won't leave additional query strings. Sure, it would fail for browsers with cookies disabled, but it's a minor issue and that's usually what happens when you have cookies disabled anyway ;) This proposal may fail on some race conditions: * The user submit a second search form while the first one hasn't loaded the target page yet: The first result page may not get the message because the second search form already overwrote the cookie. * The user open the same page or reloads while the cookie hasn't expired yet, the message would be displayed. Make the cookie expire (set the cookie with a past expiration date) when the message is processed would prevent this. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
