If you setup some sort and filter settings for the issue list, navigate away from the issue list and then back again you have to setup the sort and filter selections again. This should be remembered within a single browser view chain.
The most obvious way to remember settings between views of the index is to stash this in a cookie. This doesn't work for two reasons. The first is that it won't be different between browser sessions (ie. one browser can't have two different tabs open and keep different index settings). The second is that it would be difficult to shoehorn into the code layout since the output isn't buffered and you can't set headers after you send the html preamble.
The second most obvious way is to carry the issue list option around. This can be done fairly easily for the issue pages. The question is how to accomplish this for the new comment or other push pages since they'll use query options for other things.
Since a new readonly view has been created there are now two parts to this. First the support must be added for the normal live web UI, but it must also be added for the static readonly view.
There appears to be a way that the readonly view can use HTML5 sessionStorage to accomplish this. I'm still not sure how to accomplish this with the live view.
I've completed the live web view using a session query parameter that is passed around everywhere and storing the settings which correspond to those session internally.
If you setup some sort and filter settings for the issue list, navigate away from the issue list and then back again you have to setup the sort and filter selections again. This should be remembered within a single browser view chain.
Date: 2012-10-19 04:59:08
User: travisb
The most obvious way to remember settings between views of the index is to stash this in a cookie. This doesn't work for two reasons. The first is that it won't be different between browser sessions (ie. one browser can't have two different tabs open and keep different index settings). The second is that it would be difficult to shoehorn into the code layout since the output isn't buffered and you can't set headers after you send the html preamble.
Date: 2013-02-27 07:28:35
User: travisb
The second most obvious way is to carry the issue list option around. This can be done fairly easily for the issue pages. The question is how to accomplish this for the new comment or other push pages since they'll use query options for other things.
Date: 2013-02-28 02:18:32
User: travisb
Since a new readonly view has been created there are now two parts to this. First the support must be added for the normal live web UI, but it must also be added for the static readonly view. There appears to be a way that the readonly view can use HTML5 sessionStorage to accomplish this. I'm still not sure how to accomplish this with the live view.
Date: 2013-02-28 07:48:23
User: travisb
I've completed the readonly view filter saving using sessionStorage.
Date: 2013-03-21 04:19:51
User: travisb
I've completed the live web view using a session query parameter that is passed around everywhere and storing the settings which correspond to those session internally.
Tracked by Nitpick