Robin S Posted October 1, 2015 Posted October 1, 2015 I'm experiencing a weird bug with CKEditor that seems to occur when a neighbouring field in the same row is taller than the CKEditor field. Firefox: when typing the cursor jumps to the start of the CKEditor text area with every keypress. IE: when typing the text appears below the CKEditor window. Chrome: the bug does not occur. The screenshots below show the result of typing the second line "How now brown cow?"... All browsers, neighbouring field shorter than CKEditor field (no bug) Firefox, neighbouring field taller than CKEditor field IE v11, neighbouring field taller than CKEditor field If someone can confirm they get the same bug I'll file an issue on Github. Thanks.
Mike Rockett Posted October 1, 2015 Posted October 1, 2015 Whoa. That's the strangest thing I have ever seen. Just wow. Can't test here at the moment, but will try have a look later. Quick question: Does this happen in the current stable? (PS: You've made me drink a brown cow now.)
Robin S Posted October 1, 2015 Author Posted October 1, 2015 Quick question: Does this happen in the current stable? Just tried the current stable and can't replicate the bug.
mr-fan Posted October 1, 2015 Posted October 1, 2015 I can confirm this since 2.6.13 up to 2.6.18 https://processwire.com/talk/topic/10713-field-dependency-switches-uninvolved-ckeditor-field-into-rtl-mode/ You've tracked down the real issue on this - in the other topic we don't get why this happens... i'm working often with two column layout for the fields...and don't get the problem like you. Can you check if inline mode works? This was the result as a workaround since nobody else answers and seems to have that problem. regards mr-fan
Robin S Posted October 1, 2015 Author Posted October 1, 2015 Can you check if inline mode works? Setting the CKEditor field to inline mode does fix the bug. I think I have traced the bug back to these lines of JS code, which attempts to match the height of adjacent columns with every change (e.g. keypress) to the CKEditor field. Will open a Github issue for this. 1
mr-fan Posted October 1, 2015 Posted October 1, 2015 Great thank you for this closer look on this issue! I don't get it and used the inline workaround on this... Best regards mr-fan
Robin S Posted October 1, 2015 Author Posted October 1, 2015 Github issue is here for those interested, along with a suggestion for an alternative approach to making the input form pretty. 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now