Open
Bug 1234719
Opened 9 years ago
Updated 2 years ago
Ctrl + text selection is impossible in entry fields (<div contenteditable> elements inside table) on https://vk.com/
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox46 | --- | affected |
People
(Reporter: arni2033, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: parity-chrome, Whiteboard: [h2review-noted])
Attachments
(2 files)
>>> My Info: Win7_64, Nightly 46, 32bit, ID 20151221030239
STR_1 (just read it):
1. Register on the site https://vk.com/ (russian social network; 75k daily users)
2. Focus an appropriate entry field:
2.A) Upload an avatar, click it to expand the image, click comment box below image
2.B) Add somebody to "My Friends", send him a message. Then go to "My Messages", open any
conversation (there'll be at least 1), focus entry field at the bottom of the page
3. Type "asdf zxcv" in the entry field from Step 2.
4. Select "sd" with mouse (hold left mouse button -> move mouse to select text -> release left button)
5. Hold Ctrl key (do not release it)
6. Select "xc" with mouse
STR_2 (the testcase):
1. Open attached "testcase 1" or the "data:" url in the form above
2. Select "sd" with mouse (hold left mouse button -> move mouse to select text -> release left button)
3. Hold Ctrl key (do not release it)
4. Select "xc" with mouse
Result: The whole table cell is selected
Expectations: There should be 2 selected items: string "sd" and string "xc"
Note that if I use <textarea> instead of <div contenteditable> in my testcase, this bug doesn't happen
Summary: Ctrl + text selection is impossible in entry fields (<div contenteditable> elements) on https://vk.com/ → Ctrl + text selection is impossible in entry fields (<div contenteditable> elements inside table) on https://vk.com/
Updated•8 years ago
|
Blocks: editor-blink-compat
![]() |
||
Comment 2•7 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [parity-Chrome]
Comment 3•5 years ago
|
||
I think that we should stop searching table cell or table element when we meet editing host boundary in this loop.
https://searchfox.org/mozilla-central/rev/efdf9bb55789ea782ae3a431bda6be74a87b041e/layout/generic/nsFrame.cpp#4376-4400
OS: Unspecified → All
Priority: -- → P3
Hardware: Unspecified → All
Updated•5 years ago
|
Whiteboard: [h2review-noted]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•