Prevent incorrect caching of ToasterTable data so it doesn't go stale as the user navigates browser history with back/forward.
Changes since 75bad1b64bd485a50af69ed1f8663a0dadbb5f9e are in: git://git.yoctoproject.org/poky-contrib, elliot/toaster/bad_caching-7660 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=elliot/toaster/bad_caching-7660 Related bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7660 I haven't tested every permutation of table navigation with this patch, but issue 7660 is fixed. NB Bug 8294 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=8294) causes incorrect data to display in a similar way, but the root cause seems to be different (it's due to incorrect context update there, rather than caching). This patch doesn't fix that. Elliot Smith (2): toaster: Don't add new history entries when table data loads toaster: Don't HTTP cache ToasterTable responses bitbake/lib/toaster/toastergui/static/js/table.js | 2 +- bitbake/lib/toaster/toastergui/widgets.py | 5 +++++ 2 files changed, 6 insertions(+), 1 deletion(-) -- Elliot Smith Software Engineer Intel OTC --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
