Prevent incorrect caching of ToasterTable data so it doesn't go stale as the user navigates browser history with back/forward.
v2: Remove code to push and pop context data into the browser history, as we now just make fresh requests to the server instead. Changes since poky-contrib/toaster-next @ 97e5625bb7b8f8de8fda0fb4dd188bf107a5f4fa 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 Elliot Smith (3): toaster: Don't add new history entries when table data loads toaster: Don't HTTP cache ToasterTable responses toaster: Don't store table data in the browser bitbake/lib/toaster/toastergui/static/js/table.js | 12 ------------ bitbake/lib/toaster/toastergui/widgets.py | 6 ++++++ 2 files changed, 6 insertions(+), 12 deletions(-) -- 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
