v2.0.0-beta.19

Fixed:

• Fixed an issue where using ChatBotProvider for hooks will cause infinite re-renders
• Fixed an issue where audio service will read out html tags
• Fixed an issue where sendOutput field is being ignored for options and checkboxes attributes
• Fixed an issue where tooltip had a much lower z-index than chat window, causing it to be partially hidden
• Fixed an issue with the useToasts hook not being imported correctly
• Fixed an issue where chatbot button svg icon was not rendered correctly on mobile devices

Added:

• Added a new updateSettings utility function to the useSettings hook (refer to documentation for details)
• Added a new updateStyles utility function to the useStyles hook (refer to documentation for details)

v2.0.0-beta.18

Fixed:

• Excluded comments from theme css files parsing
• Fixed an issue where icon was not rendered correctly in footer

v2.0.0-beta.17

Fixed:

• Fixed improper parsing of css files in themes
• Fixed toast animation not working

Added:

• Updated button with svgs from: https://fonts.google.com/
• Added disabled icon support for all buttons (now possible to have different icons for enabled/disabled state)
• Added svg component support for button icons (conveniently use the fill attribute to recolor icons!)
• Added a new sendIconDisabledStyle
• Loading of chat history no longer locks the text area
• Standardized keyframe naming conventions

v2.0.0-beta.16

Fixed:

• Fixed an issue where themes may not load properly
• Buttons now properly inherit base styles even in different states (e.g. disabled, hovered)

v2.0.0-beta.15

Fixed:

• Fixed an issue where having settings.chatHistory.autoLoad: true will cause the chat history to disappear
• Fixed an issue where loading of chat history may cause previously disabled text area to become enabled
• Renamed id inside event.detail to botId for better clarity

Added:

• Added a new rcb-pre-load-chatbot event
• Added a new rcb-post-load-chatbot event
• Added a new useBotId hook

v2.0.0-beta.14

Fixed:

• Fixed an issue where having multiple chatbots can cause styling conflicts with themes
• Fixed an issue where removeMessage was not working due to outdated messages state
• Fixed an issue where defaultToggledOn property for voice did not properly register voice inputs
• Fixed an issue where settingdefaultOpen to true for chatWindow does not make it open by default
• Fixed an issue where toggling open the chat window does not emit its associated event
• Fixed a rare issue where spamming messages too fast can cause autoscroll to bottom to not work properly
• Fixed notification badge style to prevent it from becoming oval-shaped
• Fixed an issue with the library packaging process, reduces overall size by nearly 60%!
• Renamed useToast hook to useToasts for consistency

Added:

• Added proper support for React 19!
• Added a new ariaLabel section to improve accessibility support
• Added a new useChatHistory hook that provides 3 new actions (showChatHistory, getHistoryMessages and setHistoryMessages)
• Added a new sendButtonDisabledStyle (send button is now properly disabled when textarea is disabled as well)
• Improved localised styling of chatbots to reduce conflicts with host websites (and with other chatbots)

Note:
This update brings about a couple of fantastic improvements - drastically reduced library size (by nearly 60%), React 19 support, improved localised styles and better accessibility support!

v2.0.0-beta.13

Fixed:

• Fixed an issue where the toggle voice event was not properly triggered

Added:

• Improved support for ssr (users now no longer need to rely on dynamic imports as a workaround)

v2.0.0-beta.12

Fixed:

• Fixed an issue where toasts do not obey max limit
• Fixed an issue where toasts are not positioned properly
• Fixed an issue where notification sound does not play correctly in useNotifications

v2.0.0-beta.11

Added:

• Added a new useFlow hook that grants access to retrieving and restarting the conversation flows
• The hasFlowStarted boolean which was previously found in useFirstInteraction has been moved to useFlow for better consistency

Fixed:

• Fixed an issue where states were not updated in conversation flow

Note:

There have been confusions surrounding the use of ChatBotProvider such as what props it should be given if used. To reduce the mental load on developers, all props are now centralized to only ChatBot, regardless of whether you are using ChatBotProvider or not.

There is no functionality change and developers can now just remember that ChatBot is what accepts all props. With that said, if you're currently passing props to ChatBotProvider, move them all to ChatBot instead.

v2.0.0-beta.10

Fixed:

• Fixed an issue where chatbot view on mobile devices may not resize correctly
• Fixed an issue where uuids are not generated properly for non-https environments