You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported on AMO, #105 recently regressed, probably due to a change Facebook made. Submitting any text field on a profile page or chat box strips the text of any diacritics entered since the last plain character.
This issue does not reproduce with system input methods in Firefox on OS X; however, Firefox gets very confused about where the keyboard focus is, suggesting that Facebook is doing something unusual with the textbox.
Facebook also strips the diacritics as soon as you focus some other element on the page then refocus the textbox, or as soon as you switch tabs or windows and back.
At this point, the most likely culprit is that the React component that manages the contenteditable box (react-composer) is overwriting the box’s contents with the value of a property in the component’s model.
<ComposerStatusAttachmentMentionsInputWithTagExpansionContainer>
<ComposerStatusAttachmentMentionsInputContainer>
<ReactComposerStatusAttachmentMentionsInput>
<MentionsInput>
div
<AbstractMentionsTextEditor>
div
<n>
AVIM once again works in Facebook and Messenger as of v5.7.0b2, which is in the beta channel. Barring complications, I’ll publish to the release channel in a few days.
AVIM lại tương thích với Facebook và Messenger trong phiên bản 5.7.0b2, phiên bản đó trong kênh beta. Nếu không có sao, tôi sẽ xuất bản cho kênh chính trong vòng vài ngày.
As reported on AMO, #105 recently regressed, probably due to a change Facebook made. Submitting any text field on a profile page or chat box strips the text of any diacritics entered since the last plain character.
This issue does not reproduce with system input methods in Firefox on OS X; however, Firefox gets very confused about where the keyboard focus is, suggesting that Facebook is doing something unusual with the textbox.
Possibly related to kimkha/avim-chrome#18.
The text was updated successfully, but these errors were encountered: