1421318 - Google Translate: Unable to insert cursor into block of text

Status: RESOLVED WORKSFORME

(Core :: DOM: Editor, defect, P2)

Description

[Michael Ellis]

Steps to reproduce:
1. Visit Google Translate in the FF browser
2. copy-paste a block of text into the left-hand column for translation.
3. Once translated, attempt to double-click somewhere inside the block of text in order to edit the inputted text. 

Result:   Can highlight all, but cannot insert cursor
Expected Result:  Double click inside block of text to insert cursor.

Comment 1

[Mike Taylor [:miketaylr]]

I can reproduce when using the translate widget on the google search results page:

https://www.google.com/search?ei=P5IdWubgGerMjwTFgYSYCQ&q=google+translate&oq=google+translate

Comment 2

[Mike Taylor [:miketaylr]]

Tom, can you take a look?

Comment 3

[Michael Ellis]

Correction:  This bug effects the Google Translate Widget in the SERP, but not the G.Translate site

Comment 4

[Michael Ellis]

TY MIKE!

Comment 5

[Thomas Wisniewski]

This is due to Chrome and Firefox having different default selection behavior. What's happening is that their page is using JS to select all of the text on-click, because the textarea element has a "tob.poc" action:

    <textarea class="tw-ta tw-text-small" id="tw-source-text-ta" autocapitalize="off" autocomplete="off" autocorrect="off" rows="1" spellcheck="false" jsaction="focus:tob.pon;blur:tob.pof;tob.poc"></textarea>


tob.poc is ultimately a click handler which selects the text:

    function() {
      document.activeElement != this.Hi.Ie && this.Hi.Ie.focus();
      this.Hi.Ie.setSelectionRange(0, this.$().length)
    }

However, Chrome seems to be ignoring the setSelectionRange call *if* the text is already selected, and the user is doing a simple click in one spot to de-select the text. Firefox does not ignore the call in this case, so the text remains selected. WebKit follows Chrome's behavior, while Edge follows ours. Perhaps we ought to adopt the Chrome behavior?

Comment 6

[Mike Taylor [:miketaylr]]

Thanks Tom. Let's move this to Core::Editor.

Comment 7

[Firefox Bug Husbandry Bot]

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Comment 8

[Firefox Bug Husbandry Bot]

See bug 1547409. Migrating whiteboard priority tags to program flags.

Comment 9

[Mike Taylor [:miketaylr]]

It looks like Google fixed this (?maybe?). Tom could you make a reduced test case of your findings in case the interop bug still reproduces.

Comment 10

[Mike Taylor [:miketaylr]]

Oops, ni? Tom for Comment 9

Comment 11

[Thomas Wisniewski [:twisniewski]]

Alas, it seems that I didn't provide enough detail at the time to make a test-case, as I just wrote one based on comment 5 and it's not reproducing the problem (even in Firefox 56).

Comment 12

[Mike Taylor [:miketaylr]]

OK, thanks for checking. Let's go ahead and close then.