Closed
Bug 561691
Opened 15 years ago
Closed 13 years ago
When body -moz-user-select is "none", setting MozUserSelect to "text" for a child node doesn't work
Categories
(Core :: DOM: Selection, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 203291
People
(Reporter: luxigo, Unassigned)
Details
Attachments
(1 file)
|
347 bytes,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.5pre) Gecko/20100424 Ubuntu/9.10 (karmic) Namoroka/3.6.5pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.5pre) Gecko/20100424 Ubuntu/9.10 (karmic) Namoroka/3.6.5pre
The contentEditable childNode content still cannot be selected
Reproducible: Always
Steps to Reproduce:
1. set body.MozUserSelect to "none"
2. set childNode[n].contentEditable to"true"
3. set childNode[n].MozUserSelect to "text"
Actual Results:
You can add content to childNode[n] but cannot select text nor move the insertion cursor.
Expected Results:
Content should be selectable and insertion cursor should be movable
Works with chrome
This might be the intended behavior; I'm not sure.
Component: General → Selection
Product: Firefox → Core
QA Contact: general → selection
Summary: When body -moz-user-select is "none", setting MozUserSelect to "text" for a childNode doesnt works → When body -moz-user-select is "none", setting MozUserSelect to "text" for a child node doesn't work
Version: unspecified → 1.9.2 Branch
Be coherent... When body.style.backgroundColor is set, i can change a child node style.backgroundColor...
On the other hand it works with webkit when setting body.webkitUserSelect to "none" and setting webkitUserSelect to "text" for a child node.
Sure I could also set backgroundColor to "blue" for every individual element of the page, then set it to "yellow" for the elements i want in yellow..
Thats what i should do with MozUserSelect so that my database management application with thousands of elements be Firefox compatible, but we will just use Chrome waiting for the bugfix)
I want MozUserSelect="text" only for contentEditable="true" elements.
Additional comment: I can move the insertion cursor, but only with keys, not with mouse.
Behaviour still exists in FF10. I agree with luxigo that this is not expected behaviour and leads to having to write way more complicated css rules in certain cases. Webkit does it "right", btw ;) I added a testcase file.
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•