Open
Bug 882149
Opened 12 years ago
Updated 3 years ago
Coordinates near text area boundaries and line endings passed to caretPositionFromPoint produce wrong offsets
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: jimm, Unassigned)
References
Details
Attachments
(1 file)
2.41 KB,
text/html
|
Details |
Spun off from bug 865654:
(In reply to Scott Johnson (:jwir3) from comment #13)
> (In reply to Jim Mathies [:jimm] from comment #12)
> > (In reply to Scott Johnson (:jwir3) from comment #11)
> > > (In reply to Jim Mathies [:jimm] from comment #10)
> > > > Created attachment 761418 [details]
> > > > textarea
> > > >
> > > > This is still a little broken with text area boundaries, should I file a
> > > > follow up?
> > >
> > > Jim:
> > >
> > > Are you talking about if you expand the text area and then move the mouse
> > > over an area of whitespace to the right of a given line? If so, then I
> > > thought there was a bug on this already... let me see if I can find it.
> >
> > That's one problem, here are two test cases:
> >
> > 1) move your mouse to the lower edge of the textarea, you'll notice there is
> > a ~3 pixel inner boundary where cpfp returns 2 rather than a correct text
> > offset.
> >
> > 2) move your mouse to any text line and move right to the end of the text.
> > You'll notice that after the cursor moves past the last character, cpfp will
> > return an offset equal to the last character in the textarea, rather than
> > the offset at the end of the line.
>
> Ok, so these problems and the above mentioned problem in comment 11 are
> basically the same thing. What is happening is that the frame for a given
> point is being incorrectly returned (since there's an anonymous document
> structure inside of the text area). I thought there was a bug for this
> already, but a precursory search didn't turn anything up. So, yes, I think
> this should be a followup bug.
>
> As an aside, I think what we need to do for textareas is, given a point,
> find the nearest text frame to that point under certain conditions. I'm not
> 100% sure how this will work yet, though, since it's unclear that this will
> always return the correct frame.
![]() |
Reporter | |
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
Related to bug 343983?
Comment 3•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•