Bug 90462 - [BlackBerry] Touch hold on input field does trigger selection for some special cases
Summary: [BlackBerry] Touch hold on input field does trigger selection for some specia...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit BlackBerry (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-03 08:06 PDT by Yongxin Dai
Modified: 2012-07-07 12:23 PDT (History)
3 users (show)

See Also:


Attachments
Patch (2.17 KB, patch)
2012-07-03 08:52 PDT, Yongxin Dai
no flags Details | Formatted Diff | Diff
Patch (2.18 KB, patch)
2012-07-03 08:58 PDT, Yongxin Dai
no flags Details | Formatted Diff | Diff
Patch (2.19 KB, patch)
2012-07-03 09:53 PDT, Yongxin Dai
no flags Details | Formatted Diff | Diff
Patch (2.17 KB, patch)
2012-07-03 11:34 PDT, Yongxin Dai
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yongxin Dai 2012-07-03 08:06:32 PDT
Node::canStartSelection() can return false on the host node of the selectable input text field for some special cases.
Comment 1 Yongxin Dai 2012-07-03 08:52:24 PDT
Created attachment 150620 [details]
Patch
Comment 2 Antonio Gomes 2012-07-03 08:56:55 PDT
Comment on attachment 150620 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=150620&action=review

could you confirm the original problem fixed by the code you are changing does not regress?

> Source/WebKit/blackberry/ChangeLog:6
> +        Reviewed by Antonio Gomes.

I have not reviewed it :)

Tools can fill it up for you
Comment 3 Yongxin Dai 2012-07-03 08:58:57 PDT
Created attachment 150622 [details]
Patch
Comment 4 Yongxin Dai 2012-07-03 09:53:22 PDT
Created attachment 150631 [details]
Patch
Comment 5 Rob Buis 2012-07-03 10:00:43 PDT
Comment on attachment 150631 [details]
Patch

LGTM.
Comment 6 Yongxin Dai 2012-07-03 10:24:43 PDT
I can confirm the original problem fixed by the code. I tested the fix with various text input fields in past 2 days. I haven't found problem yet.


(
(In reply to comment #2)
> (From update of attachment 150620 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=150620&action=review
> 
> could you confirm the original problem fixed by the code you are changing does not regress?
> 
> > Source/WebKit/blackberry/ChangeLog:6
> > +        Reviewed by Antonio Gomes.
> 
> I have not reviewed it :)
> 
> Tools can fill it up for you
Comment 7 Rob Buis 2012-07-03 10:25:40 PDT
Comment on attachment 150631 [details]
Patch

It turns out the question Antonio asked still needs to be answered. Also the ChangeLog can be cleaned up a bit more, so far Antonio did not really review, so we should not mention him in the ChangeLog.
Comment 8 Yongxin Dai 2012-07-03 11:10:28 PDT
Hi Antonio,
I must misunderstood "original problem" in my last comment. What is the original problem you talked about?
Comment 9 Yongxin Dai 2012-07-03 11:34:53 PDT
Created attachment 150652 [details]
Patch
Comment 10 Antonio Gomes 2012-07-03 13:39:05 PDT
(In reply to comment #8)
> Hi Antonio,
> I must misunderstood "original problem" in my last comment. What is the original problem you talked about?

I mean, without your change, do a git blame to these lines you are changing, and check what was the problem it was trying to fix, when we decided to not work with shadow content. Basically, I am wondering if changing it back to how it was regresses the original issue fixed by these lines.
Comment 11 Rob Buis 2012-07-03 14:07:02 PDT
Comment on attachment 150652 [details]
Patch

LGTM.
Comment 12 Yongxin Dai 2012-07-03 14:35:31 PDT
The Original PR is #127814. It just said that text fields from fat finger should all ASSERT(!node->isInShadowTree()). But specific reason had not been mentioned.
Comment 13 Mike Fenton 2012-07-07 12:23:40 PDT
Invalid, the field should not be read only in the first place.

Investigation is continuing, but this is not the desired approach.