Firefox 3.6.3, reverted to 3.5.5...same issue.

Almost every time I launch either version I get this pop-up. (First launch after restarting or [I think] waking from long sleep goes OK, but subsequent launches generate the pop-up.)

I've done no customizing of Firefox other than setting my prefs to my liking.

Has anybody else run into this, and is there a fix?

Thanks.

Are you using a key combo that includes the Option key to launch Firefox?

Not any more.

Thanks, cyn.

Are you using a key combo that includes the Option key

I would NOT have considered that. Noted.

I should link to our previous discussion about this keyboard shortcut business [i may still do so when i get time] --- but (just for the record): i told you so.

[must include either ctrl or ⌘ to avoid hassles]

Hal gives artie a talking to.

Actually, I should have figured this out on my own either by Googleing or remembering that I ran into a similar issue with both Audio Hijck Pro and Fission.

(Just my luck to get backed into using my option key to launch all the wrong apps. [No problem with iPhoto, though, as long as I just give it a quick tap, rather than hold it.])

What the hey... Just another small bump in the road to computing nirvana!

The fascinating part of your linked discussion, though, is that Terminal seems to have a built-in "safety-valve," because in addition to control-C, control-option-C and control-shift-C will kill a process.

Has anybody noticed similar behavior as respects any other key combo?

I don't think so. I think that the extraneous keystroke had the effect of suppressing the launching of Calq (since neither Control-Option-C nor Control-Shift-C were the key combo to which you assigned that function); Terminal regarded both Control-Option-C and Control-Shift-C as Control-C with an extraneous keystroke—just as it does for me.

Isn't it curious that an extraneous keystroke can put the kibosh on one process but not affect another one?

I thought that was odd, too.

In this case, it turns out that control-C is being recognized by the terminal emulation itself, at a level even below readline. The output from:

stty -a

contains, among other things: intr = ^C , binding the ETX character (^C) to an interrupt request.

This is old unix code, configuring how to interpret the raw ASCII codes that are the ONLY input from a teletype-like device. It predates such new-fangled nuances as Command keys. (Control and Option would have been applied by the teletype to modify the ASCII code generated by the keystroke, but Command is just a flag that the terminal emulation layer never sees.)

Thanks for that; I think I actually got it.

I've noticed over the years that some key combos are unaffected by the addition of some modifier keys, but there doesn't seem to be any immediately obvious rhyme or reason to it.

For example, hit the Tab key in a TextEdit document. Now hit Option-Tab, or Control-Option-Tab. Same behavior as the plain Tab key, right? But Control-Tab does nothing.

That's not the way it works in TextEdit 1.5 on my deuced Mac(hina) running 10.5.8...

When I hit option-tab the first time it inserts a dash (Well, it looks like a dash, but it's shorter, not on my keyboard, and not displayed when I hit "option" with Keyboard Viewer open.) within the space demarcated by the stop.

When I hit it again...same line, it inserts an (multiple) un-dashed stop(s) before the initial stop (whereas hitting tab inserts un-dashed stops after the initial stop).

If I've already inserted a coupl'a un-dashed stops and hit it...same line, it deletes the last stop I've entered and replaces the first one with a dashed stop.

If I've got a dashed stop in a line and I hit "return," the next line replicates the preceding line up to the dash, and hitting return again (multiple times) clears the dash (and preceding stops) and leaves my cursor at the start of the line, after which "return" acts as expected.

Also, if I delete a line with a dashed stop and hit option-tab, the line is recreated up to the dashed stop.

Those are all the combos I've thought to try.

Well, clearly TextEdit was an unfortunate example for me to choose. I use it in Plain Text mode, and you're referring to Rich Text mode (as I discovered when I set out to make hide or hair of your reply).

I didn't follow all the convolutions of your report, but that's okay; the TextEdit reference was simply the first example that came to mind of the phenomenon under discussion—the effect, or lack thereof, of extraneous modifier keys on key combo behavior. Turns out that there is an explanation in this case...as, indeed, there likely are in most, if not all, cases (such as the one provided earlier by ganbustein). (Note that I said, " there doesn't seem to be any immediately obvious rhyme or reason to it.")

Yep...Rich Text mode.

Your point is well-taken, though.

(But what's the little dash all about, and why doesn't Keyboard Viewer show it?)

If you watch what's happening in the ruler, you'll get a huge clue.

What's happening is that you're invoking outline mode. Option-tab gets you into outline mode; within outline mode, option tab (or plain tab at the beginning of a line) indents the current line, moving it one level more subordinate in the outline. Shift-tab (or return at the beginning of a line) does the reverse, moving the line one level less subordinate. Move out enough times, and you get out of outline mode.

The formatting is controlled by the "Lists" popup menu (or by the Format->List... menu item), which lets you specify independently for each level how list items at that level are formatted. Items at each level can be labelled by consecutive letters (A, B, C, ...) of various types (uppercase, lowercase, greek, arabic) or numbers (1, 2, 3, ...) of various types (decimal, roman, japanese, arabic). Labels can be surrounded (or replaced by) arbitrary punctuation (leading/trailing parentheses, periods, quotes, angle brackets, whatever). The default is to label each line of the outline with a single hyphen.

The reason you can't see the hyphen used for formatting in Keyboard Viewer is that it's just formatting; it's not coming from the keyboard.

Thanks...useful info!

Who'da' thunk to look at the ruler? (And even if I had I'd never have thought of outline mode, because I've never either heard of or thought it would be nice to have such a critter.)

As dk said, "there doesn't seem to be any immediately obvious rhyme or reason to it."