nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

inline FormAPI IE5.x vs. 6

System

iwserver: 5.5.2 Build 17976 Interwoven 20030323 on Solaris.

I have an inline that generates FormAPI code, for instance:

print join( "\n", '<substitution>', '<script>', 'alert( "HELLO" );', '</script>', '</substitution>' );

This works with IE6. When the DCT is loaded with IE5.5, the FormAPI returned by the linine does not execute (any items the inline generates show up on the form, just the FormAPI does not exucute). Is this a known issue, a bug or other? Is there some workaround?

Find more posts tagged with

Comments

nipper

Stupid question, have you checked the browser settings ?

We use a lot of formapi on both 5.5 and 6

Migrateduser

Thanks. Other FormAPI runs in IE5.5, just not the FormAPI generated by the inline.

Gregg Faus

Can you give an example of the HTML that is generated by your inline call? I would think that IE's 5.5 HTML parser may not evaluate the javascript the same if contained within a text or select element. A snippet would be helpful.

Migrateduser

Sorry, I'm not following. The inline is in the DCT, not a callout. It generates XML, not HTML. The XML looks like any other DCT XML. The FormAPI looks like any other FormAPI (well, ampersands and such would have to be XML escaped I guess but I haven't hit that yet).

Gregg Faus

Let me clarify.

Part of the inline in the DCT might look like this:

<select required="t" size="8" multiple="t">
 <inline command="iwperl /iw-home/httpd/iw-bin/scriptname.ipl "/>
</select>

Your inline command produces the following substitution text:

<substitution>
<option value="value1" label="Option 1"/>
<option value="value2" label="Option 2"/>
</substitution>

Then the resulting HTML when you hit the template would look similar to this:

<select class='multiSelectStyle' 
name='fieldname' size=10 multiple
onfocus='datacapture.handleElementSelect(1);' onblur='parent.api.iw_dispatch_handleOnChange(1,this);'>
<option value="value1">Option 1</option>
<option value="value2">Option 2</option>
</select>

So my question is what does the HTML look like? Is it well formed?

Migrateduser

Unfortunately "view source" doesn't work in the IE5.5.browser I am testing with, and everyone else is IE6. I imagine it's just an empty <checkbox> element as the options are populated by FormAPI which is loaded into a different frame.

Gregg Faus

The source will be the same in the IE 6.0 browser so just view it on a IE 6.0 machine and post that.

Migrateduser

Well this is strange, since the options are set by FormAPI I wouldn't expect them to appear in view source (when I run the inline the checkbox has no option subelements - the options don't appear unless the FormAPI runs).

<td colspan='1'>
<DIV id="ctl9">
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="ent" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>ent </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="hho" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>hho </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="partner" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>partner </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="partner-oem" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>partner-oem </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="partner-reseller" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>partner-reseller </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="partner-services" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>partner-services </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="partner-strategic" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>partner-strategic </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="partner-technology" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>partner-technology </font>
<input type='checkbox' name= 'metadataBusiness/business_customerType' value="smb" onclick='parent.api.iw_dispatch_handleOnChange(9,this);' onfocus='datacapture.handleElementSelect(9);'> <font class='label'>smb </font>


</DIV> </td>

catorarn

ENV: TS60L/win2k/solaris

Hi guys, fyi:

I set up customer files and reproduced the problem described in your discussion here. In my case I use the inline:

<?xml version="1.0" standalone="no"?>
<!DOCTYPE datacapture SYSTEM "datacapture5.0.dtd">
<data-capture-requirements type="content" name="">
<inline command="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/getdatacapture.pl" />
</data-capture-requirements>

If she puts in the following tag: <script> <![CDATA[alert("BOOOOO2");]]></script> then FormAPI works fine, however the same alert is called within getdatacapture.pl and this is not working. The getcatacapture.pl file contains the following FormAPI calls (I took the first part of the perl script which generates xml to put into the dct):

<ruleset name="generic">
<description>Global Standard Template : v1.0 (Released: 15-May-03)</description>
<script> <![CDATA[alert("BOOOOO2");]]></script>

<script language="javascript" location="webserver" src="/iw/userscript/global/standard/forminit.js"/>

Question is whether there is a way that calling FormAPI from another file into a datacapture.cfg will work. I have several customers that are trying to increase templating performance by using callouts to get dct items into their DCT from an xml file. Is FormAPI supported when you put the js reference into that xml file (generated by the callout perl script and integrated into the DCT at runtime)?

I am investigating this within Interwoven Support, so I'll update you guys in this thread on the results. Unless you have an answer and did not post it yet.

Migrateduser

> Unless you have an answer and did not post it yet.

No response from Interwoven, no information available anywhere on this, no point filing a support case = find a workaround.

SS_sample.zip

Migrateduser

The checkboxes look right in Mozilla (but of course other FormAPI and VFE does not), just not IE5.5 (so far).

SS_sample.PNG

hasel

I have the same problem but no idea, how you can fix this.
please tell me, if you know an answer.

Migrateduser

Can you move the <script> element from the inline into the DCT?

output_my_row.PNG

LooseCannon

The following will work.

Place the code in a perl file and call it from the dct via an inline

#!/YOURHOME/iwperl -w

print qq(<?xml version="1.0" encoding="UTF-8"?>
<substitution>

<script language="javascript">
alert("BAM");
</script>

</substitution>\n);

hasel

No, that's no possibility, cause the decision which javascript bekomes loaded is decided at runtime in the perl script.

Migrateduser

Potential workaround at http://devnet.interwoven.com/forums/cgi-bin/showthreaded.pl?Cat=&Board=PRODUCTS_TEMPLATING&Number=29779&page=&view=&sb=&o=&vc=1#Post29779