Ibus Candidate window appear at wrong location in Chrome with scaling-factor
Reported by
karlsuns...@gmail.com,
Sep 27
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open chrome 2. use Ibus input 3. type in anywhere I can type What is the expected behavior? Candidate window appear at right under input What went wrong? Candidate window appear at wrong location, usually in lower right part of screen Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: ArchLinux Flash Version: see https://github.com/ibus/ibus/issues/2039#issuecomment-424954191
,
Oct 16
Tried testing the issue on chrome reported version# 69.0.3497.100 using Ubuntu 14.04 with steps mentioned below: 1) Launched chrome reported version and selected 'Unikey' from the input source(right top of the screen) 2) Opened New Tab Page, right below to the omnibar seen suggestion box, from suggestion box selected the option to type 3) Entered the text in the omnibar, seen text got entered @Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, provided your feedback on it which help in further triaging it, if possible provide the screencast of the issue which help in better understanding. Thanks!
,
Oct 16
I am using Gnome and set org.gnome.desktop.interface scaling-factor to 2, this seems essential to trigger this bug Anyhow, this is fixed in chrome 70
,
Oct 16
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 16
If you check my attachment you will find that the candidate window is far away from the input box. Only encounter this issue when you set the scale factor to 2 in HiDPI screens. But the Google Chrome Beta(70) has no such issue. When the chrome 70 stable is release, please close this issue.
,
Oct 17
As per comment# 5 from the reporter, closing the issue and marking it as Won't fix. Note: Feel free to raise a new one if the issue is seen again. Thanks! |
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Sep 27