Codeberg/Community
54
325
Fork
You've already forked Community
12

Image not shown in Firefox #350

Closed
opened 2020年12月03日 10:28:55 +01:00 by azzamsa · 10 comments

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

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](/attachments/73e05f9a-1532-4074-82cf-07f84c39739c)
111 KiB
Member
Copy link

What certificate warnings are these? Do you have any critical warnings in the browser console?

What certificate warnings are these? Do you have any critical warnings in the browser console?

Works for me in Firefox. Weird.

Works for me in Firefox. Weird.

@azzamsa pleace clean your browser cache!

@azzamsa pleace clean your browser cache!
Member
Copy link

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.

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.
Author
Copy link

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.

> 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.
Author
Copy link

I've tried with restart with add-on disabled but no luck.

I checked the browser console and I has some errors

image

image

I've tried with `restart with add-on disabled` but no luck. I checked the browser console and I has some errors ![image](/attachments/5d415935-da87-4a8b-9539-34ee093b0216) ![image](/attachments/29b934d6-d1cb-40d0-87ae-9e2afbcc290c)
Author
Copy link

The problem solved if I untick this:

image

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" }
The problem solved if I untick this: ![image](/attachments/69ad2622-6b70-481c-acc4-7130a2399c10) but, indeed other pages can't use its own font. - [related issue](https://support.mozilla.org/en-US/questions/913498) complete error message: ```js 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" } ```
related https://github.com/go-gitea/gitea/pull/13837 ?
Author
Copy link

The issue vanishes.

Thanks.

related: #352

The issue vanishes. Thanks. related: https://codeberg.org/Codeberg/Community/issues/352

@6543

Thanks deployed that yesterday

@6543 Thanks deployed that yesterday
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

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.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

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.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#350
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

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?