Posted: 10/28/2008 2:50:48 PM EDT
|
From the text area where you type your message to tab right to the submit button... the way it was before the addition of the subscribe drop-down was added.
I'm so used to being able to tab once and be on the submt button and then just hit enter... not only on here but on Gmail and an online game I play.... Please? Done something like this |
|
The tab order for standard mode is fixed The tab order for the WYSIWYG mode is still 2 The tab order when you start a new topic and tab from the subject box... normallly goes into the main message box.... in WYSIWYG it doesn't. It actually followed the  after you tab through all of the smilies. |
|
Quoted: The tab order for standard mode is fixed The tab order for the WYSIWYG mode is still 2 The tab order when you start a new topic and tab from the subject box... normallly goes into the main message box.... in WYSIWYG it doesn't. It actually followed the after you tab through all of the smilies.The WYSIWYG editor has an additional tab because you are typing inside a window versus an html element. so once you are done typing you need to hit tab twice. I'll try to find a solution. |
HTML DOM tabIndex PropertyHTML DOM tabIndex Property[url=http://www.w3schools.com/htmldom/dom_obj_text.asp] [img class='navup']http://www.w3schools.com/images/up.gif[/img] Complete Text Object Reference[/url] Definition and UsageThe tabIndex property sets or returns the tab index for a text field. The tab order defines the order the elements appear if you navigate the page using the "tab" button on the keyboard. Syntax
ExampleThe following example alerts the tab index of different text fields: <html> <head> <script type="text/javascript"> function checkTab(x) { alert(x.tabIndex) } </script> </head> <body> <form id="myForm"> <input type="text" tabindex="1" onclick="checkTab(this)"> <input type="text" tabindex="2" onclick="checkTab(this)"> <input type="text" tabindex="3" onclick="checkTab(this)"> </form> </body> </html> |
|
You obviously failed to read my post or to understand it. The WYSIWYG editor is based off an internal page, thus not an element of the main window. So when the cursor is located off the page, it can't follow tabindex standards. Make sense? Since you seem motivated to offer help, why dont you code a custom javascript add-on to control cursor through the external page. I could use that more than the tabbing, but you can code come up with that bit of code too. Shouldn't be too bad, just have the javascript in the page catch the tab, pass it back to the parent, then push to the next tab index item.  |
|
I think I understand... it still tabs out, I just don't know where it tabs out the first time you do it. When the cursor is in the WYSIWYG you can still tab out of it... just takes two strikes. I'm not sure I understand what you mean as to why it doesn't go on the first one. With the subject field... there is still a tab order from the subject... it goes from there to the submit button.83 strikes from the subject field to cycle through all of he links from the top of the page down through all the smilies into the WYSIWYG area. Reverse tabbing is 27 strikes cycling from the bottom links up. So I'm nto entirely sure why you if it can get there, just the long way around, why the order can't be changed. Or why you would need a JScript to do it. |