[Bug 107247]

[Neil-httl]

(In reply to comment #23)
> The former fixes an issue where there is a selection within the editable
> area, but the editable area is not focusable, then tab is pressed. (The
> removed code from nsFocusManager is only called when there is nothing
> focused).
I could only get that code to be hit when there was a caret. I'm not sure how to make an unfocusable editable area, but I guess it won't have a caret.

> The editor-base.inc change though makes scrolling occur in a number of
> situations where it shouldn't, for example, scrolling should not occur while
> caret browsing is on, nor while the caret is within the focused editable
> area.
The global window commands already know about caret browsing. (If you look at the browser-base.inc then you'll see the bindings are the same. At some point we may want to rename them back to reduce confusion.) And, except for the code block in the focus manager, its idea of a caret also applies to editable areas, which was why I wanted to remove the code block!

> Is the editor attaching it's command controller to the document and not the
> editable area?
Correct. There was some issue with attaching the commands to the editable area which ehsan has pointed me towards several times but I still forget the bug #.

-- 
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/107247

Title:
  Launchpad bug pages trigger caret browsing in Firefox and other Gecko
  browsers

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/107247/+subscriptions