File Changes for tdreszer

v293_preview to v293_preview2 (2013-11-18 to 2013-12-02) v293

• src/hg/hgTracks/hgTracks.c
  • lines changed 7, context: html, text, full: html, text
    Adding back-button suppoirt through jquery.history.js API. At this time back-button support is only for position. At all times the image should agree with the cart. This means that moving forward, the image must be stacked in window.History.state and moving back, the image must be refreshed using the old location. Note that full page refreshes complicate the picure. Back-button will recall a client side cached page which may be greatly out of sync with cart. Stretegy is to use image only update, but if all else fails, a full page reload is used. This means, that image only update is preferred going forward. To that end, several previous places that required full page refresh can now be done with image only rtefresh. At this time, anytime the chrom changes, the page will be fully refreshed. Redmine #7473.
• src/hg/js/hgTracks.js
  • lines changed 357, context: html, text, full: html, text
    Adding back-button suppoirt through jquery.history.js API. At this time back-button support is only for position. At all times the image should agree with the cart. This means that moving forward, the image must be stacked in window.History.state and moving back, the image must be refreshed using the old location. Note that full page refreshes complicate the picure. Back-button will recall a client side cached page which may be greatly out of sync with cart. Stretegy is to use image only update, but if all else fails, a full page reload is used. This means, that image only update is preferred going forward. To that end, several previous places that required full page refresh can now be done with image only rtefresh. At this time, anytime the chrom changes, the page will be fully refreshed. Redmine #7473.
• src/hg/js/jquery.history.js
  • lines changed 1, context: html, text, full: html, text
    Checking in jquery.history.js which is a plug-in that enables back-button support. This is a 3rd party file and is untouched by UCSC.
• src/hg/js/makefile
  • lines changed 1, context: html, text, full: html, text
    Adding back-button suppoirt through jquery.history.js API. At this time back-button support is only for position. At all times the image should agree with the cart. This means that moving forward, the image must be stacked in window.History.state and moving back, the image must be refreshed using the old location. Note that full page refreshes complicate the picure. Back-button will recall a client side cached page which may be greatly out of sync with cart. Stretegy is to use image only update, but if all else fails, a full page reload is used. This means, that image only update is preferred going forward. To that end, several previous places that required full page refresh can now be done with image only rtefresh. At this time, anytime the chrom changes, the page will be fully refreshed. Redmine #7473.