Doubleclick drag selection (word by word selection) creates several selection ranges

NEW
Unassigned

Status

()

2 years ago
2 years ago

People

(Reporter: arni2033, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

User Story

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509

Step 0 is quite long to provide parity between steps in this comment and on attached "screenshot 1"

STR_1:
0. Open url [1] or extract attached "testcase 1" and open .htm file in browser.
   Doubleclick word "Используйте" in string "Используйте этот" w/o releasing left mouse button
1. Move mouse to word "примеры" in string "примеры их применения"
2. Move mouse to the right from search results
3. Move mouse vertically to the top, to the same horizontal line where you started selection
4. Move mouse to the left in that line, to word "Google" in string "Google может предлагать"
5. Move mouse to the word "оператор" in string "Используйте этот оператор"

AR:  Browser creates 3 selection ranges {1}, {2}, {3}
ER:  Only range {2}.  Browser should select ONLY text between selection start and selection end.

URL:
> [1] https://www.google.ru/search?q=%D0%BD%D0%B0%D0%B9%D1%82%D0%B8+%D1%81%D0%B8%D0%BC%D0%B2%D0%BE%D0%BB%D1%8B+%D0%B2+%D0%B3%D1%83%D0%B3%D0%BB%D0%B5&newwindow=1&client=firefox-b-ab&gbv=2&sei=SIfaV4H-F-P06ATQ_Z2QAw


Selection ranges from "actual result":
> {1} "Хотя перечисленные ниже символы поддерживаются, их включение в ... Если пунктуация не сделает поиск точнее, "
> {2} "этот оператор"  (According to bug 1250006. Or sometimes "Используйте этот оператор")
> {3} "найти сайты с похожим контентом.\nОператоры поиска Google и символы в запросах - Блог про SEO\nsky-fi.info › Поисковые системы"

Attachments

(2 attachments)

Comment hidden (spam)
(Reporter)

Updated

2 years ago
No longer blocks: 1277113
(Reporter)

Updated

2 years ago
Component: Untriaged → Selection
Product: Firefox → Core
(Reporter)

Updated

2 years ago
User Story: (updated)
Comment hidden (spam)
Comment hidden (spam)
You need to log in before you can comment on or make changes to this bug.