Ticket #859 (closed issue: wontfix)
[M] Browse tabs jumping around DataProviders
| Reported by: | selatham | Owned by: | lawrence |
|---|---|---|---|
| Priority: | discussion | Milestone: | PROD Final |
| Component: | discovery | Version: | |
| Keywords: | Cc: |
Description
Now that we've got more than one installation up and connecting to Browse I find that strange things happen in tabs. I started at http://wwwdev.neodaas.ac.uk/projects/ndg/discovery and searched on badc. Viewed a badc record, browsed it then went back to search tab. This was then http://ndgbeta.badc.rl.ac.uk//discovery. Then when I went to results I was getting some other unrelated BODC results. Tried Ctrl+R but no difference. Is this to do with the fact that I had used an ndgbeta.badc discovery in another Mozilla tab previously? Or is it our caching? or something else?
Change History
comment:2 Changed 14 years ago by lawrence
- Priority changed from critical to discussion
- Status changed from new to assigned
- Type changed from defect to issue
Hmmm. This is doing what it should do, but maybe not what we want it to do :-)
You start at neodaas ... when you browse to a badc record, you are now at the badc site, and the cookie which provides the results tab has come from the last results you have had with a badc search as opposed to the results of the last search you did (which was at neodaas).
The way around this is to NOT jump sites with browse, but instead to haul the (secure or otherwise) browse record back to the original site. I can do this. Should I?
(A similar problem will expose itself pretty rapidly with the shopping cart etc, we should probably talk it thru at the next meeting).
comment:3 Changed 14 years ago by lawrence
Alternatively, we could force all non-local browse links to carry a flag which causes a reset of the search results, or even post the search query so it can populate the browse tab ...
... but what if one was using browser tabs and deliberately trying to keep them separate?
