Hi,
have you tried adding a tabindex of 1 to something at the top of the page? Maybe that would solve it. I presume it is targetting that because it’s the only textfield, but maybe you could add the tabindex to an image or something like that.
Adrian Lawley: www.adrianlawley.com
That will most likely confuse things like screen readers though, might be a good workaround for now though until I figure it out.
Thanks
Lee
No, didn’t seem to fix it that.
If I remember correctly there is a piece of javascript in the web login snippet that sets focus to the login in form. If so, try to disable that piece of code in the snippet.
Not sure thought...
Look in assets/snippets/weblogin/weblogin.inc.php
find the following code:(lines 87 - 89)
<script type="text/javascript">
if (document.loginfrm) <?php echo !empty($uid) ? "document.loginfrm.password.focus()" : "document.loginfrm.username.focus()" ?>;
</script>
disable it or remove it completely
Exactly right breezer.
This code relic needs to die ASAP. I believe that inline JavaScript and CSS should be kept out of snippets and left to user created templates and templating chunks. Although forcing focus to a text input may be situationally useful, for many users, undoing this is going to cause nothing but confusion.
A user should be able to edit a chunk or TV to focus or blur a text input, but digging through code in files on their servers? (weblogin.inc.php?). That just sounds like either a really bad idea or a good way to break something.
-sD-
Dr. Scotty Delicious, Scientist.