Closed brian-rose closed 4 months ago
Here's a partial screenshot of https://cookbooks.projectpythia.org on Safari on MacOS 12.6.1:
and a screenshot of the same page on Chrome:
The badges are created dynamically at site build time using this code
Why does it fail on Chrome but not other browsers? (Firefox is also confirmed to work as expected) @ProjectPythia/infrastructure
The rendered HTML for the HRRR-AWS cookbook Binder badge on the Gallery page here looks like this:
<a class="reference external" href="http://binder.mypythia.org/v2/gh/ProjectPythia/HRRR-AWS-cookbook.git/main"><img alt="Binder" src="http://binder.mypythia.org/badge_logo.svg"/></a>
while the rendered HTML for the same badge on the README page (which looks fine on Chrome) is this:
<a class="reference external" href="http://binder.mypythia.org/v2/gh/ProjectPythia/HRRR-AWS-cookbook.git/main"><img alt="Binder" src="http://binder.mypythia.org/badge_logo.svg" /></a>
Other than a bit of whitespace, they look identical to me. No idea why the first one does not render properly on Chrome.
Bringing up the Developer's Console in Chrome, it is 1) replacing http with https, and then 2) throwing an invalid certificate authority error when it tries to load the svg using that protocol. It's happening on my version of Chrome both for the Gallery and README pages.
More impetus for me to get a new Jetstream2 Binderhub instance up which uses https and has a recognized certificate authority.
This should go away when our new Pythia binder service is up and running!
Update: this problem is mostly resolved since most Cookbooks on the gallery are now linking to the new Pythia binder which uses https.
There are still a couple of Cookbooks on the gallery that are not linking to the new Binder:
There are PRs open in both those repos to get them updated to the latest infrastructure.
As discussed in #103, the new Binder badges with the correct links drawn dynamically from each Cookbook's
_config
file do not display properly in the Chrome browser.