Market page will not display in Safari on mac OS

[ewbjan]

Followed the setup guide instructions all the way to paying the 1 dcr fee. Market page shows progress indicator and never updates to show buy and sell orders. Also wallet page options do not work in Safari (all links are greyed out).

[chappjc]

Will test on Epiphany as the closest browser I have access to, but we do have some MacOS users. It sounds a bit like there might be a problem with the location of the "site" folder though. Three questions:

1. how did you install? from one of the supplied archives or manually built from the git repository?
2. when dexc starts, what does it say in the logs regarding the location of the "site" folder?
3. In Safari, can you look for error messages in the browser console? https://appuals.com/open-browser-console/

[ewbjan]

Installed from the latest archive (downloaded, changed to executable and then ran it from command line). Tried both versions 0.1.0 and 0.1.1 of dexc. after desc starts, it shows: Looking for site in /Users/[username]/decred/site 2020-11-17 20:36:50.924 [INF] WEB: Located "site" folder at /Users/[username]/decred/site Safari console shows the below errors: Refused to connect to ws://127.0.0.1:5758/ws because it does not appear in the connect-src directive of the Content Security Policy. Unhandled Promise Rejection: SecurityError: The operation is insecure. followed by (screenshot of additional info) [image: Screen Shot 2020-11-17 at 2.33.01 PM.png]

…

On Tue, Nov 17, 2020 at 2:09 PM Jonathan Chappelow ***@***.***> wrote: Will test on Epiphany as the closest browser I have access to, but we do have some MacOS users. It sounds a bit like there might be a problem with the location of the "site" folder though. Three questions: 1. how did you install? from one of the supplied archives or manually built from the git repository? 2. when dexc starts, what does it say in the logs regarding the location of the "site" folder? 3. In Safari, can you look for error messages in the browser console? https://appuals.com/open-browser-console/ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#839 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE2YWR44FOLAYN5XYKK4N6TSQLJ6RANCNFSM4TZBDW6Q> .

[chappjc]

Is the browser opened to "http://127.0.0.1:5758/"? The Content Security Policy error saying that "ws://127.0.0.1:5758/ws" is not allowed by the connect-src directive indicates that it somehow differs from how the brower is addressing the page.

The screenshot didn't seem to make it in the comment.

[chappjc]

OK, I've reproduced in Epiphany.

Thanks for the report. We'll get this fixed right away.

Refs:

• https://bugs.webkit.org/show_bug.cgi?id=201591
• CSP: connect-src 'self' and websockets w3c/webappsec-csp#7

does seem to be a bug in safari/epiphany/webkit

• https://wpt.fyi/results/content-security-policy/connect-src/connect-src-websocket-self.sub.html?label=experimental&label=master&aligned
• http://wpt.live/content-security-policy/connect-src/connect-src-websocket-self.sub.html

We will search for a workaround

[chappjc]

Resolved in PR #840.

Unfortunately, I don't see a way for the user to workaround the issue with Safari setting, so this will need to land in the next patch release.