After codeberg.org migrations. My Firefox can't show images in this site. I think the image location is not considered secure by Firefox. Works well in Chromium
Image not shown in Firefox #350
What certificate warnings are these? Do you have any critical warnings in the browser console?
Works for me in Firefox. Weird.
@azzamsa pleace clean your browser cache!
Could it make sense to mark all content served by gitea with Etag: <some_version>? There is also another related issue open (https://github.com/go-gitea/gitea/issues/13499), the approach we implemented for Codeberg pages linked therein.
What certificate warnings are these? Do you have any critical warnings in the browser console?
it says the images crom from unstrusted sources.
now the warnings gone. But the images still not shown.
@azzamsa pleace clean your browser cache!
I've tried using Firefox private window. The issue still persists.
I've also deleted the cookies and site data of this site.
Works for me in Firefox. Weird.
I am on Firefox Developer Edition 84.0b3.
Okay maybe it's on my end. I will try look around more.
I've tried with restart with add-on disabled but no luck.
I checked the browser console and I has some errors
The problem solved if I untick this:
but, indeed other pages can't use its own font.
complete error message:
downloadable font: no supported glyph data table(s) present (font-family: "Noto Color Emoji" style:normal weight:400 stretch:100 src index:2) source: https://codeberg.org/fonts/NotoColorEmoji.ttf
downloadable font: rejected by sanitizer (font-family: "Noto Color Emoji" style:normal weight:400 stretch:100 src index:2) source: https://codeberg.org/fonts/NotoColorEmoji.ttf
4 simplemde.min.js:14:15191
Object { name: "heading-1", action: g(e)
, className: "fa fa-header fa-header-x fa-header-1", title: "Big Heading" }
simplemde.min.js:14:15284
5 simplemde.min.js:14:15191
Object { name: "heading-2", action: v(e)
, className: "fa fa-header fa-header-x fa-header-2", title: "Medium Heading" }
simplemde.min.js:14:15284
6 simplemde.min.js:14:15191
Object { name: "heading-3", action: y(e)
, className: "fa fa-header fa-header-x fa-header-3", title: "Small Heading" }
simplemde.min.js:14:15284
7 simplemde.min.js:14:15191
Object { name: "heading-bigger", action: m(e)
, className: "fa fa-header fa-header-x fa-header-bigger", title: "Bigger Heading" }
simplemde.min.js:14:15284
8 simplemde.min.js:14:15191
Object { name: "heading-smaller", action: p(e)
, className: "fa fa-header fa-header-x fa-header-smaller", title: "Smaller Heading" }
simplemde.min.js:14:15284
9 simplemde.min.js:14:15191
10 simplemde.min.js:14:15191
Object { name: "code", action: h(e), className: "fa fa-code", title: "Code" }
Thanks deployed that yesterday
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?