1.2.3

• fix: Allowing HTML in item descriptions (https://github.com/empreinte-digitale/orejime/issues/18)

1.2.2

• fix: import of nl translations (https://github.com/empreinte-digitale/orejime/pull/27)
• fix: hiding batch actions when all apps are required (https://github.com/empreinte-digitale/pull/issues/28)

1.2.1

• doc: capitalization of nationalities and languages (https://github.com/empreinte-digitale/orejime/issues/16)
• doc: improved example markup (attributes were missing from <script /> tags)
• translations: updates to nl translations
• internal: node-sass update

1.2.0

• new feature: Ability to customize cookie serialization (https://github.com/empreinte-digitale/orejime/issues/13)

1.1.1

nothing different from 1.1.0, this is just to make npm bypass a problem...

1.0.3

• add a few CSS rules to prevent collapsing with the website styles
• fix a couple JS errors on IE11 that occured after saving one time

1.0.2

• fix accessibility issue with Orejime not removing the app aria-hidden="true" at times
• replace default "powered by" url by the Orejime homepage

1.0.1

• add the version number in the built files
• tiny fix in modal text, remove a superfluous whitespace between description and privacy policy text

Orejime 1.0.0

The project now has moved a lot from the original one. The way the lib can be consumed and the way the lib is authored are noticeably different from Klaro!. For these reasons, we decided to give our fork its own name: Orejime :cookie:.

The main updates included in this version are:

• name change: all options with a default "klaro" value now have a default "orejime" value
• name change: README and demo have been totally revamped to match the changes between Klaro! and Orejime
• new feature: you can now configure Orejime to enable implicit consent via the implicitConsent config. Implicit consent means, if the user navigates on more than one page on your website, all the apps configured will be automatically accepted.
• new feature: if the user has saved his preferences and a new apps config is detected, the notice (or the modal, if mustConsent is set) should now appear again to let the user know of the changes.
• feature change: when toggling apps after the user already saved his preferences once: never save preference as soon as it is toggled (see https://github.com/KIProtect/klaro/issues/52).
• feature change: easier cookie deletion on app deactivation. When defining an app in your config file, now you shouldn't have to bother to describe the cookie domains anymore. Orejime should find them on its own (see https://github.com/KIProtect/klaro/issues/51).
• feature change: app toggle switchs: add a label below the switch to be 100% clear on the current state of the toggle
• feature change: the "toggle all" checkbox has been replaced by two distinct buttons, "enable all apps" and "disable all apps", for more clarity.
• feature change: if no element with the given elementID is in the DOM, it will now be inserted at the beginning of the body and not the end
• refactor: complete overhaul of the way the lib can be consumed. You can now consume Orejime via npm, with commonjs or es6 modules, in addition to the already existing umd build. More details in b868d7a.
• refactor: stop making a build with CSS included in the umd build. The css is now only available via its own css file.
• fix: better default CSS and JS behavior to prevent website scrolling when the modal is open.
• fix: support IE11 (assuming some polyfills are in the page)
• dev: use browser-sync as a dev server