aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs
diff options
context:
space:
mode:
authorsmcv <smcv@web>2016-12-19 12:46:22 -0400
committeradmin <admin@branchable.com>2016-12-19 12:46:22 -0400
commit8395e430991b30ac96d6f3952fd8eda37ad2b434 (patch)
tree856feb8d84ba16c2a9647c3550893e09d4c3e50b /doc/bugs
parent7d35dc88f3825512d5553ee8378084ed93391db5 (diff)
downloadikiwiki-8395e430991b30ac96d6f3952fd8eda37ad2b434.tar
ikiwiki-8395e430991b30ac96d6f3952fd8eda37ad2b434.tar.gz
Not possible as stated, but could be adapted into a valid feature request
Diffstat (limited to 'doc/bugs')
-rw-r--r--doc/bugs/img_tag_should_support_relative_size.mdwn28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/bugs/img_tag_should_support_relative_size.mdwn b/doc/bugs/img_tag_should_support_relative_size.mdwn
index a625487c4..b6966e056 100644
--- a/doc/bugs/img_tag_should_support_relative_size.mdwn
+++ b/doc/bugs/img_tag_should_support_relative_size.mdwn
@@ -1 +1,29 @@
The size parameter should accept relative values, like "100%". When including large images, I would like it to be scaled relative to the available space.
+
+> 100% of what?
+>
+> The purpose of `[[!img]]` is to scale large images, for example photos, down
+> to a more web-suitable size. When ikiwiki rebuilds the website, it cannot
+> know how large visitors' web browser windows are going to be, so it cannot
+> scale the image relative to the size of a visitor's web browser window.
+>
+> The closest thing it could do would be to not scale the image at all
+> (potentially a very large download if it's a high-resolution photo),
+> and use CSS or `<img sizes=...>` to ask the visitor's web browser to scale
+> the image relative to something the web browser knows, such as the viewport
+> size.
+>
+> With HTML5 `<img sizes="..." srcset="...">`, it would be possible to extend
+> `[[!img]]` to produce more than one resized image and let the visitor's
+> browser choose which one to download, but I'm not sure what a good syntax
+> for that would look like...
+>
+> "The available space" is not something we can use, because current HTML
+> standards do not offer that. In HTML5 it is possible to base sizes on the
+> viewport (window) size, but the available space (excluding sidebars etc.)
+> is not something the browser can know in advance, because it needs to know
+> how large images are before it carries out layout calculations, and it
+> needs to carry out layout calculations before it can know the available
+> space.
+>
+> --[[smcv]]