Save page
First, make sure the page you are uploading is saved on your computer or server. If the page has not been saved, you are uploading the page without any changes. Not saving the page may seem obvious, but it is not an uncommon cause of this problem.
Refresh page
If the page is saved, your Internet browser may be loading the page from its cache instead of from the web server. To reload the web page from the server, refresh the browser, which can often be done by pressing the F5 key on the keyboard.
TipThe location.reload method takes a parameter which is a Boolean. If set as true, the page will be forced to refresh from the server. The default value is false that may refresh the page from the browser cache. As you click the button in the demo page, it will reload the page by using location.reload default value: See online demo and code.
Doing a hard refresh (pressing Ctrl+F5) may also help make sure everything is not loading from a cached version on your computer.
Uploaded again
If you have uploaded the file to a different directory or it was corrupted during the upload, it will not change the page you are refreshing. Try uploading the files again and make sure they are in the right directory.
Clear browser cache
If you continue to encounter issues, try to clear all of the Internet browsers cache (history).
TipRun the browser in incognito mode, so nothing is cached or loaded from cache.
Wait
If you are uploading an update to a page or image, and are not seeing changes, give it a few minutes. Some servers, such as a server on a CDN must replicate the information across multiple servers, which can take time. If you're using a service such as CloudFlare, you may also need to delete the cached version of the web page on their servers through the CloudFlare website.
Delete and re-upload the page
If the above recommendations do not work, try deleting the page on the server. Refresh your browser to get an error about the missing page, upload the page with new changes, and refresh the browser window again.
Other issues
If you continue to experience issues with seeing changes that have been made to an uploaded page, you may require assistance from your network administrator or Internet service provider. For example, if you are network is using a proxy, that page may be cached on that server and not loading the pages with new changes. For additional assistance, we suggest contacting your administrator or service provider.
Additional information
- See the cache and web page definitions for further information and related links.
Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave 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
Comments
commented Feb 18, 2016
Usually, after refreshing a page, the page still stays at the same position prior to the refresh. However, I noticed with MDL, the page would jump back to the top after refresh. Is this intended? |
added this to the V2 milestone Feb 18, 2016
added enhancementLayout labels Feb 18, 2016
commented Feb 18, 2016
This is likely due to the way we're taking care of things inside the Layout component. Since we're scrolling inside of an element rather than on the body, the browser doesn't know how to keep the current position. This would be a BC break for v1.x, but we'll try to address the issue when rewriting layout in v2! |
commented Feb 18, 2016
Understood. Looking forward to V2! |
commented Mar 13, 2016
This breaks anchor navigation. I'm resorting to this terrible hack: |
commented Mar 24, 2016
Solution #1120 (comment) |
commented Mar 31, 2016
I was able to fix this by overriding the div with the mdl-layout class by specifying height: auto in the css. _layout.scss is specifying it as height: 100% which seems to cause the scrolling to top behavior.The scrolling to top on refresh was less of an issue, but the scrolling to top after the mdl js loads seems quite bad, especially if the user has already scrolled down reading the page before the js has finished loading, at which point they are brought abruptly to the top again, quite jarring. |
commented May 3, 2016
Thanks @compressed! I can confirm that your workaround solves the problem of the page jumping to the top after it has been loaded fully. |
commented May 4, 2016
but then the header is not fixed |
commented May 6, 2016
@kybarg Not sure whether to reply on this thread or on #1120 but I'm assuming that solution has not been implemented on the Google Developers website? Neither the hash nor the reload works: https://developers.google.com/web/fundamentals/discovery-and-monetization/social-discovery/?hl=en#use-schemaorg--microdata-to-provide-rich-snippets-on-google I'm definitely looking forward to a fix for this, especially the hash. |
commented Jul 3, 2016
I'm using the mdl-componentupgraded event to have anchor navigation working properly. Page reload still fails.Depends on jQuery, but conversion to pure JS should be straightforward. |
commented Sep 15, 2016
@sgomes - will v2 also address the issue where the page returns to the top when it finishes loading? That is, if you start scrolling before the page has finished loading, it will jump to the top when loading completes. You can see this issue in the demo site - https://getmdl.io/templates/android-dot-com/index.html |
commented Sep 15, 2016
Yes since we aren't dynamically destroying and re-injecting the content. This is all related to the same problem in the V1 code. |
commented Nov 22, 2016 • edited
edited
Thank U viotti. It works for hash, even if I refresh the page I changed your code slightly to make it JQuery free: |
commented Jun 24, 2018
Kind of ironic that one of the official example pages is fixing this exact issue by overwriting mdl styles: https://rework.withgoogle.com/ But it's a good example on how you can fix this issue on your own site. |
commented Jul 8, 2018
Excuse me. Can you tell me where to put the above code in my website? I am new to web development. |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment