Module conflicts with MaxLength

Thanks for the report - I'm trying to replicate the issue and am seeing things inconsistent with the issue you've described. It seems like the <div class="counter">Used chars: 23</div> node is in a different place in your document. Immediately following the textarea, I have a div with the ck ck-reset ck-editor ck-rounded-corners classes. That's the one that should be targeted and changed.

I'm using:

• Core v10.1.6
• Gin admin theme v8.x-3.0-rc7
• maxlength v2.1.2
• CKEditor5 Fullscreen v1.0.0-beta5

I wonder if the id is inadvertently getting clobbered somehow? Which points to an issue - the module should use data attributes instead of ids (and the Dom traversal may have to be addressed). I think the move to data-attributes is a change that should be made regardless.

Happy to look into this further if you can provide more details

Thanks for the answer. I was testing on:

• Drupal 9.5.11
• Gin 8.x-1.0-rc4
• maxlength v2.1.2
• CKEditor5 Fullscreen v1.0.0-beta5

I've noticed some time ago, weird behaviour of maxlength. The counter is, as you described, right below the textarea when I'm creating new node. And fullscreen button works fine. However, when I save node and edit it again, the counter from maxlength is above the textarea and at this moment, fullscreen button is not working anymore.

I'm not sure why maxlength div is displayed in two different places, but I hope this description would help you to verify if this conflict should be resolved in CKEditor5 Fullscreen module?

Thanks!

@besek, I've made a new release of the module that uses data attributes instead of ids (so it should be less fragile). Are you able to try this and see if that changes things? I can test as well, but I'd like to make sure I'm not missing anything present in your use case.

@occupant, thanks, I've tested it and it really looks like it if working well now. Thank you!