Closed Bug 1159949 Opened 5 years ago Closed 4 years ago
[Browser][Text Selection] Using 'Select All' in a browser window causes the selection carets to move toward the top corners of the screen, where they are non-functional
Description: When using 'Select All' in Browser, the Carets will move to the top corners of the browser. These carets are largely unselectable by the user, as they almost always activate Edge Gestures. When the user does manage to select the carets, they will move in unpredictable ways that do not allow the user to effectively modify the selection. Repro Steps: 1) Update a Flame to 20150429010205 2) Connect to a WiFi or Data network. 3) Perform a Google search using the Rocketbar to open a google results page in the Browser. 4) Long press a word on the page and choose the 'Select All' icon. Actual: Both selection Carets move to the top corners of the screen where they are non-functional. Expected: The two selection carets move to the beginning and the end of the selected content, and are still functional and selectable. Environmental Variables: Device: Flame 3.0 (319MB)(Full Flash) Build ID: 20150429010205 Gaia: 6e35b0948c42a4398b8a5916015de167121683a1 Gecko: 1ad65cbeb2f4 Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: 8/8 See attached: Video (URL), Logcat
This issue DOES occur on Flame 2.2 builds. Both selection Carets move to the top corners of the screen where they are non-functional. Environmental Variables: Device: Flame 2.2 (319MB)(Full Flash) BuildID: 20150429002501 Gaia: 1b7aa7e60788668ed09abf76022dfa231dbe88d4 Gecko: d38ff4717f39 Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Component: Gaia::Browser → Selection
Product: Firefox OS → Core
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
This will happen if dom tree have out-of-flow elements. Thus, those out-of-flow elements are continuous in the dom tree but not in the visual. Right now caret will have some problem in this case. In the google search page, the search form on the top of page is absolute element. So caret is non-funtional.
This also happens on complex web pages per comment 2. We cannot do anything on caret side.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.