in reply to Re: CB sidebar auto-expansion problem
in thread CB sidebar auto-expansion problem

> What do you mean "if expandable"?

Typed text is substring of older/expanded text

See example in OP.

I just updated FF to 52.x before the trouble started, please check your version.

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

  • Comment on Re^2: CB sidebar auto-expansion problem

Replies are listed 'Best First'.
Re^3: CB sidebar auto-expansion problem
by beech (Parson) on Mar 28, 2017 at 02:49 UTC

    Hi,

    Oh you're talking about autocomplete/formfill/form completion , I usually turn that off (browser.formfill.enable false)

    I have older version of firefox (45...) and I dont get that problem with the chatterbox form

    I assume you've ruled out plugins by testing in -safe-mode?

    update: I just fired up brand new 52.0.1, cannot replicate the issue

    Do you experience phantom key presses with any other program?

      Thank you for your help!

      > I usually turn that off (browser.formfill.enable false)

      Good, a last resort! :)

      > I assume you've ruled out plugins by testing in -safe-mode?

      Did it now, problem persists.

      > Do you experience phantom key presses with any other program?

      No and to be clear, It's happening only if the Chatterbox Sidebar is opened in the sidebar (sic). (i.e. you need a bookmark, like explained here Other CB Clients

      When opened directly without bookmark the problem doesn't happen.

      For reproduction:

      • Open in sidebar!!!
      • Talk something like "... test" and wait till it shows up
      • Type "..." and hit TAB key to focus on [talk] button
      • The content of the input box has automatically expanded to ... test (or something lexically closer in your history) even before hitting RETURN
      • No dropdown was shown
      • If you repeat the last steps, but with clicking on [talk] without tabbing, the effect will be the same (no dropdown, but completion appears for a second in input before being send)

      I'm pushing my collegue to update his FF on his Win Box to test it there later.

      Cheers Rolf
      (addicted to the Perl Programming Language and ☆☆☆☆ :)
      Je suis Charlie!

      update

      I just failed to reproduce it in another instance of the same firefox but with another profile.

      Giving up now, will just turn off browser.formfill.enable in about:config , I rarely need to repeat myself ;-)

        Hi,

        Ok, now I can replicate it in the newest 52.0.1 , typing "..." posts "... test"

        There is a slightly different version of the bug in 45, when I type "..." and hit enter, nothing gets posted

        What a weird firefox bug :)