Closed
Bug 791338
Opened 14 years ago
Closed 14 years ago
Firefox does not scroll screen to show cursor for contenteditable elements in iframe
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox18 verified)
VERIFIED
FIXED
Firefox 18
| Tracking | Status | |
|---|---|---|
| firefox18 | --- | verified |
People
(Reporter: radarxc, Assigned: kats)
References
()
Details
Attachments
(1 file, 1 obsolete file)
|
2.04 KB,
patch
|
cwiiis
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1
Steps to reproduce:
Go to http://www.tinymce.com/tryit/full.php
Click on the contenteditable element.
Actual results:
Android software keyboard covers up contenteditable element and the blinking text cursor.
Expected results:
The website is scrolled so that the blinking text cursor is visible within the lessened screen space, which is the same behavior that occurs for input box elements.
| Assignee | ||
Comment 1•14 years ago
|
||
What version of Firefox for Android are you seeing this on? It should have been fixed in bug 785520.
(In reply to Kartikaya Gupta (:kats) from comment #1)
> What version of Firefox for Android are you seeing this on? It should have
> been fixed in bug 785520.
Firefox 18 in Android(fennec-18)
Actually, I update the patch for bug 785520. However, it still does not work for the contenteditable elements in iframe.
If contenteditable in a iframe, the var focused will be an iframe rather than instance of HTMLTextarea or any other input tag instance. So maybe this is the problem.
Comment 3•14 years ago
|
||
Related to bug 793677?
Updated•14 years ago
|
Comment 4•14 years ago
|
||
I can reproduce with the aforementioned URL on Nightly (09/24).
| Assignee | ||
Comment 5•14 years ago
|
||
I can also reproduce this. I'll take a look once my build is done (i.e. probably tomorrow).
Assignee: nobody → bugmail.mozilla
OS: Windows 7 → Android
Hardware: x86_64 → All
| Assignee | ||
Comment 6•14 years ago
|
||
While trying to fix this I found a regression from bug 727352. Patch for the regression coming, and I have this bug almost working as well.
Blocks: 727352
| Assignee | ||
Comment 7•14 years ago
|
||
Attachment #664623 -
Flags: review?(blassey.bugs)
| Assignee | ||
Comment 8•14 years ago
|
||
Attachment #664634 -
Flags: review?(chrislord.net)
Comment 9•14 years ago
|
||
Comment on attachment 664634 [details] [diff] [review]
Part 2 - Do a better job of scrolling-into-view editable elements inside frames
Review of attachment 664634 [details] [diff] [review]:
-----------------------------------------------------------------
Looks alright to me - I'll trust your comment about the better UX :)
::: mobile/android/chrome/content/browser.js
@@ -985,5 @@
>
> // tell gecko to scroll the field into view. this will scroll any nested scrollable elements
> // as well as the browser's content window, and modify the scrollX and scrollY on the content window.
> focused.scrollIntoView(false);
> -
Any reason for getting rid of this blank line?
Attachment #664634 -
Flags: review?(chrislord.net) → review+
Updated•14 years ago
|
Attachment #664623 -
Flags: review?(blassey.bugs) → review+
| Assignee | ||
Comment 10•14 years ago
|
||
Comment on attachment 664623 [details] [diff] [review]
Part 1 - Fix regression from JSON conversion
I'm moving this first patch over to bug 793677 which specifically tracks the regression. Carrying the r+ over there too.
Attachment #664623 -
Attachment is obsolete: true
| Assignee | ||
Comment 11•14 years ago
|
||
(In reply to Chris Lord [:cwiiis] from comment #9)
>
> Any reason for getting rid of this blank line?
Whoops, accident. I put it back in and landed on inbound:
https://hg.mozilla.org/integration/mozilla-inbound/rev/e305a1b3a777
Comment 12•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
Target Milestone: --- → Firefox 18
Comment 13•14 years ago
|
||
Is Aurora affected here?
Status: RESOLVED → VERIFIED
status-firefox18:
--- → verified
| Assignee | ||
Comment 14•14 years ago
|
||
Yeah, I think all versions back to 14 will be affected. It's not a regression, just a bug we've had since initial implementation.
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•