Wrong position of input frame when typing in Electron/Chromium based program with a HiDPi screen
Reported by
lelouchs...@gmail.com,
Oct 12
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/69.0.3497.81 Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: Please fill in the following items if you don't know the root cause. Which distribution and version?: (E.g. Fedora 27. Check /etc/fedora-release) Arch Linux Which desktop environment and version?: (E.g. GNOME 3.24. Check $XDG_CURRENT_DESKTOP and your ISO image.) GNOME 3.26 Which session type?: (X11 or Wayland. Check $XDG_SESSION_TYPE) Wayland Which application and version?: (E.g. gedit 3.24, leafpad, kate, xterm) Atom Chrome All Electron(Chromium) based program. IBus version?: (Run ibus version) IBus 1.5.17 Issue description: IBus got a wrong position in Electron or Chrome programs, I have a 4K screen with 200% scale, it always shows Chinese frame out of screen bottom, and I cannot see what character in the frame. Steps to reproduce: Run Chrome with a hidpi screen. Use ibus-rime Chinese (I think it's not a rime specific issue but I am using RIME) Type. Can you reproduce your problem when you restart ibus-daemon? (yes / no): (Run ibus exit and ibus-daemon --xim &) yes Do you see any errors when you run ibus-daemon with the verbose option?: (Run ibus-daemon --xim --verbose & and look at the output when you encounter your problem.) no Can you reproduce your problem with a new user account instead of the current your account? (yes / no): yes What is the expected behavior? with correct position of input frame when typing in Chromium based program with a HiDPi screen. What went wrong? IBus got a wrong position in Electron or Chrome programs, I have a 4K screen with 200% scale, it always shows Chinese frame out of screen bottom, and I cannot see what character in the frame. Did this work before? N/A Chrome version: 69.0.3497.81 Channel: stable OS Version: Ubuntu 18.04 Flash Version: None
,
Oct 12
,
Oct 14
,
Oct 16
Thanks for filing the issue! @Reporter: Could you try to check this issue on latest beta# 70.0.3538.54 and let us know if the issue still persists. You can download latest chrome beta from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Oct 16
It not persists in latest chrome beta. https://www.google.com/chrome/dev/?platform=linux
,
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 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!
,
Oct 17
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by lelouchs...@gmail.com
, Oct 12