Exponentcms Exponent CMS → 2.1.0

Comments and changes to this ticket

• 

  dleffler October 20th, 2011 @ 02:08 PM

  This may not be as simple as it sounds. Though tab history has been implemented on several views, it's only those where they are the only thing displayed since the method above refers to tab numbers and these numbers are identical for each tabview container. Also, selecting the frst tab causes the page to scroll to the top by virtue of the way anchors and links work.

  Another issue is that we set expHistory coming into the page, not going out so expHistory points to the page, not the updated url shown in the address when switching tabs.

  In theory we could use the session or cookies to track the tab selected and then do some more extensive checking in the javascript used from the above example, or implement some php code that does a 'javascript:history.go(-1)' instead of pulling the page off the expHistory stack.

  There are some hacks that work for particular pages/actions, but are not a system-wide solution which is what is needed.

• 

  dleffler May 15th, 2012 @ 12:15 AM

  • State changed from “new” to “open”

  [bulk edit]

• 

  dleffler October 6th, 2012 @ 06:42 PM

  • State changed from “open” to “resolved”
  • Assigned user set to “expNinja”
  • Milestone set to “2.1.0”
  • Milestone order changed from “104” to “0”

  With the new exptabs implementation, this is built-in and we've converted all tabs to use it.