Google search translate textarea secondary selection working in Chrome Safari but not Firefox Edge
Reported by
kdub...@mozilla.com,
Sep 26 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0 Example URL: Steps to reproduce the problem: 1. Go to https://www.google.com/search?q=translate 2. Type a text. 3. Click outside of the box 4. Click inside the box (all text is selected. Works everywhere the same.) 5. Click a second time. What is the expected behavior? The caret is inserted at the position of the click in the text. Safari behaves the same way than Chrome. What went wrong? In Firefox 57 and 58, this is not happening, the full text stays selected. In the original Webcompat report it is said that Edge is behaving the same way than Firefox. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? N/A Chrome version: <Copy from: 'about:version'> Channel: stable OS Version: OS X 10.13 Flash Version: This does NOT happen in https://translate.google.com/#fr/en/La%20vie%20est%20un%20long%20fleuve%20tranquille. This is a spin-off of https://webcompat.com/issues/9032
,
Sep 26 2017
Tested the issue on latest stable 61.0.3163.100 and on latest canary 63.0.3223.8 using Ubuntu 14.04,Windows 7 and Mac 10.12.6 and is reproducible with steps mentioned below. 1. Navigated to https://www.google.com/search?q=translate and typed "test" in the text box. 2.Clicked outside translation box and now tried selecting "es" from "test". 3.Observed selection of entire "test" instead of "es". NOTE: In Firefox also entire text gets selected. But unable to select some part of text as no cursor is seen there. This issue is seen from M50 [50.0.2166.0] . Hence considering this issue as Non-regression and marking as Untriaged for further inputs.
,
Oct 3 2017
kdubost@, could you tell me your intention? Do you want to make Chrome to behave as same as Firefox? It seems Chrome, FireFox and Edge behave differently, e.g. mouse press selected range and mouse release after a few seconds, Chrome and Edge set caret, Firefox keeps range selection.
,
Oct 3 2017
yosin sure. The intent is to understand why we have the difference and understands if a set of browsers need to be modified and/or if the spec is clear enough so that we do not have any ambiguities. Or if it's just something in the code of the site giving a different behavior to certain browsers. Basically we need to diagnose the source of the issue.
,
Oct 3 2017
Thank you for providing more feedback. Adding requester "yosin@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 3 2017
Thanks kdubost@ for explanation. Once you find the root cause of behavior differences, please reopen this issue or file a new bug.
,
Oct 3 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Sep 26 2017