urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge branch 'master' of ssh://git.ikiwiki.info/srv/git/ikiwiki.info

master
Joey Hess 2010-09-19 20:15:38 -04:00
parent 8063b960ad 2745dfee60
commit 012300404e
2 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/bugs/cutpaste.pm:_missing_filter_call.mdwn
View File

@ -39,3 +39,17 @@ function.
> constraints, without removing cutpaste's ability to have forward pastes > constraints, without removing cutpaste's ability to have forward pastes
> of text cut laster in the page. (That does seems like an increasingly > of text cut laster in the page. (That does seems like an increasingly
> bad idea..) --[[Joey]] > bad idea..) --[[Joey]]
> > OK -- so the FOO/BAR thing was only a very stripped-down example, of
> > course, and the real thing is being observed with the
> > *[[plugins/contrib/getfield]]* plugin. This one needs to run *before*
> > `preprocess`ing, for its `{{$page#field}}` syntax is (a) meant to be usable
> > inside ikiwiki directives, and (b) the field values are meant to still be
> > `preprocess`ed before being embedded. That's why it's using the `filter`
> > hook instead of `sanitize`.
> > Would adding another kind of hook be a way to fix this? My idea is that
> > *cut* (and others) would then take their data not during `scan`ning, but
> > *after* `filter`ing.
> > --[[tschwinge]]

3
doc/tips/html5.mdwn
View File

@ -15,7 +15,8 @@ No care is taken to add backwards compatability hacks for browsers that
are not html5 aware (like MSIE). If you want to include the javascript with are not html5 aware (like MSIE). If you want to include the javascript with
those hacks, you can edit `page.tmpl` to do so. those hacks, you can edit `page.tmpl` to do so.
[Dive Into HTML5](http://diveintohtml5.org/) is a good reference for [Dive Into HTML5](http://diveintohtml5.org/) is a good reference for
current compatability issues and workarounds with html5. current compatability issues and workarounds with html5. And a remotely-loadable
JS shiv for enabling HTML5 elements in IE is available through [html5shiv at Google Code](http://code.google.com/p/html5shiv/).
--- ---