From 4c4c517cf99c0eaadfee5d1c413715a8db0953bf Mon Sep 17 00:00:00 2001
From: Domenic Denicola <d@domenic.me>
Date: Wed, 13 Jul 2016 19:00:27 -0400
Subject: [PATCH] Remove unnecessary and unimplemented canvas tainting when
 painting text

As discussed in #1540, this check does not give any additional
protections over those already provided by CORS, which these days fonts
are subject to.

Fixes #1540. Helps with #1431.
---
 source | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/source b/source
index a7e54895c61..b84a8d7673c 100644
--- a/source
+++ b/source
@@ -62679,18 +62679,6 @@ try {
 
    </li>
 
-<!--ADD-TOPIC:Security-->
-   <li><p>If the <span>text preparation algorithm</span> used a font that has an <span>origin</span>
-   that is not the <span data-x="same origin">same</span> as the <span>origin</span> specified by
-   the <span>entry settings object</span> (even if "using a font" means just checking if that font
-   has a particular glyph in it before falling back to another font), then set the
-   <code>CanvasRenderingContext2D</code>'s <span
-   data-x="concept-canvas-origin-clean">origin-clean</span> flag to false.</p></li>
-   <!-- because fonts could be considered sensitive material, I guess; and because that
-   sensitivity could extend to whether or not a particular glyph is in the font in the first place.
-   -->
-<!--REMOVE-TOPIC:Security-->
-
   </ol>
 
 <!--v6DVT - this is commented out until CSS can get its act together