Closed
Bug 548792
Opened 16 years ago
Closed 16 years ago
Selecting text in large IFRAME does not cause window to scroll
Categories
(Core :: Web Painting, defect, P2)
Core
Web Painting
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | final+ |
People
(Reporter: bugzilla, Assigned: roc)
References
Details
Attachments
(3 files)
|
5.08 KB,
text/html
|
Details | |
|
3.56 KB,
patch
|
MatsPalmgren_bugz
:
review+
|
Details | Diff | Splinter Review |
|
977 bytes,
patch
|
MatsPalmgren_bugz
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a2pre) Gecko/20100225 Minefield/3.7a2pre (.NET CLR 3.5.30729)
Build Identifier:
See attached testcase. When trying to select all the text in the IFRAME, the window does not scroll to allow the offscreen text to be selected. This is a regression from Firefox 3.6.
Reproducible: Always
Steps to Reproduce:
1. Have IFRAME that is larger than the window.
2. Start a selection in the iframe
3. Move mouse to bottom of screen/window
Actual Results:
The window does not scroll.
Expected Results:
The window scrolls to allow more text to be selected.
| Reporter | ||
Comment 1•16 years ago
|
||
Comment 2•16 years ago
|
||
Regression range:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=120667a01fd2&tochange=a43e2f7eda8f
Looks like a regression from bug 526394.
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Component: Selection → Layout: View Rendering
Ever confirmed: true
QA Contact: selection → layout.view-rendering
| Assignee | ||
Updated•16 years ago
|
Assignee: nobody → roc
| Assignee | ||
Comment 3•16 years ago
|
||
Attachment #429454 -
Flags: review?(matspal)
| Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs review]
Comment 4•16 years ago
|
||
Comment on attachment 429454 [details] [diff] [review]
fix
r=mats
Attachment #429454 -
Flags: review?(matspal) → review+
Updated•16 years ago
|
Whiteboard: [needs review]
| Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs landing]
| Assignee | ||
Comment 5•16 years ago
|
||
Checked in, but backed out because it caused the accessibility test test_caretmove.html to fail on Linux and Windows, e.g.:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1269829304.1269831497.30384.gz
Whiteboard: [needs landing]
| Assignee | ||
Comment 6•16 years ago
|
||
That bustage was revealing a real bug in existing code. We're updating the rect incorrectly.
Attachment #435557 -
Flags: review?(matspal)
| Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs review]
Updated•16 years ago
|
Attachment #435557 -
Flags: review?(matspal) → review+
Comment 7•16 years ago
|
||
Comment on attachment 435557 [details] [diff] [review]
additional fix
r=mats
Updated•16 years ago
|
OS: Windows XP → All
Hardware: x86 → All
Whiteboard: [needs review]
| Assignee | ||
Updated•16 years ago
|
Whiteboard: [needs landing]
Comment 8•16 years ago
|
||
Is there a followup bug for doing the same for ScrollSelectionIntoView (specifically for the typeahead find selection)?
| Assignee | ||
Comment 9•16 years ago
|
||
Since bug 526394, ScrollSelectionIntoView uses nsIPresShell::ScrollFrameRectIntoView, which we're fixing here.
Comment 11•16 years ago
|
||
Comment on attachment 429454 [details] [diff] [review]
fix
> rect += container->GetPosition();
>- container = container->GetParent();
>+ container = nsLayoutUtils::GetCrossDocParentFrame(container);
Do we not want to use the second argument of GetCrossDocParentFrame here to include the cross doc offset?
| Assignee | ||
Comment 12•16 years ago
|
||
Yes we do, good catch!
| Assignee | ||
Updated•16 years ago
|
blocking2.0: ? → final+
Priority: -- → P2
| Assignee | ||
Comment 13•16 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/6549437223c3
http://hg.mozilla.org/mozilla-central/rev/4b48094881e1
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [needs landing]
Updated•8 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•