MyShaarli/tpl/tagcloud.html

<!DOCTYPE html>
<html>
<head>{include="includes"}</head>
<body>
	<div id="pageheader">{include="page.header"}</div>
<div class="center">
    <div id="cloudtag">
        {loop="tags"}
        <span class="count">{$value.count}</span><a href="?searchtags={$key|urlencode}" style="font-size:{$value.size}pt;">{$key}</a>
        {/loop}
    </div>
</div>
{include="page.footer"}
</body>
</html>
Initial commit (version 0.0.40 beta) 2013-02-26 10:09:41 +01:00			`<!DOCTYPE html>`
			`<html>`
			`<head>{include="includes"}</head>`
			`<body>`
			`<div id="pageheader">{include="page.header"}</div>`
W3C compliance (work on issue #64 - https://github.com/shaarli/Shaarli/issues/64): * fix duplicate IDs - #paging_older, #paging_newer become classes as the paging is displayed twice (top, bottom) in the linklist * fix duplicate IDs - #paging_privatelinks and #paging_linksperpage become classes * daily links are now valid (use &amp) * name attribute is not used anymore on a tag in link list * center tag is replaced by CSS in picwall and tag cloud * action in form tag can't be empty, use # instead * fixed configure table with CSS instead of cellpadding, border, and valign * export links are now valid * remove "size" in input tag * Fix missing alt attributes for img elements * tpl/daily: Use HTML entities instead of char escape codes * tpl/export: fix missing </span> closing tag * Remove obsolete language attribute on <script> elements 2014-12-12 17:01:02 +01:00			`<div class="center">`
			`<div id="cloudtag">`
			`{loop="tags"}`
Working on shaarli/Shaarli#224 I reviewed character escaping everywhere with the following ideas: * use a single common function to escape user data: `escape` using `htmlspecialchars`. * sanitize fields in `index.php` after reading them from datastore and before sending them to templates. It means no escaping function in Twig templates. 2 reasons: * it reduces risks of security issue for future user made templates * more readable templates * sanitize user configuration fields after loading them. 2015-06-11 13:53:27 +02:00			`<span class="count">{$value.count}</span><a href="?searchtags={$key\|urlencode}" style="font-size:{$value.size}pt;">{$key}</a>`
W3C compliance (work on issue #64 - https://github.com/shaarli/Shaarli/issues/64): * fix duplicate IDs - #paging_older, #paging_newer become classes as the paging is displayed twice (top, bottom) in the linklist * fix duplicate IDs - #paging_privatelinks and #paging_linksperpage become classes * daily links are now valid (use &amp) * name attribute is not used anymore on a tag in link list * center tag is replaced by CSS in picwall and tag cloud * action in form tag can't be empty, use # instead * fixed configure table with CSS instead of cellpadding, border, and valign * export links are now valid * remove "size" in input tag * Fix missing alt attributes for img elements * tpl/daily: Use HTML entities instead of char escape codes * tpl/export: fix missing </span> closing tag * Remove obsolete language attribute on <script> elements 2014-12-12 17:01:02 +01:00			`{/loop}`
			`</div>`
Initial commit (version 0.0.40 beta) 2013-02-26 10:09:41 +01:00			`</div>`
			`{include="page.footer"}`
			`</body>`
CSS: remove hardcoded style from templates Fixes shaarli/Shaarli#29 Style elements refactored as follows: - use existing ids and classes if possible, - else, define new ones and stick with the existing naming convention, - remove hardcoded style attributes from RainTPL templates. Exception: In tpl/tagcloud.html, the display size of each tag is computed at page generation. Signed-off-by: VirtualTam <virtualtam@flibidi.org> 2014-12-02 21:00:52 +01:00			`</html>`