921544 - user-select: none not respected when drag starts from element without user-select:none

Status: RESOLVED DUPLICATE of bug 739396

(Core :: DOM: Selection, defect)

Description

[asleepysamurai]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36

Steps to reproduce:

When text-selection (or mouse drag) starts at an element which does not have user-select:none style applied, and passes over an element which does have user-select:none, then the unselectable text is highlighted as selected.

1. Goto http://jsfiddle.net/sbZhV/1/
2. Click the red div and start dragging southeast towards bottom-right corner of page, such that cursor passes over text in green div.


Actual results:

Text selection style is applied to the text.


Expected results:

Text selection style should not be applied to text in green div. Works as expected in Chrome.

Comment 1

[asleepysamurai]

In the above JSFiddle if the class 'noselect' is added to the red div, then the text in the green div is not selected.

Comment 2

[Mark Reid [:mreid]]

There's some inconsistency with copy/paste as well.

1. Go to http://jsfiddle.net/6xKQP/
2. Select some of the red text, all of the green text, and some of the blue text.
3. Edit > Copy
4. Paste the result somewhere

Actual results:
It does the "right thing" and only pastes the selectable parts

Expected results:
I expected the pasted text to match the selected text.

The actual results for copy/paste are good, and I think the displayed selection should only include the red+blue pieces.

Interestingly, while the selection *looks* correct in Chrome, it's copy/paste behaviour is wrong (it actually pastes the un-selected text too).

Comment 3

[Han Seoul-Oh]

I'm finding that this is fixed in the Firefox 35 beta, can you confirm?

I think this is clearly a duplicate of bug 832514 and bug 1032090, which are marked as duplicates of bug 739396, whose fix lands in Firefox 35.

Comment 4

[Florian Rivoal]

Confirmed, no longer reproduces

Comment 5

[xixixao]

(In reply to Han Seoul-Oh from comment #3)
> I'm finding that this is fixed in the Firefox 35 beta, can you confirm?
> 
> I think this is clearly a duplicate of bug 832514 and bug 1032090, which are
> marked as duplicates of bug 739396, whose fix lands in Firefox 35.

This is fixed now.

Comment 6

[Thomas Wisniewski]

Confirmed that this is fixed. Closing as a dupe of bug 739396.