On 25 Feb., 14:11, David Muir <davidkm...@gmail.com> wrote: > I think what P is referring to is what using cookies enables: remember > what tab you were on when refreshing the page. > > Which makes me wonder, why not have an option to have the hash set > instead of using a cookie? > > eg > index.html: > > <div class="tabs"> > <ul> > <li><a href="#tab1">Tab1</a></li> > <li><a href="#tab2">Tab2</a></li> > </ul> > <div id="tab1"></div> > <div id="tab2"></div> > </div> > > If I type index.html#tab2 in the address bar, it loads the page with > tab2 selected. Which is great, as it lets me jump to a specific tab from > a different page, and refreshing the page means that tab2 stays selected. > Currently we need to use a separate plugin to handle this.
Huh? This functionality is implemented, actually right from the very beginning... > Looking > through the source, it says that the hash is being stripped from the url > until issue #3808 is fixed. Just checked and 3808 has been fixed, so > does that mean we can have our hashes again? :-) That's another bug - related to ajax tabs with a hash in their href attribute. But that has nothing to do with the hash in the page's url that contains the tabs. --Klaus
