Closed
Bug 1245755
Opened 8 years ago
Closed 8 years ago
Composition string is rendered on wrong position on google docs
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(firefox47 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox47 | --- | affected |
People
(Reporter: m_kato, Assigned: m_kato)
Details
Attachments
(2 files)
Firefox screenshot
- Step 1. Open https://docs.google.com/ 2. Input aaa 3. Input あああ using IME (don't commit this) - Result Composition string (あああ) is wrong position. When omitted this, it rendered correctly. - Notes This works fine on Chrome. - Detail Google docs generates HTML for Firefox <iframe class="docs-texteventtarget-iframe"> ... <html><body role="presentaion"><div style="margin-top: 0x; ..." contentedtiable="true"> IME Composing text... </div></body></html>... But, for chrome <iframe class="docs-texteventtarget-iframe"> ... <html><body style="margin-top 0px; ..." ... contentedtiable="true"> IME Composing text... </body></html> So since <body> element into <iframe> has no margin setting (default is 8px), composing text's position will be wrong.
|
Assignee | |
Comment 1•8 years ago
|
||
|
|
Assignee | |
Comment 2•8 years ago
|
||
Reported to Google. This will be fixed within a couple of weeks...
Assignee: nobody → m_kato
|
|
Assignee | |
Comment 3•8 years ago
|
||
Works find. Thanks, google!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
||
Updated•5 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•