-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Website broken #1513
Comments
yes, this is a known issue (CC @detonin ) |
@rouault Ooops, I accidentally pressed send before entering the actual description, sorry for that! In short the problem seems to be that the template refers to various non-secure resources (CSS, but also images), which by default get blocked by most browsers. Un-blocking results in correct rendering. I can provide more details but if this is a known issue that's probably not necessary. |
Hi Johan, many thanks for your input ! Well, the issue is known in the sense that I noticed that the jekyll template I used by then is not correctly rendered by github anymore (it's not rendered at all actually). I was thinking of replacing completely the template by another one but if you think of sth easier to do to fix it, I would be more than happy to implement it :). |
ping @bitsgalore (no rush btw: this is just in case you do not receive notification without explicit tagging) |
@detonin I'll try to have a look, hopefully next week. |
Fixed this and took the opportunity to switch to Github Actions (as the legacy builder will be deprecated soon. |
Expected behavior and actual behavior.
...to fill...
Steps to reproduce the problem.
...to fill...
Operating system
...to fill...
openjpeg version
...to fill...
The text was updated successfully, but these errors were encountered: