[RTKO] dev#188879 : Agenda : enabling back button on chrome to use same parameters
Closed
requested to merge dev#188879_mel_amelioration_de_la_navigation_dans_la_page_agenda into master
1 unresolved thread
Merge request reports
Activity
Filter activity
added 1 commit
- 5c580862 - dev#188879 : Agenda : enabling back button on chrome to use same parameters
added 1 commit
- de821c8a - dev#188879 : Agenda : enabling back button on chrome to use same parameters
added 1 commit
- a4face61 - dev#188879 : Agenda : enabling back button on chrome to use same parameters
added 1 commit
- e7b2c4e0 - dev#188879 : Agenda : enabling back button on chrome to use same parameters
requested review from @gloas
Resolved by Henri-Damien LAURENT- Resolved by Henri-Damien LAURENT
37 40 38 41 return 39 42 $this->renderFilters($calendar, $calendar->getArticles()) 40 . 41 $widget->renderElements(); 43 . $widget->renderElements() 44 . $this->_editBackButtonLink($calendar); 45 } 46 47 48 protected function _editBackButtonLink(Class_Calendar $calendar) : string 49 { 50 if (!$this->view->isAjax()){ 51 Class_ScriptLoader::getInstance() 52 ->addJQueryReady('$(".calendar").masonry();'); -
ATTENTION, masonry c'est le rendu grid ou wall qui doit gérer ça.
Voir si le beAjax / isAjax reste utile une fois déplacé dans le rendu adéquat.
un agenda n'est pas systématiquement un masonry.
Donc sur les calendrier on va avoir des erreur JS car masonry ne sera pas connu.
Edited by Ghislain Loas changed this line in version 6 of the diff
- Resolved by Henri-Damien LAURENT
- Resolved by Henri-Damien LAURENT
- Resolved by Henri-Damien LAURENT
- Resolved by Henri-Damien LAURENT
- Resolved by Henri-Damien LAURENT
- Resolved by Henri-Damien LAURENT
added 1 commit
- 0402e5da - dev#188879 : Agenda : enabling back button on chrome to use same parameters