Skip to main content

47 posts tagged with "❤️ Improved"

Changes that improved upon existing functionality

View All Tags

Client API v1.3.0

  • Changes for the upcoming change in Chrome's REFERER Header. It's now possible to set your own referer value by using the referer param in the PostMessages api call.
  • PostDevices now returns a warning when the account, for which this devices get's registered, has no or not working push settings.
  • We now return an error when the API has no connection to the Database. Before we only showed a white screen without any information on it.
  • We now support CIDR ip ranges and ipv6 in the IP restriction configuration
  • Added the following security headers
    • X-XSS-Protection: 1; mode=block Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.
    • X-Content-Type-Options: nosniff Prevents MIME-sniffing
    • X-Frame-Options: SAMEORIGIN The page can only be displayed in a frame on the same origin as the page itself
  • Added the no_access error to the documentation
  • Added the api base url to the documentation

Web library v1.2.16

danger

There is an issue in this version which prevents IE 11 to load the chat. This is fixed in v1.2.17

Added

Improved

Fixed

  • Fixed color contrasts of elements to conform to the WCAG level AAA guidelines
  • Fixed problem where some HTML elements had the same ID

Deprecated

  • The sendInitialMessage function since it is now replaced by the sendMessage which is an identical replacement

Web library v1.2.14

  • Added a core-js-builder that lets us make custom core-js builds (this way we minimize the amount of Polyfills that are
  • bundled with the chat files and thus minimize the chances for conflicting Polyfills)

Web library v1.2.13

  • Added custom proxy for converting Maps to proxies
  • Turned the events object into a Map so it also works on IE11 (the proxy-polyfill for IE seals the objects when creating a Proxy, so we couldn't add any events to the events object. To fix this we made a Map instead of Object for the events)
  • Added core-js polyfills mainly for the Reflect polyfill which is used for the custom proxies for Map objects