We’re running a graphics community, and members often post (very) high res images. Currently, when you click on an image it will enlarge it, loading the original image but scaled to the viewport. Clicking the enlarged image will take you to the next image in the post, and users have to “right click → view image in new tab” to see it at full, original size (or download the image).
Is there a way to either change this behavior so that clicking an enlarged image will open it at full-size? Alternatively (and perhaps nicer), is it feasible to create a theme component that adds a “view full size” option below the enlarged image?
I never understood the difference between this and the download link, aren’t they the same thing? We have an existing discussion on this here on meta already..
You may not want to actually have the file in your downloads folder just to take a quick look at something. Also, it requires at least one additional click to download and then view. ArtStation has an elegant solution for this (example link), and I use it all the time:
I think in most browsers the download icon just opens the raw image URL in a new browser tab and it’s not saved anywhere (outside of your cache) unless you right click… so I guess the labeling might be a bit misleading?
Hmm maybe I’m missing something, but for me, it always actually downloads the file. Is it a configuration thing? Opening image files in a new tab would be
Wow, it does here, but not on my site (example link). I checked in safe mode and it still downloads there, suggesting some site setting. I’ll dig in, if you have any ideas I’d love to hear.
And yes, is opening the file in a new tab is the expected behavior then ‘download’ might not be an accurate label.
Ah I see, so your site isn’t directly linking the image with the extension, the URL is https://blenderartists.org/uploads/default/0dea5b078999bf99ae583dfc353e31dde79bf764
It has the same behavior in safe mode with all themes/plugins disabled… so it must be a difference in the image handling configuration
The difference is in expected behavior. At least to me, “Download” implies saving an asset and is something I reserve for some kind of later usage or project, whereas something like “View Full” implies a quick means to do just that.
They’re different enough that equating them can apparently cause confusion.
It would be ideal to offer both behaviors for a given image, like the ArtStation example. There’s no ambiguity there.
Hmm, I did some digging (warning: I’m a Ruby noob) and from what I see the download URL is taken from the data-download-href on the image. It seems to be defined here:
But this attribute only contains the ‘upload.sha1’, and no file extension. The image a href’s in this topic don’t contain the data-download-href attribute, I wonder if this is because the image I just shared above is too small to be resized and didn’t trigger a rebake. I’ll upload a larger one below for testing (CC0 licensed):
Maybe it’s because BlenderArtists doesn’t use a CDN (!?) so they get the content-disposition from our service that tell the browser to download it, and the Meta CDN is stripping it?
We use Cloudflare for images only. I just checked on another Discourse server (one that I know does not use a CDN), and see the same download behavior there - example link.
Estou ciente das vantagens — especialmente se você usar uma com endpoints próximos aos seus usuários. Até agora, o cache do Cloudflare tem funcionado bem para nós (é razoavelmente rápido e alivia nosso servidor do serviço de imagens) e ainda estamos com um orçamento muito apertado.
Não deveria haver um comportamento diferente para “download” de imagem quando o CDN está ativado em comparação com quando está desativado. @pmusaraj, você dedicou bastante tempo a essa área; há algum motivo para não haver um cabeçalho Content-Disposition especial aqui (onde temos um CDN S3 definido), enquanto ele está definido para instalações locais?
@codinghorror Acredito que o termo que estamos usando aqui, junto com o ícone, está meio errado. Basta dizer original e eliminar toda essa questão de “disposição” para download. Você simplesmente clica nele e, incondicionalmente, é levado à URL onde a imagem está localizada. Isso também simplifica a implementação do CDN como um bônus adicional.
OK, então precisamos repassar a disposição para o AWS CDN aqui @pmusaraj. Acho que o aplicativo precisará atuar como front-end para o download. (também confirme que funciona com CDN normal)
Em relação ao tópico original, acho que, se você quiser um link de tamanho completo na sua lightbox @bartv, será necessário um componente de tema.
Não vejo realmente nenhum problema aqui com comportamentos diferentes, também. O CDN pode ter o comportamento de download mais sofisticado e o não-CDN pode ter o comportamento mais simples.
