contentEditable elements are not considered clickable by the event fluffing code

RESOLVED FIXED in mozilla26

Status

()

Core
Event Handling
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: vingtetun, Assigned: vingtetun)

Tracking

Trunk
mozilla26
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Created attachment 750971 [details] [diff] [review]
Patch

Sounds like a contentEditable item should be considered like an input element.

(Gaia use a contentEditable area for writing sms/mms).
Attachment #750971 - Flags: review?(roc)
Comment on attachment 750971 [details] [diff] [review]
Patch

Review of attachment 750971 [details] [diff] [review]:
-----------------------------------------------------------------

::: layout/base/PositionedEventTargeting.cpp
@@ +155,5 @@
>      if (content->AttrValueIs(kNameSpaceID_None, nsGkAtoms::role,
>                               nsGkAtoms::button, eIgnoreCase)) {
>        return true;
>      }
> +    if (content->HasAttr(kNameSpaceID_None, nsGkAtoms::contenteditable)) {

I think you should call IsEditable. We want to the descendants of a contenteditable element return true here too.

And please add a test.
Created attachment 758179 [details] [diff] [review]
Patch v2 + tests
Assignee: nobody → 21
Attachment #750971 - Attachment is obsolete: true
Attachment #750971 - Flags: review?(roc)
Attachment #758179 - Flags: review?(roc)
https://hg.mozilla.org/mozilla-central/rev/eeb4c68989f3
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.