User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050718 Camino/0.9a2 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050718 Camino/0.9a2 Standard OS X-wide keybindings don't work in HTML form fields. For example, in most applications, ctrl-d is the equivalent of delete. This doesn't work in Camino. Reproducible: Always Steps to Reproduce: 1. Go to http://google.com, or any other page with a form field. 2. Enter some text. 3. Position the cursor under a character. 4. Press ctrl-d. Actual Results: Nothing. Expected Results: The character under the cursor should have been delete.

I could have sworn there was a bug on this already. Ah, well. I agree this is a good idea. (The reason they don't already work is simply because they aren't Cocoa text fields.)

Some tweaking in htmBindings.xml should enable it I think. http://lxr.mozilla.org/mozilla/source/content/xbl/builtin/mac/platformHTMLBindings.xml

(In reply to comment #2) > Some tweaking in htmBindings.xml should enable it I think. > http://lxr.mozilla.org/mozilla/source/content/xbl/builtin/mac/platformHTMLBindings.xml I'm am not sure exactly what you're suggesting, but I think that it may not be a "complete" solution--for Cocoa apps, the bindings are fully customisable via ~/Library/KeyBindings/DefaultKeyBinding.dict, etc.

It seems to me that he wants Emacs-style keystrokes to work in textareas and text inputs.

All Cocoa bindings should be respected, even if customized. For me it is Control-A (Go to beginning of line) and Control-E that I feel are missing.

None of Cocoa bindings is working : Control-E, Control-A, control-F, control-B :-((( If they worked, I would have switched from Safari !

If all we need to do is edit that file, then here's a patch (with bindings taken directly from the Unix version of this file).

Of course, this will affect all Mac apps, which we may or may not want, but there it is.

A slightly better patch. I forgot some mutli-line stuff and I forgot to add to the "editor" block. Also cleaned up some indentation.

Wevah, how do we implement these patchs ?(In reply to comment #9) > Created an attachment (id=193667) [edit] > Better patch. > > A slightly better patch. I forgot some mutli-line stuff and I forgot to add to > the "editor" block. Also cleaned up some indentation. Wevah, how do we implement these patches ? I don't know anything about it

Oops! This is already done in the nightlies. I just forgot to dupe this bug to the other bug. *** This bug has been marked as a duplicate of 229473 ***

(In reply to comment #11) > Oops! This is already done in the nightlies. I just forgot to dupe this bug to > the other bug. > > *** This bug has been marked as a duplicate of 229473 *** Thanks, but it still doesn't work (I have downloaded the latest nightly build). For example, just go to the Camino home page, http://www.mozilla.org/projects/camino/homepage.html, and in the upper right corner, after "Search Mozilla", type anything you want and then press "ctrl-A" to return to the beginning of your line : you obtain a "bong", and nothing more :-((

It works for me.

Well... I don't understand, it definitely doesn't work for me... Just in case, I use Mac OS X 4.2 (in French), my keyboard is an AZERTY one...

It looks like it's only checked in on the trunk. You can get a nightly trunk build at ftp.mozilla.org/pub/mozilla.org/camino/nightly/latest/ (as opposed to /latest-1.0/ ) if you desire use of these bindings (as I'm sure you do, commenting here, and all). Just keep in mind that it's trunk and not the Camino 1.0 branch if you file any new bugs on it.

Thanks ! It works fine now. I didn't know the existence of this "trunk"...

Isn't the relatively new 1.0rc1 built from the trunk? This patch obviously hasn't been applied to whatever rc1 was built from, and that's quite a pity. This is rather important functionality for a lot of people who are used to C-a and C-e, for example.

1.0rc1 is built off the 180branch, the trunk won't ship for about a year.

ok, and you can't apply this (or other) patches selectively in the interest of Mac users?