From 647fd97bef55d2371e87f0cd418ddff62f36800e Mon Sep 17 00:00:00 2001
From: Jez Ng
Date: Wed, 24 Oct 2012 15:33:56 -0400
Subject: Use insertCSS() API instead of manually created style element.

For some reason addCssToPage seemed to break on Chrome 24.

Closes #676.
---
 content_scripts/link_hints.coffee | 1 -
 1 file changed, 1 deletion(-)

(limited to 'content_scripts/link_hints.coffee')

diff --git a/content_scripts/link_hints.coffee b/content_scripts/link_hints.coffee
index 55a78036..5c7f6510 100644
--- a/content_scripts/link_hints.coffee
+++ b/content_scripts/link_hints.coffee
@@ -60,7 +60,6 @@ LinkHints =
     @setOpenLinkMode(mode)
     hintMarkers = @markerMatcher.fillInMarkers(@createMarkerFor(el) for el in @getVisibleClickableElements())
 
-    DomUtils.addCssToPage(settings.get("userDefinedLinkHintCss"), "vimiumLinkHintCss")
     # Note(philc): Append these markers as top level children instead of as child nodes to the link itself,
     # because some clickable elements cannot contain children, e.g. submit buttons. This has the caveat
     # that if you scroll the page and the link has position=fixed, the marker will not stay fixed.
-- 
cgit v1.2.3