[iOS] Autocapitalize does not work as expected

[Aashish]

Tried this against the nightly build.

Editor does not autocapitalize correctly upon pressing return (new line). For it to autocapitalize, one has to enter a dot (.) (i.e. close the previous sentence).

To Reproduce: Go to nightly build from iOS Safari (mobile Safari) Enter a word 'Hello' Tap on Return to go to a new line Type something. Text will not be capitalized.

[Jakub Ś]

Editor does not autocapitalize correctly upon pressing return (new line). For it to autocapitalize, one has to enter a dot (.) (i.e. close the previous sentence).

Are you sure this is editor fault? We don't provide, support or prevent such feature on iOS. I would rather assume that this is how it works. Could you recheck and let me know?

[Piotrek Koszuliński]

It's hard to say who's problem is this. Autocapitalising is iOS'es native feature and we cannot control it. Apparently, our custom handler for return key does not toggle that native feature. If that turns to be true, we'll have to report a ticket to Webkit team, but we can't do anything more.

[Aashish]

iOS default capitalization behavior does capitalize first letter after a newline (RETURN) key. Capitalization works if a period (.) is entered.

However, I did notice that the RETURN key is not firing the 'keydown' event. It does fire the 'keyup' event. This could be the issue.

I am not sure if its CKEDITOR or iOS.

It affects lists significantly since the hitting enter does not capitalize the next list item.

Is there some workaround? Maybe there is a way to convert the character entered after RETURN to uppercase but I could not find a way to get the current cursor position.

I've tried to insert an invisible period character (text color same as background, small font size). However, its not always successful after keyup and keydown is not getting detected. Plus, the next character at times inherits the dots style.

[Piotr Jasiun]

In fact text in the new line is not capitalized in the CKEditor and it is in the native contenteditable so I confirm this bug.