-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
LinearLayout with EmojEditText sometimes disappearing when popup is shown (in fragment) #28
Comments
What's your I don't know if |
Can you try |
Using getView() method now, which gives me the root view for the fragment. At least know now how to reproduce the bug: |
Just did a little debugging with your code, seems the problem is that isKeyboardOpen is true AFTER soft keyboard has been closed. This is why showAtBottom() is called when it shouldn't. |
Which version are you using? |
compile 'com.vanniktech:emoji:0.3.0' |
Can you quickly check version |
Just tried version 0.1.0 and it seems to work there. All keyboard close events are detected properly here. |
Then I guess this commit is causing the issue. The reason I changed it back there was because some of the listeners were not called at the right moment. |
@anti-gone any other information / clues on how to fix it? |
I'm closing this issue due to inactivity. If you have any further input on the issue, don't hesitate to reopen this issue or post a new one. |
I have a fragment containing several linear layouts with on linear layout at the bottom containing the EmojEditText and some buttons. I use the button to toggle the EmojPopup visibility.
Sometimes (let's say one in 10 times or 15 times) the emoj popup opens but the linear layout above it just disappears when I click the button. If I choose an emoj the popup disappears and the linear layout is visible again.
I cannot trigger this on purpose, seems like a race condition of some kind? Could it be related to wrong root view? I'm using view.getRootView() (view is the inflated view for the fragment).
The text was updated successfully, but these errors were encountered: