rhysd / Mstdn

Tiny web-based mastodon client for your desktop
MIT License
389 stars 15 forks source link

Local or federated timeline is not loaded after startup #30

Open osapon opened 7 years ago

osapon commented 7 years ago

Immediately after startup, the home TL is displayed, but the part where local or federation is displayed is not read. React progress bar at the top of the screen stops without stretching to the end.

In this state, move once to the setting screen, return again, and click on local or federation will make it display well. this state, when switching to local or federation view by custom CSS without switching to the setting screen, it will be displayed, but it may become unresponsive after the subsequent image preview etc. It seems to occur on instances of version 1.4 and higher.

rhysd commented 7 years ago

Thank you for reporting this.

I'm not facing this issue currently on macOS on https://mstdn.jp (Mastodon v1.4.3). It may be platform specific issue.

React progress bar at the top of the screen stops without stretching to the end.

Can you provide a screenshot for this?

And could you please try How to Debug section? It launches DevTools. If there is any error, it may be reported in 'console' tab of DevTools.

osapon commented 7 years ago

https://gyazo.com/223c01582ef2fa4a5e2a384582f49c62 (movie 30s) It seems that reading of the screen does not complete after starting. It switches when switching to the setting screen and operates.

https://gyazo.com/f83b16afa8dd80760ead270e4f9bf195 (movie 30s) After launching, I click the image then it will not open. When I press the federation changeover button twice, the image is displayed at the same time the federation is displayed, but it can not be closed.

https://gyazo.com/2fdc75a3519a9655bf5f28bfc0acd99d (movie 60s) After starting up, pressing the federation switching button twice while reading is not completed switches it. Even if you click on the image, it will not open immediately, and if you press the federation or local switch button, the image will come out. Image switching will work. This also can not close the image too.

https://gyazo.com/4573c7ea41b37e19141ea2f5262a8d2d It is the result of debug mode. A warning was output to the console.

https://gyazo.com/2d0b9f9f76157b437f61569d5d16ff87 Network manifest.js were not loaded by CSP.

rhysd commented 7 years ago

Thank you for helpful videos.

From the console output, the first error looks not related to this issue. The error was emitted by React runtime because of minified HTML with development environment (it seems that setting NODE_ENV to development enables React's debugging features).

From the screenshot of performance monitor, the 'blocked:csp' may be the root cause of this issue. The content looks to be blocked by CSP (Content Security Policy). CSP is checked when sandbox is enabled. So it's related to config, I think.

Could you paste your config.json with hiding your personal account information?

rhysd commented 7 years ago

I think I can try with your config.

osapon commented 7 years ago

My config.json I am setting the sandbox to false to use User CSS.

{
  "hot_key": "CmdOrCtrl+Shift+S",
  "icon_color": "black",
  "always_on_top": false,
  "normal_window": true,
  "zoom_factor": 0.7,
  "hide_menu": false,
  "chromium_sandbox" : false,
  "accounts": [
    {
      "name": "温泉",
      "host": "m6n.onsen.tech",
      "default_page": "/web/timelines/home"
    }
  ],
  "keymaps": {
    "a": "/about",
    "j": "scroll-down",
    "k": "scroll-up",
    "i": "scroll-top",
    "m": "scroll-bottom"
  }
}
osapon commented 7 years ago

This issue may have been caused by remodeling the instance. Problems could not be reproduced in instances that were not remodeled.