🐛 [Bug] No cookies - no page

[ulfgebhardt]

🐛 Bugreport

If you have cookies on localhost (or any other domain running the wallet) disabled, the page stays empty. The user is left without a hint what to do to fix it.

We should advice the user in this case to enable cookies and that our page is (for now) without function for him if he does not do so.

To reproduce:

1. Navigate to http://localhost/vue
2. Delete LocalStorage
3. Forbid cookies on localhost
4. (shift) Reload Page

Workaround:

Enable cookies

Related:

With an empty storage there is several error appearing on the console:

vue.runtime.esm.js?2b0e:619 [Vue warn]: Error in render: "TypeError: Cannot read properties of null (reading 'name')"

found in

---> <Login> at src/views/Pages/Login.vue
       <AuthLayoutGDD> at src/views/Layout/AuthLayout_gdd.vue
         <App> at src/App.vue
           <Root>

vue.runtime.esm.js?2b0e:1888 TypeError: Cannot read properties of null (reading 'name')
    at Proxy.render (Login.vue?d29d:79)
    at VueComponent.Vue._render (vue.runtime.esm.js?2b0e:3548)
    at VueComponent.updateComponent (vue.runtime.esm.js?2b0e:4066)
    at Watcher.get (vue.runtime.esm.js?2b0e:4479)
    at new Watcher (vue.runtime.esm.js?2b0e:4468)
    at mountComponent (vue.runtime.esm.js?2b0e:4073)
    at VueComponent.Vue.$mount (vue.runtime.esm.js?2b0e:8415)
    at init (vue.runtime.esm.js?2b0e:3118)
    at merged (vue.runtime.esm.js?2b0e:3301)
    at createComponent (vue.runtime.esm.js?2b0e:5978)

Furthermore:

• Remove reference from Readme.md

[ulfgebhardt]

This is still an issue since without cookies you are redirected to another domain and you cannot use the browsers feature to allow cookies from the blocked domain