From 7f81afd7efbeb931d16ce1f3a1ed53a54226d553 Mon Sep 17 00:00:00 2001 From: Bernhard Posselt Date: Fri, 7 Nov 2014 12:32:05 +0100 Subject: move 3rdparty directory to vendor to be more consistent with composer standard and because we also use js/vendor for third party libs --- .../ezyang/htmlpurifier/docs/proposal-colors.html | 49 ++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 vendor/ezyang/htmlpurifier/docs/proposal-colors.html (limited to 'vendor/ezyang/htmlpurifier/docs/proposal-colors.html') diff --git a/vendor/ezyang/htmlpurifier/docs/proposal-colors.html b/vendor/ezyang/htmlpurifier/docs/proposal-colors.html new file mode 100644 index 000000000..657633882 --- /dev/null +++ b/vendor/ezyang/htmlpurifier/docs/proposal-colors.html @@ -0,0 +1,49 @@ + + + + + + + +Proposal: Colors - HTML Purifier + + + +

Colors

+
Hammering some sense into those color-blind newbies
+ +
Filed under Proposals
+
Return to the index.
+
HTML Purifier End-User Documentation
+ +

Your website probably has a color-scheme. +Green on white, +purple on yellow, +whatever. When you give users the ability to style their content, you may +want them to keep in line with your styling. If you're website is all +about light colors, you don't want a user to come in and vandalize your +page with a deep maroon.

+ +

This is an extremely silly feature proposal, but I'm writing it down anyway.

+ +

What if the user could constrain the colors specified in inline styles? You +are only allowed to use these shades of dark green for text and these shades +of light yellow for the background. At the very least, you could ensure +that we did not have pale yellow on white text.

+ +

Implementation issues

+ +
    +
  1. Requires the color attribute definition to know, currently, what the text +and background colors are. This becomes difficult when classes are thrown +into the mix.
    2. +
  2. The user still has to define the permissible colors, how does one do +something like that?
    3. +
+ + + + + -- cgit v1.2.3