Closed
Bug 313164
Opened 19 years ago
Closed 19 years ago
Bidi: Caret navigation is broken inside inline elements
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
mozilla1.8rc1
People
(Reporter: uriber, Assigned: uriber)
References
Details
(Keywords: fixed1.8, regression)
Attachments
(2 files)
582 bytes,
text/html
|
Details | |
4.01 KB,
patch
|
smontagu
:
review+
roc
:
superreview+
asa
:
approval1.8rc1+
|
Details | Diff | Splinter Review |
When I fixed bug 288789 by changing the semantics of
nsFrameList::GetPrev[Next]VisualFor(), I neglected to change the case where the
parent frame is not a block frame (i.e. it's an inline frame). This has no
effect on textareas (which can't contain inlines), but it does break HTML
editing, keyboard-selection, and caret navigation when bidirectional text is
contained within an inline element.
I'll attach a testcase and a patch soon.
Assignee | ||
Comment 1•19 years ago
|
||
In Composer, or Caret Browsing mode:
In the upper paragraph, try moving the caret in and out of the numbers (in the
1st and 3rd lines). Notice that the caret moves to all kinds of unexpected
places.
The lower paragraph (which is idetical except it is not wrapping a <span>)
works correctly.
Assignee: mozilla → uriber
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•19 years ago
|
||
In the case where the parent is not a block frame, use the direction-aware
nsFrameOrigin (with a dummy value of "0" for the line number), instead of just
comparing the x coordinates (disregarding direction).
Simon - do you think you can review this soon so we will have some sort of
chance of getting this into 1.8? (I'm not too optimistic, but let's try).
Attachment #200233 -
Flags: review?(smontagu)
Comment 3•19 years ago
|
||
Comment on attachment 200233 [details] [diff] [review]
patch
r=smontagu
Attachment #200233 -
Flags: review?(smontagu) → review+
Assignee | ||
Comment 4•19 years ago
|
||
Comment on attachment 200233 [details] [diff] [review]
patch
Thanks, Simon!
ROC - same request here. This is a regression, and I'd really like to try and
slip the fix into 1.5.
Attachment #200233 -
Flags: superreview?(roc)
Comment on attachment 200233 [details] [diff] [review]
patch
looks good ... it's pretty clear that nothing has changed for LTR too
Attachment #200233 -
Flags: superreview?(roc) → superreview+
Assignee | ||
Comment 6•19 years ago
|
||
Comment on attachment 200233 [details] [diff] [review]
patch
Asking for last-minute approval1.8rc1. The changed code is only reached when
navigating in bidi HTML, so any risk is limited to that area (which is pretty
broken without this fix).
Attachment #200233 -
Flags: approval1.8rc1?
Assignee | ||
Updated•19 years ago
|
Flags: blocking1.8rc1?
Updated•19 years ago
|
Attachment #200233 -
Flags: approval1.8rc1? → approval1.8rc1+
Comment 7•19 years ago
|
||
not going to flag this as a blocker but if it lands before the freeze, then it's
in :-)
Flags: blocking1.8rc1? → blocking1.8rc1-
Assignee | ||
Comment 8•19 years ago
|
||
Checked in by timeless to both trunk and branch, 2005-10-21, 13:06.
Assignee | ||
Updated•19 years ago
|
Target Milestone: --- → mozilla1.8rc1
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: zach → layout.fonts-and-text
You need to log in
before you can comment on or make changes to this bug.
Description
•