Upon further investigation, I believe the problem I have encountered is
related to TOMAHAWK-606. (See [1])
My t:commandLinks and t:commandButtons are also not working, with the
same javascript error message appearing for all 3 components:
"newInput has no properties" (firefox)
I see references to a "newInput" in some javascript functions that
Tomahawk is generating. This is the first I've seen these javascript before:
----------------------------------------------
function oamSetHiddenInput(formname, name, value)
{
var form = document.forms[formname];
if(form.elements[name]==undefined)
{
var newInput = document.createElement['input'];
newInput.setAttribute('type','hidden');
newInput.setAttribute('name',name);
newInput.setAttribute('value',value);
form.appendChild(newInput);
}
else
{
form.elements[name].value=value;
}
}
function oamSubmitForm(formName, linkId, target, params)
{
var clearFn =
'clearFormHiddenParams_'+formName.replace(':','_');
if(eval('window.'+clearFn)!=undefined)
{
eval('window.'+clearFn+'(formName)');
}
if(window.getScrolling!=undefined)
{
document.forms[formName].elements['autoScroll'].value=getScrolling();
}
if(target!=undefined && target != null)
{
document.forms[formName].target=target;
}
if(params!=undefined && params != null)
{
for(var i=0; i<params.length; i++)
{
oamSetHiddenInput(formName,params[i][0],
params[i][1]);
}
}
oamSetHiddenInput(formName,formName +':'+'_idcl',linkId);
if(document.forms[formName].onsubmit)
{
var result=document.forms[formName].onsubmit();
if( (typeof result == 'undefined') || result )
{
document.forms[formName].submit();
}
}
else
{
document.forms[formName].submit();
}
return false;
}
----------------------------------------------
Given the correlations, I will not create a new JIRA for this. Instead,
I will post comments on the existing issue TOMAHAWK-606. Looks like no
one has posted a full example demonstrating the bug, so maybe I can do that.
[1] http://issues.apache.org/jira/browse/TOMAHAWK-606
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Mike Kienenberger wrote:
On 9/20/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
My t:panelNavigation2 problem occurs when using Core 1.1.4 (release)
with Tomahawk 1.1.5 (nightly 2006-09-16)
However, the component works fine when I also use the nightly core build
of the same date.
So, only issue worth pursuing vis-a-vis my panelNavigation2 problem
would be to get the Tomahawk 1.1.5 branch patched to restore
compatibility with Core 1.1.4 release. Sound reasonable?
Later, when I have time, I'll see if there is already a JIRA somewhere.
Otherwise, I'll work on providing more information to get one started.
1.1.4 and 1.1.5 (either package) should be compatible with each other.
So I'd consider that a blocker issue for a 1.1.4 tomahawk release.
Yes, please check and see if there's already an open JIRA issue and,
if not, please open a new one with an example showing the
incompatibility and stating which combinations work and which do not.
