Item8995: some TwistyPlugin variations don't work in chrome browser (but the same TML works via chrome to tmwiki)

We've discovered a usage in the wild that works on tmwiki, but not on foswiki 1.0.9:

this is chrome browser specific

source

%TWISTY{prefix=" 
---++++!! " link="Bonus " showimgright="%ICONURLPATH{toggleopen}%" hideimgright="%ICONURLPATH{toggleclose}%" suffix=" 

"}% 

inside the twistie

%ENDTWISTY%

actual

---

-- SvenDowideit - 09 May 2010

foswiki.org's XHTML output is horribly, horribly broken at the moment with an unclosed script tag that can't be helping.

Even with trunk (and even with skin=plain), I am not sure that a span can always contain heading elements.

Finally, I am very disappointed that we have decided to assume HTML5 browsers and strip attributes from script and style tags. It is now impossible to get a default foswiki to validate properly until these are re-added, a more appropriate DOCTYPE is set or better - we come up with a nice way of adding script and css to a page (ADDTOZONE is a nice piece of the solution, but only a very small piece) where we could make these attributes optional via configure or some sort of skin cover.

-- PaulHarvey - 09 May 2010

Troublemaker is PiwikPlugin that is not tracked in svn.

Where have we decided to assume html5?

-- ArthurClemens - 10 May 2010

um, wft are you people talking about?

this bug has been found on a users system when converting to foswiki 1.0.9 from tmwiki.

It is also present here on foswiki.org.

I guess the only signal present in the noise is that it might be skin related - and you're wrong there too :/ - it happens on plain skin, pattern skin etc

-- SvenDowideit - 10 May 2010

Sven, my point was that the output of your twisty does not validate.

And now, as I noted in Item8998, JQueryPlugin emits html5 markup in XHTML-transitional documents, so we will never get our skins to validate.

-- PaulHarvey - 11 May 2010

The default mode is span (should be renamed to 'inline'?). That results in a span surrounding a h4 header, and Chrome does not accept it.

Solution is to set mode to div (should be renamed to 'block'?):

-- ArthurClemens - 12 May 2010

works like a charm, thankyou

we'll need to update some docco for migration..

-- SvenDowideit - 13 May 2010

Commenting is disabled while not logged in