Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Ctrl+Shift+Arrow keys not working, stopped highlighting text [SOLVED]

  • 5 antwurd
  • 126 hawwe dit probleem
  • 11 werjeftes
  • Lêste antwurd fan tmdeppner

more options

Today I suddenly cannot use Ctrl+Shift+Arrow keys (right/left) to highlight text when composing messages in Gmail.

Today I suddenly cannot use Ctrl+Shift+Arrow keys (right/left) to highlight text when composing messages in Gmail.

Bewurke troch cor-el op

Alle antwurden (5)

more options

Just heard about Firefox "Safe Mode", so I tried that.

Things worked fine in Safe Mode, and I recalled that the add-on Firebug just installed an update. I disabled it and things are all good now.

more options

So I disabled Firebug and this resolved the issue too. I sure hope Firebug releases a fix for this soon, as it's a tool I use quite a bit.

Thanks for the advice tmdeppner!

more options

I hope they fix it soon, too.

If you want to follow the developers' discussion, there's a thread about it in the Firebug issues forum: http://code.google.com/p/fbug/issues/detail?id=3721

more options

OK - it's firebug but you don't need to throw out the baby with the bathwater and uninstall it.

The problem is key bindings. Basically when you do Control-Shift-Left (and Control-Shift-Right) firebug has those bound to "forward" and "backward" commands. You can fix those bindings and then they won't bug you again.

Click:

Tools -> Firebug -> Customize Shortcuts -> click on the "Go Forward" link and press Control-Shift-ALT-Right Arrow, then click on the "Go Back" link and press Control-Shift-ALT-Left Arrow.

Then click OK.

If you don't have firebug installed then it may be another plugin that is causing the issue...

more options

Nice to have a work-around until it's fixed. Thanks, uptoeleven.