summaryrefslogtreecommitdiffstats
path: root/3rdparty/htmlpurifier/docs/ref-css-length.txt
diff options
context:
space:
mode:
authorBernhard Posselt <nukeawhale@gmail.com>2013-05-04 00:15:41 +0200
committerBernhard Posselt <nukeawhale@gmail.com>2013-05-04 00:15:41 +0200
commit10831dd274ff65d4852b47dbc398adae61845206 (patch)
tree9f9397bb7433fd53bfacf88d8c8b3cf2ef50e27d /3rdparty/htmlpurifier/docs/ref-css-length.txt
parent7b628a3e4d105f2e571d0fe142d59f201d6a10d0 (diff)
use html purifier for sanitation
Diffstat (limited to '3rdparty/htmlpurifier/docs/ref-css-length.txt')
-rw-r--r--3rdparty/htmlpurifier/docs/ref-css-length.txt30
1 files changed, 30 insertions, 0 deletions
diff --git a/3rdparty/htmlpurifier/docs/ref-css-length.txt b/3rdparty/htmlpurifier/docs/ref-css-length.txt
new file mode 100644
index 000000000..afbcc3125
--- /dev/null
+++ b/3rdparty/htmlpurifier/docs/ref-css-length.txt
@@ -0,0 +1,30 @@
+
+CSS Length Reference
+ To bound, or not to bound, that is the question
+
+It's quite a reasonable request, really, and it's already been implemented
+for HTML. That is, length bounding. It makes little sense to let users
+define text blocks that have a font-size of 63,360 inches (that's a mile,
+by the way) or a width of forty-fold the parent container.
+
+But it's a little more complicated then that. There are multiple units
+one can use, and we have to a little unit conversion to get things working.
+Here's what we have:
+
+Absolute:
+ 1 in ~= 2.54 cm
+ 1 cm = 10 mm
+ 1 pt = 1/72 in
+ 1 pc = 12 pt
+
+Relative:
+ 1 em ~= 10.0667 px
+ 1 ex ~= 0.5 em, though Mozilla Firefox says 1 ex = 6px
+ 1 px ~= 1 pt
+
+Watch out: font-sizes can also be nested to get successively larger
+(although I do not relish having to keep track of context font-sizes,
+this may be necessary, especially for some of the more advanced features
+for preventing things like white on white).
+
+ vim: et sw=4 sts=4