Placeholder text only shows when the page first loads

[zoaked]

Description:
The placeholder text in select mode is disappearing after interacting with tagify

Analysis:
There is CSS applied to the input that sets the placeholder opacity to 1 using the :empty psudo selector. When that selector does not match the default styling sets the opacity to 0. When the page first loads the placeholder text is shown. Selecting a tag and then removing it hides the placeholder text because a <br> child is left behind. This tag is not shown as CSS has set it's display to none. Since it is there at all the parent element is technically not empty and so the override styles no longer apply.

This did not occur in 4.7.2 - it only started with 4.8.0 so something in one of these commits is adding that extra br tag.

Demo:
Previous version working
Latest version not working

[yairEO]

I will fix it promptly (next few days)

[gugiserman]

@yairEO I see you pushed a release related to this issue and closed it but I'm on v4.8.1 using mixed mode (textarea, vanilla) and still having a similar problem, just to let you know 😶

When I manually erase all text content (either by selecting all and hitting backspace or just hitting backspace character by character until empty), placeholder is not restored (stays empty forever) and I get this error in console:

tagify.min.js:8 Uncaught TypeError: Cannot read properties of null (reading 'nodeType')
    at b.onKeydown (tagify.min.js:8)

---

Update: I just tried v4.7.2 as mentioned in this issue original report and it works! So I think it's same to assume the bug is not fixed entirely. I won't have time today to check it out or make a demo project, sorry 😞

[yairEO]

You opened the issue for select-mode, so that commit closed that issue. Now there is another issue, with mix-mode.
That is another thing :) You should have been more accurate when detailing the bug, I only debugged this in select-mode and did not even bothered checking mix, since I thought you need this urgently for select

I will work on a fix for mix-mode

[gugiserman]

You opened the issue for select-mode, so that commit closed that issue. Now there is another issue, with mix-mode.
That is another thing :) You should have been more accurate when detailing the bug, I only debugged this in select-mode and did not even bothered checking mix, since I thought you need this urgently for select

I will work on a fix for mix-mode

I'm not the author of the issue 😆 Sorry, I should've opened a new issue, I didn't understand his issue was specifically for select mode.

Thanks for the quick reply and for the awesome library by the way! Absolutely life saver!

[zoaked]

Thanks for jumping on this report! There seems to be a bit of confusion as I do not use mix mode so only observed the issue in select mode. Someone else jumped in afterwards to expand the issue report as happening in other modes. (mix) That is why it was not detailed in the original bug. Thank you again for all your efforts in maintaining this library.

[yairEO]

Thank you both for the nice words :)