Howdy,
Just now, this happened: The quick-reply buttons do no disappear after a visitor clicks on one of them. This behavior is new, please fix this. See below.
Thank you!
2 Likes
Confirmed. Same issue happening with your AI Chatbot live demo.
What’s going on, Team Elfsight?
Cheerio! 
1 Like
Hi there, @Petar_Dietrich 
Thank you so much for bringing this to our attention!
I’ve shared the wrong assistant of our AI assistant and they’ll adjust this info on the knowledge base.
Regarding the quick replies issue, everything is working fine on my end now:
Could you please check it once again? If the issue still persists, please try to check it in incognito mode 
1 Like
Hey @Max,
Thank you. It’s working now. However, another issue now popped up (not sure if a result of the above fix): The CSS rules for styling hyperlinks stopped working.
I updated this post to maintain topic continuity. Can you please look into that as well?
Cheerio!
Hey @Max,
Another update: Just learned many of our CSS rules (in our configurator) no longer work – perhaps the result of an internal update made by your developers.
For example, the CSS rule below (I’ve been using it for months), no longer works.
Can you investigate this as well?
Thank you!
[class*="widget-window__QuickRepliesContainer-sc"]>button {
max-width: unset;
}
So, I queried the Quick-Reply buttons inside the chatbot and, indeed, it appears your developers changed the chatbots code. This is what’s working for me now:
/* Quick-Reply Button Styling Test (Button Width) */
[class*="quick-reply-button__Button-sc"] {
max-width: unset;
}
or
/* Quick-Reply Button Styling Test */
[class*="chat-content__QuickRepliesContainer-sc"]>button {
max-width: unset;
}
1 Like
I am so sorry about this inconvenience!
It seems that classes of some elements have been changed, this is why some codes stopped working.
I am happy to see that you’ve found the correct class for the Quick Replies and your code works great.
As for the link color, here is an updated CSS code (I’ve also updated it in the CSS Codes post):
[class*="floating-panel__Container-sc"] a {
color: red; // Link color
}
[class*="floating-panel__Container-sc"] a:hover {
color: red; // Link color on hover
}
[class*="floating-panel__Container-sc"] a:active {
color: red; // Link color when clicked
}
[class*="floating-panel__Container-sc] a:visited {
color: red; // Link color once visited
}
Please try it out and let me know if it helped
If you notice any other codes that stopped working, please let me know. I’ll be happy to look into this!
1 Like
Hey @Max,
Thank you. As always, ready to help. However, the fact that your developers changed the CSS selectors without notifying customers, you, etc. is not acceptable.
What are Elfsight’s plans to prevent this from happening again?
Cheerio!
I completely understand how you feel, and I’m really sorry about this situation 
Here’s the thing: stable classes (starting with .es) remain unchanged. However, some widget elements use temporary or combined classes that may change after updates.
When we update element classes, we usually migrate all widgets with customizations that include old classes to the new version, so customizations don’t break. Unfortunately, this time the migration was missed, which caused the issue. But everything is fixed now.
I hope this clears things up.
Also, I’ve updated the code for changing the link color with the stable class. Feel free to use this instead:
.es-window-container {
color: red; // Link color
}
.es-window-container a:hover {
color: red; // Link color on hover
}
.es-window-container a:active {
color: red; // Link color when clicked
}
.es-window-container a:visited {
color: red; // Link color once visited
}