-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix history api #266
base: master
Are you sure you want to change the base?
fix history api #266
Conversation
handle only own history stack & make history api actually work
Pokud to ma resit neprijemnej problem, nefunkcniho tlacitka BACK, tak mi to neresi :/ To kdysi urcite fungovalo, ale mam pocit, ze se to rozbilo, kdyz nekdo "fixoval" (a ja mergoval) fungovani na pri vice gridu na jedne strane :/ |
Nie, riesit to ma najma to, aby sa grido nesnazilo handlovat VSETKY zmeny stavov, ale len tie svoje (params.grido=true). |
Muzes prosim popsat, jak to zreprodukovat? Diky |
var state = $.data(document, this.grido.name + '-query') || '', | ||
query = window.location.search; | ||
|
||
if (state !== query) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
staci, ked bude state
= '' a query
lubovolny string (teda niekde mimo grido niekto nastavi hash), tak grido robi request na refresh. Aspon ak si dobre pamatam, tak toto som riesil
To prave nedokazu nasimulovat :/ Pouzivas nette.ajax.js plugin? Ten ajax request ze serveru musi vracet |
Ano, pouzivam. |
handle only own history stack & make history api actually work