mcwumbly
(Dave McClure)
11월 5, 2017, 1:28오후
1
I find this behavior surprising:
I post a link to an image on it’s own line, like the one below from the article .
It shows up in the preview fine
I create the post
It shows up fine in my post for a while.
Later, it gets replaced with a thumbnail saying: “This image is too large to display; click here to view”
Onebox link:
View insights, event recaps, and how teams transform work with visual collaboration. Read articles on remote work, facilitation, design thinking, and more.
Preview screenshot:
After post screenshot:
After image is replaced screenshot:
TODO
mcwumbly
(Dave McClure)
11월 5, 2017, 1:59오후
2
Looks like the problem isn’t happening here. Maybe it’s a site setting I need to adjust to work around this issue?
dax
(Daniela)
11월 5, 2017, 2:28오후
3
2개의 좋아요
mcwumbly
(Dave McClure)
11월 5, 2017, 2:47오후
4
Currently it’s 4MB (4096 KB). Looks like that image is 35 MB.
What have others set that to nowadays?
This is in @vinothkannans list of things to improve. The behavior is correct but the UI could use some work.
3개의 좋아요
mcwumbly
(Dave McClure)
11월 5, 2017, 9:23오후
6
If there were anyway to make it clear this would happen in the preview , that would make it a lot less surprising.
Also, it wasn’t clear to me what “too large” meant, as there are site settings both for file size and for dimensions. I wasn’t sure which setting would need adjusting with the current language.
2개의 좋아요
PR created. The new UI won’t create confusions.
4개의 좋아요
The issue is that we’re doing some magic server-side to automatically downsize big images which we can’t really do client-side.
I agree. One setting is only used to create thumbnails, the other is to prevent mobile users from wasting their bandwidth downloading a gigabyte GIF.
2개의 좋아요
mcwumbly
(Dave McClure)
11월 6, 2017, 3:50오후
9
Cool, thanks. What happens in the new UI?
1개의 좋아요
As you can see it will have some explanation.
5개의 좋아요