-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Everything writes in RTL after pressing Enter #1254
Comments
We need more details, I can't reproduce. |
@youknowriad I'm using Firefox on MacBook Pro 101, without any console errors. It's a MAMP setup, running PHP 7.0.12. |
@HardeepAsrani Are you using |
Nope, only enter. |
I'll try doing it on a live server to see what happens. |
Tested on a new MacBook Pro late-2016 in Firefox, and same happens. |
Enter works properly for me. I was having an issue with shift+Enter fixed by #1299. It'd be great if you can test again with master. |
Closing, I can't reproduce. Feel free to reopen if you still experience this but we'd need more information on how to do reproduce. |
Hey, sorry I was out at a WordCamp + busy organizing a WC in our city. So little busy. And yes, it's still open. @youknowriad Don't see an option to re-open. And yes, I tried it with the latest master and still happening. And we can try to do a live screen share when I can try reproducing it on FF on your Mac. What say? |
@youknowriad I'm also not able to reproduce. |
This bug looks a little like this one… maybe they are related ? |
@nicolinuxfr Yup, it's the same. :) |
I am unable to reproduce this. It makes me wonder if we're missing some steps. Until we get more steps, I am closing as without it we are chasing reproducing - we can always reopen. |
You can close it, the #1607 is still open so it's fine for me. :-) |
So I was trying test the Gutenberg and started to write to see how it is. And apparently if I write and press enter, everything stars writing RTL. So it appears that the typing cursor stays in the left. Here's a GIF attached:
Tried to search if it was reported before but couldn't find. Too many tickets. :)
The text was updated successfully, but these errors were encountered: