Hi!
> <a href="#"
> onclick="clear__5Fid0();document.forms['_id0'].elements['autoScroll'].value=
> getScrolling();document.forms['_id0'].elements['_id0:_link_hidden_'].value='
> _id0:pageID';if(document.forms['_id0'].onsubmit){if(document.forms['_id0'].o
> nsubmit())
> document.forms['_id0'].submit();}else{document.forms['_id0'].submit();}retur
> n false;" id="_id0:pageID"></a
>
One thing which makes me felling a little bit uncomfortable is the size
of the resulting html file.
Say you have hundreds of command links in your jsf
(tree/datatable/navigation) especially a tree with client side
navigation tends to hold many entries - imagine the size of the
resulting html file with all this onclick= on each command link.
Like the clear__ method we can render a submit__ javascript method which
wraps all this stuff, cant we?
And maybe we can call this clear__ from within submit__ too, so this
makes the above url something like:
> <a href="#"
> onclick="return submit__5Fid0()" id="_id0:pageID"></a
>
Or do I miss something?
If not, I'll prepare a patch for it.
Ciao,
Mario