202
edits
Browser History:Redirects: Difference between revisions
Jump to navigation
Jump to search
m
→History View
BrettWilson (talk | contribs) m (→History View) |
BrettWilson (talk | contribs) m (→History View) |
||
| Line 46: | Line 46: | ||
Coalescing redirects will be an optional portion of history queries, so callers can get the raw visit data if desired. | Coalescing redirects will be an optional portion of history queries, so callers can get the raw visit data if desired. | ||
When the history system gives query results by visit, we will hide the sources of redirects and only show destinations. For all visits X that result in redirects to Y, we will remove X and add Y (if Y isn't already in the result set). Then repeat this | When the history system gives query results by visit, we will hide the sources of redirects and only show destinations. For all visits X that result in redirects to Y, we will remove X and add Y (if Y isn't already in the result set). Then repeat this operation until there are no redirected visits (to handle multiple redirect hops) | ||
This handles many cases: multiple redirected destinations from X, mutiple redirect sources from Y. It also means that if you do a query and it matches the source, you'll get the destionation even if the query doesn't match the destination. There are some strange results, however: | This handles many cases: multiple redirected destinations from X, mutiple redirect sources from Y. It also means that if you do a query and it matches the source, you'll get the destionation even if the query doesn't match the destination. There are some strange results, however: | ||