diff options
| author | Joey Hess <joey@gnu.kitenet.net> | 2009-10-05 16:18:54 -0400 |
|---|---|---|
| committer | Joey Hess <joey@gnu.kitenet.net> | 2009-10-05 16:18:54 -0400 |
| commit | 4b2eaac156433d6e16b4b63660654bb26561b77f (patch) | |
| tree | 3497c2ad18760ef6d28d6615efb3d8c82ebd756c | |
| parent | b8fae0ec3986b675d055a55fa986388d6c35658f (diff) | |
response
| -rw-r--r-- | doc/todo/CSS_classes_for_links.mdwn | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/todo/CSS_classes_for_links.mdwn b/doc/todo/CSS_classes_for_links.mdwn index 43a480be8..38db87724 100644 --- a/doc/todo/CSS_classes_for_links.mdwn +++ b/doc/todo/CSS_classes_for_links.mdwn @@ -92,3 +92,12 @@ I find CSS3 support still spotty... Here are some notes on how to do this in Ik >> As an alternative to patching the uses of `htmllink`, what do you think >> about patching `htmllink` itself? Are there circumstances where it might be >> used to generate a non-internal link? -- [[Jon]] + +>>> I think that the minimum configurability to get something that +>>> can be used by CSS to style the links however the end user wants +>>> is the best thing to shoot for. Ideally, no configurability. And +>>> a tip or something documenting how to use the classes in your CSS +>>> to style links so that eg, external links have a warning icon. +>>> +>>> `htmllink` can never be used to generate an external link. So, +>>> patching it seems the best approach. --[[Joey]] |