New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unwanted first character using IME API #4662
Comments
This #4661 issue is the same as this but with different behavior on Safari. |
preparation (due to the cursor overlapping on IE). #4662
The issue is rescheduled to February. Tasks to be finished/fixed:
|
any new update? |
Hi @ruzia there are still a few bugs that we need to finish before we will be able to get back to this project. I do not know if we will be able to do in in February (as predicted before) but we will do our best to try. |
Fix unwanted first character on FF. Enabled the Copy/Paste functionality, now IME works with copying, pasting and cutting. Issue: #4662
* Fixed eslint error and added hiding an editable element on every editor preparation; * Add missing tests and remove commented code; * Add more tests which check focus state after cell selection; * Update TS definition file. Issue: #4662
The IME was merged into develop branch. The editor is not compatible with |
Additionally, there is some visual bug which occurs only on Edge browser. When we try to compose the word the first character is not visible in the input element but psychically it is there so it does not disturb later composition. After inputting the second character and so on, the whole text becomes visible. This will be fixed as a separate issue. |
Hi @ruzia please update to 4.0.0. The issue has been solved in this version. |
thanks for reply! |
Description
The unwanted first character appears in the editor when IME API is used.
Steps to reproduce
Task 33
(cell A1) and switch cell into editing mode (press enter);In result, the editor should contain only Chinese symbols. Instead, the first character is visible as English character.
Your environment
The text was updated successfully, but these errors were encountered: