D
Deleted member 1
Guest
I'm aware of this behavior. It just showed up with the latest update for Gboard and chrome. Working on a fix asap.
M
member 3289
Guest
Might be my Samsung keyboard, but when I try to initiate a search, it won't let me type unless i scroll to the top of whatever page I'm on. If I try to search midway down or wherever, my keyboard disappears when I start typing, almost like it thinks I'm trying to execute an on-screen command.
Not sure if this is making any sense. I'm usually good at describing things
Not sure if this is making any sense. I'm usually good at describing things
M
member 3289
Guest
Doing it with the Samsung keyboard as well. Also happens when pressing backspace. Driving me nuts
D
Deleted member 1
Guest
yes I am aware
its a flaw with their update and the built in text box control. I can't control either of those things.
Work arounds include using firefox in the meantime.
I will be updating our site ASAP when the software maker or chrome gives us a fix
D
Deleted member 1
Guest
Have identified a low level error in the newest version of chrome. this is not our site specific but is related to the way chrome handles some web standards. Since it's the browser managing web standards wrong I would blame the browser. Waiting on an update.
Just as an FYI, pressing backspace does it too.
D
Deleted member 1
Guest
Current work around include using a browser other than chrome or toggling OFF the rich text editor until we get a fix
click that gear to turn it on and off. turning off lets you type but no more formatting and extras.
Fix asap but google likely owes a new chrome version.
click that gear to turn it on and off. turning off lets you type but no more formatting and extras.
Fix asap but google likely owes a new chrome version.
D
Deleted member 1
Guest
Chrome error confirmed and expected fixed next week
to them.
Comment 33 by benmason@chromium.org on Thu, Sep 3, 2020, 5:33 AM CDT (2 hours ago) Project Member
Labels: -Hotlist-Merge-Approved
Taking this merge to M85 now, will be included in re-spin next week.
You fixed it @Splinty !