Bug: Quotes didn't show up properly #645

Closed
opened 1 month ago by HexagonCDN · 11 comments

nobody/LocalCDN#1042
Hello. On that issue, my quotes don't display. Can you check why and fix it please?

https://codeberg.org/nobody/LocalCDN/issues/1042 Hello. On that issue, my quotes don't display. Can you check why and fix it please?
Collaborator

To which quote and message are you referring to? Also what's your expected outcome with that message?

To which quote and message are you referring to? Also what's your expected outcome with that message?
Poster

3.1. Enable logging
Enable logging

3.2. Get logging informations
Open "Browser Console" with CTRL + SHIFT + J or the menu

Get logging informations Get logging informations

3.3. Enable "Show Content Messages" and use the filter
Enable "Show Content Messages" and use the filter Enable "Show Content Messages" and use the filter

This may need updates for latest version as the logging feature changed.

HTML filter
The HTML filter uses the JavaScript API webRequest.filterResponseData. This API is not supported by Chromium. It was proposed already in 2015, 5 years ago. I don't think this will ever work under Chromium.
Chromium Bugreport | Issue 487422: WebRequest API: allow extensions to read response body

HTML filter may be possible now!
https://bugs.chromium.org/p/chromium/issues/detail?id=487422
image

Originally posted by @HexagonCDN in nobody/LocalCDN#1042

1. > 3.1. Enable logging > Enable logging > > 3.2. Get logging informations > Open "Browser Console" with CTRL + SHIFT + J or the menu > > Get logging informations Get logging informations > > 3.3. Enable "Show Content Messages" and use the filter > `Enable "Show Content Messages" and use the filter Enable "Show Content Messages" and use the filter` This may need updates for latest version as the logging feature changed. 2. > HTML filter > The HTML filter uses the JavaScript API `webRequest.filterResponseData.` This API is not supported by Chromium. It was proposed already in 2015, 5 years ago. I don't think this will ever work under Chromium. > Chromium Bugreport | Issue 487422: WebRequest API: allow extensions to read response body HTML filter may be possible now! https://bugs.chromium.org/p/chromium/issues/detail?id=487422 ![image](/attachments/492170fe-683d-4019-b782-32d81b6c08b8) _Originally posted by @HexagonCDN in https://codeberg.org/nobody/LocalCDN/issues/1042#issue-152909_
Poster
1.  
> 3.1. Enable logging
> Enable logging 
> 
> 3.2. Get logging informations
> Open "Browser Console" with CTRL + SHIFT + J or the menu
> 
> Get logging informations  Get logging informations 
> 
> 3.3. Enable "Show Content Messages" and use the filter
> `Enable "Show Content Messages" and use the filter  Enable "Show Content Messages" and use the filter` 

This may need updates for latest version as the logging feature changed.

2. 
> HTML filter
> The HTML filter uses the JavaScript API `webRequest.filterResponseData.` This API is not supported by Chromium. It was proposed already in 2015, 5 years ago. I don't think this will ever work under Chromium.
> Chromium Bugreport | Issue 487422: WebRequest API: allow extensions to read response body
``` 1. > 3.1. Enable logging > Enable logging > > 3.2. Get logging informations > Open "Browser Console" with CTRL + SHIFT + J or the menu > > Get logging informations Get logging informations > > 3.3. Enable "Show Content Messages" and use the filter > `Enable "Show Content Messages" and use the filter Enable "Show Content Messages" and use the filter` This may need updates for latest version as the logging feature changed. 2. > HTML filter > The HTML filter uses the JavaScript API `webRequest.filterResponseData.` This API is not supported by Chromium. It was proposed already in 2015, 5 years ago. I don't think this will ever work under Chromium. > Chromium Bugreport | Issue 487422: WebRequest API: allow extensions to read response body ```
Poster

This is my expected outcome.

> This is my expected outcome.
Collaborator

Thank you for your comments, this is a bug with the markdown library that Gitea uses. I've opened a bug for it: https://github.com/yuin/goldmark/issues/313.

Thank you for your comments, this is a bug with the markdown library that Gitea uses. I've opened a bug for it: https://github.com/yuin/goldmark/issues/313.
Collaborator

For now you can put a extra new line(between the task list item and the quote) in order to have it correctly rendered.

For now you can put a extra new line(between the task list item and the quote) in order to have it correctly rendered.
Gusted added the
gitea-related
upstream
labels 1 month ago
Collaborator

Upstream PR was merged.

[Upstream PR](https://github.com/go-gitea/gitea/pull/20300) was merged.
6543 referenced this issue from a commit 1 month ago
Poster

Can we close the issue now?

Can we close the issue now?
Collaborator

It's closed when Codeberg updates to Gitea v1.17 which includes this fix.

It's closed when Codeberg updates to Gitea v1.17 which includes this fix.
Poster

How can I know when is Codeberg updated? Thank you.

How can I know when is Codeberg updated? Thank you.
Collaborator

When this or the main issue gets closed.

When this or the [main issue](https://codeberg.org/Codeberg/Community/issues/579) gets closed.
6543 closed this issue 3 days ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Codeberg/Community#645
Loading…
There is no content yet.