Back to issue list Export

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.

travisb 2012-10-18 21:59:08
hash: a2ecc3a48fc0f911311dcb9508b667cd9bbb3aab55566d6c2d0b50bc72b2b203
Date: 2012-10-18 21: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.

travisb 2013-02-26 23:28:35
hash: 098c929ec6a932855a0c64d170d9639e9289bfa04b98b70d7b7eef107032ebc7
Date: 2013-02-26 23: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.

travisb 2013-02-27 18:18:32
hash: 9364b58353739c068423e9c628b5c123d52a177300607b74b8e0d20fd747fff4
Date: 2013-02-27 18: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.

travisb 2013-02-27 23:48:23
hash: 5ccc66f3b48063dc42aa4b3486fe088c536f88588c07aec3ba057455d5d584a5
Date: 2013-02-27 23:48:23
User: travisb

I've completed the readonly view filter saving using sessionStorage.

travisb 2013-03-20 21:19:51
hash: 38442ea057d8a748b5efb600e5c06dc12afb40bb4db3126a71657b1f66e634e4
Date: 2013-03-20 21: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