tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gredler (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Commented: (TAPESTRY-195) Cannot disable auto-focus feature in ValidField
Date Fri, 20 Jan 2006 02:10:42 GMT
    [ http://issues.apache.org/jira/browse/TAPESTRY-195?page=comments#action_12363350 ] 

Daniel Gredler commented on TAPESTRY-195:

Are there any updates on this? Is this going to be fixed in a 3.0.4 or in 4.1?

On some pages I have a form divided up into different tabs. The background tabs are hidden
using CSS (display:none). Sometimes tapestry generates JavaScript that tries to focus fields
that are hidden on these background tabs, which causes errors.

On some pages I have the issue described above, where the page automatically scrolls down
and skips the intro section above the form.

Finally, a somewhat related issue is that all of this is done in a function that overwrites
window.onload, so any custom window.onload functionality is lost. It'd be nice if you used
something like this (http://simon.incutio.com/archive/2004/05/26/addLoadEvent):

function addLoadEvent(func)
	var oldonload = window.onload;
	if (typeof window.onload != 'function'){
    	window.onload = func;
	} else {
		window.onload = function(){

> Cannot disable auto-focus feature in ValidField
> -----------------------------------------------
>          Key: TAPESTRY-195
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-195
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 3.0
>  Environment: Operating System: MacOS X
> Platform: Macintosh
>     Reporter: Lars Hoss

> The method addSelect(IRequestCycle) (line 131) adds JavaScript code to the body
> in order to automatically select and focus the ValidField. Though this feature
> is very nice it would be useful if there was a way to disable it. For example
> let's assume a rather long page where the form is located at the end of the
> page. The current implementation causes the browser to jump to the end of the
> page and therefore hide the beginning of the page. A simple solution might be to
> add a parameter to ValidField that triggers the code generation. But if you have
> many ValidFields in a form this solution isn't very convenient. Personally I
> would say that this "option" belongs to the Form component but then ValidField
> needs to talk to the Form component in some way. If you like I could develop a
> solution myself and present it afterwards?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message