[Mobile] Fix caret position after inline paste - Update.

[mkevins]

Note

This is an addendum to #14893 as "concurrent" changes in #14820 made the previous patch inert.

Specifically, the flag needsSelectionUpdate was moved from state to this so that it could be toggled false in the render method without triggering an additional render. More details here: https://github.com/WordPress/gutenberg/pull/14820/files#r274915836 .

Description

This PR fixes part of this issue: wordpress-mobile/gutenberg-mobile#828 , specifically, when inline content is pasted.

How has this been tested?

This has been tested using the steps here:
wordpress-mobile/gutenberg-mobile#828 (comment)

Screenshots

Types of changes

This is a bug fix, but currently only resolves a part of the original issue. It serves as an incremental improvement.

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.

[marecar3]

Hey @mkevins, nice fix here :)

I tried both on iOS and Android and it's working like expected.

I have found some issue, which I think isn't related to this PR and maybe we already have raised it.

On iOS, when you paste the content e.g. Hello World, Hello will lose bold style after the paste, however on Android that isn't a case, so I can assume that Android is working as expected and iOS not ?

[marecar3]

Note: @mkevins maybe it would be good to add Label: Component Mobile to this PR.

[mkevins]

Thank you @marecar3 . I've added [Component] Mobile label, and one for paste as well.

[mkevins]

I have found some issue, which I think isn't related to this PR and maybe we already have raised it.

On iOS, when you paste the content e.g. Hello World, Hello will lose bold style after the paste, however on Android that isn't a case, so I can assume that Android is working as expected and iOS not ?

I don't recall that one, but it could be. I don't yet have an iOS device to test on, but will soon. I wonder if it could be related to styles set on inline span tags. I remember a known issue about some loss of styles around that, so it could be related.