-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Webogram loads to a white page #278
Comments
Are you using your own build or http://zhukov.github.io/webogram? |
I'm using http://zhukov.github.io/webogram |
Hi, I have exactly the same problem, using http://zhukov.github.io/webogram on ArchLinux with Firefox 29.0.1 |
Hi,
After that white screen reproduces again, please open javascript console (Tools - Web - Console). First inspect its contents for errors, then try to enter |
Hi, |
@edmundoa and what about other commands? That gives me almost no info. |
Oh, sorry, I forgot about them with the excitement of seeing my messages again :)
Please let me know if you need any more information! |
Try to refresh the page and check if any errors are present in console. |
I need the screenshot of very beginning of console. So please scroll it to the top and make another one. BTW I can't reproduce it on OS X 10.9.2 + Firefox 29.0.1. It's strange. |
Hm... it seems like it is an outdated version of Webogram. Try to execute |
Thanks, after clearing browser cache and restarting Firefox, everything is ok. |
In my case, I already cleared the cache and restarted the browser before doing anything else. Either way, running |
applicationCache.update() didn't work for me, but I went to the Firefox preferences and cleared offline data for Webogram and it started working again 😄 |
Hi, temporary solution. In firefox 29.0 (running on GNU/Linux Fedora 20) go to Preferences -> Advanced -> Offline Wev Content and User Data. Select "zhukov.github.io" from the list and click on remove... Voila! [Update: This solution worked in two machines more.] |
Hi, have same problem, white page on link http://zhukov.github.io/webogram/#/ on Firefox 29 (windows 7) on console everything is white and empty too, tried to clear cache or reload nothing change, for now i'm tried temp solution by 1nv1 (thank a lot!) and it works...for now, hope it resolve but don't know how to do it |
Thank you @1nv1 - that works perfectly! |
One question @WindohsCrasher , What platform you run Firefox? Is for get a new clue about the problem. |
@1nv1 I run it on openSUSE Linux 13.1 x64, Firefox 28.0. Hope that helps :) |
Thanks @WindohsCrasher. I hope so... |
I had the same problem with Firefox 29 on Ubuntu 14.04 x64. Thanks! |
I have no idea about the problem. I can't reproduce by myself. I tried to fix it in latest update, but that was just a guess. Would be great if with the problem someone could debug it. You can start by learning, why code |
I had "zhukov.github.io" as an exception in "Advanced > Preferences > Network > Offline Web Content and User Data", so I removed it from the list, refreshed Webogram and it is working again. |
I had 5.1 MB of offline data just before I cleared (if that helps)
|
for me also clearing offline data makes webogram working properly |
Same problem here, Firefox 29.0.1 on Windows 7, solved clearing offline data. |
Same here, FFx 29.0.1 on Win7 and solved thanks to offline data cleaning like suggested by 1nv1, Thanks! tent:wq |
This a concurrent problem, from time to time when webogram updates I have to clean cache, but I guess regular users don't have a clue about what's going on. Is the cache.manifest number increasing accordingly when changes on the js/css files are made? |
I've found a PC with this problem. It seems like Firefox has partly updated application cache - the index.html page is up to date, while app.js is cached one from previous revision. In this case the app is not going to work properly and autoupdate to actual version. The only way out is to clear the cache manually as described in previous comment #278 (comment). |
@nukeador sure, manifest is updated with every deploy, you can see the actual version here: https://github.com/zhukov/webogram/blob/gh-pages/app.manifest. So in my case index.html is from this commit: https://github.com/zhukov/webogram/blob/4af727000857999fa1599c931ce0bc2522758afa/index.html, and app.js is loaded from https://github.com/zhukov/webogram/blob/dcb407309b2c77697e18c042f250b6b5f1345d4d/js/app.js, which is definitely not actual version. I am pretty sure, that this situation is not expected by any of app developers. The application cache must either be updated completely or not updated at all. I assume, that GitHub Pages have no problems with source and manifest headers, while this works perfectly fine in Google Chrome and Safari. |
@zhukov I see the cache manifest file is caching everything (*) and that's a problem because it's also caching itself, so the browser is unable to check the changes: https://github.com/zhukov/webogram/blob/master/app/app.manifest Also maybe the name should be webogram.appcache or similar, because app.manifest could be used for other stuff not related with cache. |
@nukeador no, this is a link for test manifest, which is active only for local development. The production one (which is hosted here http://zhukov.github.io/webogram/app.manifest) is generated with Gulp. Its actual contents: https://github.com/zhukov/webogram/blob/gh-pages/app.manifest. There is no manifest in the list of cache targets and no Also, the asterisk in https://github.com/zhukov/webogram/blob/master/app/app.manifest is under NETWORK section, which means that every resource should be downloaded from network and application cache should be ignored for every file except index.html. But again, this is actual for test environment only. |
@nukeador I will try to rename this file to *.appcache, but I'm not sure, if this can cause any problems. |
@eBug Could you repost the content wrapped inside like so? ``` TypeError … } ``` This way, formatting is preserved and it's easier to read. |
Webogram currently loads to a white page on Firefox 29.0.1 on Arch Linux. I've tracked this down to the html element being set to display: none; on the CSS. Using the Stylish addon with a custom style to inject "html { display: block !important; }" makes it work again.
Maybe this is related to some code move from 2d50db4?
The text was updated successfully, but these errors were encountered: