php - Designing a container page -
are there potentiall pitfalls following idea:
...i want have 1 container page, index.php. header , outlines constant in middle want 1 big panel, loads content external php files, 1 each "slide". when user click link, central div update new content, outer edge remain unchanged.
will able use session variables, etc correctly set-up. realise break browser history other possible ui issues, there techincal barriers.
the session should not lost.
the browser history not need lost - please read onpopstate (and history.pushstate) , onhashchange js events. ajax-heavy sites can determine content loaded way.
one of pitfails is, if using lot of js, events newly loaded content need re-attached, can delegated container not replaced.
jquery's .load() function may useful started.
Comments
Post a Comment