+1 with the provisions mentioned by Sergiu. However I’m not entirely confident about our HTML5/XHTML validation tools. Specifically, I’m not 100% convinced that they find all validation issues but I don’t know those tools well so I could be wrong. I do know that we exclude some vms for various reasons. Thus putting clean=false could increase the possibility of having non XHTML/HTML5-valid output without noticing it.
The good part is that on the long run it should allow us to fix non-XHTML/HTML5-valid code instead of having it fixed by the HTML Cleaner. Thanks -Vincent > On 15 Jul 2016, at 16:13, Marius Dumitru Florea > <[email protected]> wrote: > > Hi devs, > > I'd like to propose that we use, from now on, {{html clean="false"}} when > developing applications, because: > > * HTML cleaning is an extra step that can increase page loading time > * the HTML cleaner can have bugs (like any other code) or unexpected > behaviour (like removing some elements or some attributes when you don't > expect it) > * when I make a mistake in my HTML code I'd like to detect it as soon as > possible, instead of letting the cleaner silently "fix" it for me. Note > that we would still have the webstandards validation tests as a safety net > (only for the default distribution though) > > We should keep clean=true by default because we don't want the XWiki users > to break the XWiki UI too easily when they copy some HTML from the web and > paste it inside the HTML macro. > > Here's my +1 > > WDYT? > > Thanks, > Marius _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
