When designing pages for a project that uses dynamically loaded pages/content (the website will not be accessible to search engines, so that's never a concern. Only for desktop PC use. Not for mobile phone use. Using Spring MVC), is it wiser to:
1. Create a page with a header, menu and footer and dynamically load the content in the center, according to what the user chooses from the menu?
OR
2. Create separate html pages for the header, menu and footer and design a dynamic page which with center content, that will dynamically load the header, menu and footer?
- A priority for this project is to use up as less of the network bandwidth as possible.
- My main concerns are that if I use iFrames to load the header, menu and footer, there might be problems when resizing the page.
Doesn't GMail work by loading only the center content? Do you know how they manage to allow the User to use the back button of the browser inspite of the content being loaded dynamically?
This is what the layout would look like:
XMLHttpRequest cannot load file:///F:/Projects/Frontend/header.html. Cross origin requests are only supported for protocol schemes: http, data, chrome-extension, https, chrome-extension-resource.
header.html
by using local access. Try using a HTTP server and then change the url scheme tohttp
rather thanfile