Skip to content
This repository has been archived by the owner on Oct 25, 2023. It is now read-only.

Webogram loads to a white page #278

Closed
turl opened this issue May 10, 2014 · 39 comments
Closed

Webogram loads to a white page #278

turl opened this issue May 10, 2014 · 39 comments

Comments

@turl
Copy link

turl commented May 10, 2014

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?

@ingria
Copy link
Contributor

ingria commented May 10, 2014

Are you using your own build or http://zhukov.github.io/webogram?
I'd had the exact same issue on fx29.

@turl
Copy link
Author

turl commented May 10, 2014

I'm using http://zhukov.github.io/webogram

@t-chab
Copy link

t-chab commented May 10, 2014

Hi,

I have exactly the same problem, using http://zhukov.github.io/webogram on ArchLinux with Firefox 29.0.1

@zhukov
Copy link
Owner

zhukov commented May 10, 2014

Hi,
this is probably a problem with Click-jacking protection:

    if (window.chrome && chrome.app && chrome.app.window || self == top) {
      document.documentElement.style.display = 'block';
    } else {
      top.location = self.location;
    }

After that white screen reproduces again, please open javascript console (Tools - Web - Console). First inspect its contents for errors, then try to enter self == top. If the result is false, enter window == window.top, self and top separately and share screenshot here.
If the result was true, try to execute document.documentElement.style.display = 'block'. The page must become visible.

@edmundoa
Copy link

Hi,
I'm also having this issue on Firefox 29.0.1 in OS X 10.9. Executing document.documentElement.style.display = 'block' in the javascript console fixed the problem for me.

@zhukov
Copy link
Owner

zhukov commented May 10, 2014

@edmundoa and what about other commands? That gives me almost no info.

@edmundoa
Copy link

Oh, sorry, I forgot about them with the excitement of seeing my messages again :)

< self == top
> true
< window == window.top
> true
< self
> Window → http://zhukov.github.io/webogram
< top
> Window → http://zhukov.github.io/webogram

Please let me know if you need any more information!

@zhukov
Copy link
Owner

zhukov commented May 10, 2014

Try to refresh the page and check if any errors are present in console.

@edmundoa
Copy link

I only see a few warnings regarding JS, but anyway here's a screenshot:
web-console-output

@t-chab
Copy link

t-chab commented May 10, 2014

Here's my screenshot :

webogram

With

document.documentElement.style.display = 'block' 

the page appears.

@zhukov
Copy link
Owner

zhukov commented May 10, 2014

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.

@t-chab
Copy link

t-chab commented May 10, 2014

webogram

@zhukov
Copy link
Owner

zhukov commented May 10, 2014

Hm... it seems like it is an outdated version of Webogram. Try to execute applicationCache.update() in console and wait for minute, then reload a page. If that doesn't help, try to reset browser cache.

@t-chab
Copy link

t-chab commented May 10, 2014

Thanks, after clearing browser cache and restarting Firefox, everything is ok.

@edmundoa
Copy link

In my case, I already cleared the cache and restarted the browser before doing anything else. Either way, running applicationCache.update() made the trick for me.
Thank you for the support! 👍

@turl
Copy link
Author

turl commented May 10, 2014

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 😄

@DissCent
Copy link

I also have this problem. I tried the following things:
-cleared all cache
-restarted firefox
-executed applicationCache.update() which leads to "undefined" in the console

System: openSUSE Linux 13.1 x64, Firefox 28.0
Screenshot:

netgames1

@pahnin
Copy link

pahnin commented May 11, 2014

webogram error
I think some asserts are not loaded, because of cross origin request blocked! Using firefox 29.0 on ubuntu
tried clearing cache etc, didn't work applicationCache.update() didn't work either

@1nv1
Copy link

1nv1 commented May 12, 2014

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!
Regards.

[Update: This solution worked in two machines more.]

@Catecs
Copy link

Catecs commented May 12, 2014

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

@DissCent
Copy link

Thank you @1nv1 - that works perfectly!

@1nv1
Copy link

1nv1 commented May 12, 2014

One question @WindohsCrasher , What platform you run Firefox? Is for get a new clue about the problem.
Regards!

@DissCent
Copy link

@1nv1 I run it on openSUSE Linux 13.1 x64, Firefox 28.0. Hope that helps :)

@1nv1
Copy link

1nv1 commented May 12, 2014

Thanks @WindohsCrasher. I hope so...

@AlexBurdu
Copy link

I had the same problem with Firefox 29 on Ubuntu 14.04 x64.
@1nv1's solution seems to fix it.

Thanks!

@zhukov
Copy link
Owner

zhukov commented May 12, 2014

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 document.documentElement.style.display = 'block' is not executed in app.js.

@Falc
Copy link

Falc commented May 12, 2014

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.

@asdofindia
Copy link
Contributor

I had 5.1 MB of offline data just before I cleared (if that helps)
Ubuntu 14.04 Firefox 29
On May 13, 2014 1:21 AM, "Aitor García" notifications@github.com wrote:

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.


Reply to this email directly or view it on GitHubhttps://github.com//issues/278#issuecomment-42879453
.

@alokmahor
Copy link

for me also clearing offline data makes webogram working properly

@nappa85
Copy link

nappa85 commented May 13, 2014

Same problem here, Firefox 29.0.1 on Windows 7, solved clearing offline data.

@tentator
Copy link

Same here, FFx 29.0.1 on Win7 and solved thanks to offline data cleaning like suggested by 1nv1, Thanks!

tent:wq

@nukeador
Copy link
Contributor

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?

@zhukov
Copy link
Owner

zhukov commented May 14, 2014

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).

@zhukov
Copy link
Owner

zhukov commented May 14, 2014

@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 zhukov closed this as completed May 14, 2014
@nukeador
Copy link
Contributor

@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

https://developer.mozilla.org/en-US/docs/HTML/Using_the_application_cache#Example_1.3A_a_simple_cache_manifest_file

Also maybe the name should be webogram.appcache or similar, because app.manifest could be used for other stuff not related with cache.

@zhukov
Copy link
Owner

zhukov commented May 14, 2014

@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 * in CACHE section.

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.

@zhukov
Copy link
Owner

zhukov commented May 14, 2014

@nukeador I will try to rename this file to *.appcache, but I'm not sure, if this can cause any problems.

@Ryuno-Ki
Copy link
Contributor

@eBug Could you repost the content wrapped inside like so?

```
TypeError … }
```

This way, formatting is preserved and it's easier to read.
Thank you in advance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests