5 Nov
2008
5 Nov
'08
5:52 p.m.
Thomas Mortagne wrote:
> Hi,
>
> On Tue, Nov 4, 2008 at 7:33 PM, Regan Gill
<rgill(a)acceptsoftware.com>
wrote:
It can be done. From JavaScript we can prevent the default behavior of
the browser and add our own logic. But then we would have to ask more
questions:
* do all the users expect the tab to indent?
* which character should be used? space or real tab. If space, how
many?
* what if the JavaScript is disabled?
Regards,
Marius
It could be an option setting for the wiki:
1. Default (focus change)
2. Insert Tab
3. Insert Space
I think if Javascript is disabled then they just get the default
behavior. (wouldn't other things not work in that case as well? )
My company is pretty picky about editors (we include FCKeditor in our
product and there are a lot of enhancement requests for that) so I am
getting quite a few requests for enhancements on the wiki including this
one. The other big one is a request for double click to edit. So I don't
know if I just have picky customers or not, but personally I would
really like to have tabs since they make code easier to write in the
pages.
Thanks for your replies,
Regan
> Hi,
>
> I have set up xwiki for my company's wiki. One complaint I am
getting a
> lot from users is that the tab key
doesn't insert a tab when
editing,
> instead it works like a form and moves the
focus. Is there a good
reason
for this
or just something no one got around to implementing?
If you are using Firefox, I think it's the default behavior of this
browser (when IE insert a tab character) in an input field.
Now, maybe we can catch the tab key event in some way... but I will
let more WYSIWYG experienced guys answer for this ;)