Slow scrolling wth large images #1195

New Issue

Open

opened 2022-08-28 06:42:52 +00:00 by qwerty287 · 5 comments

qwerty287 commented

2022-08-28 06:42:52 +00:00

Contributor

E.g. in Gitnex readme, see attached video.

VID-1661668876649.mp4

1.5 MiB

qwerty287 added the

🐛 Bug

💻 UI/UX

labels 2022-08-28 06:42:52 +00:00

foxy commented

2023-12-14 19:12:22 +00:00

I see no readme pictures at all lol. Just their alt text

mmarif commented

2023-12-15 07:42:40 +00:00

Owner

@foxy, can you share a repository link?

There are two things to note:
1- Currently svg are not supported.
2- Check the path to images, it should be a full path.

@foxy, can you share a repository link? There are two things to note: 1- Currently svg are not supported. 2- Check the path to images, it should be a full path.

foxy commented

2023-12-15 09:18:12 +00:00

https://codeberg.org/foxy/.dotfiles

Then I believe 2 could be the problem here. Why are full paths not supported?

https://codeberg.org/foxy/.dotfiles Then I believe 2 could be the problem here. Why are full paths not supported?

mmarif commented

2023-12-15 13:17:41 +00:00

Owner

https://codeberg.org/foxy/.dotfiles

Then I believe 2 could be the problem here. Why are full paths not supported?

Full path is supported only. The files are on the server not on the phone or app, so it needs full path to load them.

So instead of this:
![Screenshot #0](.screenshots/0.png)
Should be:
![Screenshot #0](https://codeberg.org/foxy/.dotfiles/raw/branch/main/.screenshots/0.png)

Note the raw in the URL.

> https://codeberg.org/foxy/.dotfiles > > Then I believe 2 could be the problem here. Why are full paths not supported? Full path is supported only. The files are on the server not on the phone or app, so it needs full path to load them. So instead of this: `![Screenshot #0](.screenshots/0.png)` Should be: `![Screenshot #0](https://codeberg.org/foxy/.dotfiles/raw/branch/main/.screenshots/0.png)` Note the `raw` in the URL.

foxy commented

2023-12-15 15:08:01 +00:00

Sorry I meant "why are only full paths supported" lol.

Other mobile clients for git hosting services figure out how to expand relative urls into proper absolute urls (adding raw too). Wouldn't this be the ideal behavior?

Sorry I meant "why are only full paths supported" lol. Other mobile clients for git hosting services figure out how to expand relative urls into proper absolute urls (adding raw too). Wouldn't this be the ideal behavior?