Item10470: View broken in IE8

-- AndreasHafner - 10 Mar 2011

Commenting is disabled while not logged in

First: "new topic" view seems to be broken. There is only a text field for entering the topic name and a checkbox for allowing non-wiki names. Topic parent select field, template field and submit button missing completely.

Second: Another topic making excessive use of the twisty plugin (used to trigger display of sublevels of list) doesn't work either. Display stops at first occurence of toggle link.

Error occurs both in compatibility and normal mode. Client is Windows XP 5.1 SP3. IE is 8.0.6001. In Firefox all is fine.

Foswiki is 1.1.2, Twisty (1.6.11) and JQuery (4.00) are up to date. JQueryVersion in use (according to configure) is 1.4.4.

Both seems to be a jscript problem. As this is not limited on a plugin (only the second problem), I consider this to be quite urgent.

Many thanks and warm regards Andi

-- AndreasHafner - 11 Mar 2011

UPDATE 1

I found out that this minimal piece of code already breaks the view in IE8:

Test 1
% TWISTY{} %
Test 2
% ENDTWISTY %
Test 3

I consciously added spaces after the % so they don't expand.

All that shows up for me in IE8 is "Test 1" and my custom expand link (which is btw (mehr) ). Again all working fine with Firefox. If it wasn't for the "new topic" problem I'd say it's a Twisty problem.

Andi

-- AndreasHafner - 11 Mar 2011

UPDATE 2

Here are two lines you would never want to put into your WebPreferences:

• Set TWISTYPLUGIN_TWISTYSHOWLINK = <span style="font-size: smaller;">(mehr)<span>
• Set TWISTYPLUGIN_TWISTYHIDELINK = <span style="font-size: smaller;">(einklappen)<span>

After removing those lines, the example from UPDATE 1 works, as well as creating new topics. So this seemed to be Twisty related anyway.

The viewing problem of the heavily "Twisty"ed site still persists. Please contact me upon investigating this problem, and I will provide you with some TML code breaking the view.

Regards Andi

-- AndreasHafner - 11 Mar 2011

RESOLVED

Removed all custom preferences, cleared all the caches, everything works now.

Regards Andi

---

I guess you had an issue with double quotes - if so this needs to be documented. And next to that stale browser cached javascript.

-- ArthurClemens - 11 Mar 2011