[2.x] Alternative layout, OR add ability for basic filtered text-HTML

Your design looks nice. But I'm sorry, the feature is too project specific.

But I could fix one point: It should be possible to integrate some basic html to the text area fields. So at least you can style headings and subtitles and spans (may be custom links with option for button classes).

If you are ok with that, we could change the ticket subject. But this task has potential for 1-2 days of work. (CKEditor integration, save filter solution for backend and frontend, ...) So, this could take some time.

If you like to share and contribute your design as alternative skin, we could talk about that.

Hi @vistree
I sent you a personal message for that.

Enabling filtered text in the modal would be great.

An option to add HTML tags to banner text would be great!

Are there any ohter options to add at least line breaks (<br/>) right now?

Imho such custumizations should go into a Twig template or a (JS) Drupa.theme function.

Added a MR that changes the cookie text configuration text-area into a full html field. It's draft, also needs implementation in the client-side lib I believe where HTML is being interpreted as text.

At the very least it would be useful to add "rich text" before the buttons, and an extra text-area after.

Back to NW, see my comment in GitLab.

Also we have to ensure this doesn't break anything for existing installations. Patch / MR should be against latest .dev version!

Tried to implement this one and faced the issue:
- cookiesjsr inserts markup as a plain text, and I could not find a way to pass anything to the library to be rendered as markup.

Like @gilmord, it's OK on the administration side, but on the public side, it's rendered as plain text.

Possible 2.x feature.

Hey ho, let's go! 2.x branch was recently created. Please help to implement this or if you're not a developer, please sponsor some development hours.

This feature is something that we would be interested as well, are there any updates on this?

Also interested!

FYI: The larger plan for 2.x is to replace the React client by a Vue client: https://github.com/jfeltkamp/cookiesjsr-vue for many reasons (also license and technical). I think that should be done first, combined with other refactorings.

Joachim started the implementation already, as you can see, but there's a lot of work to be done in this module and our small 3 person DROWL team is super busy for the next months. Joachim and we invested many development weeks into this module, so anyone who's interested in the future of the COOKiES module should consider helping or sponsoring to put this on more shoulders.

Thank you!

Hi,

While the new VUE-based JS library is not available, we have implemented a small JS script that renders any HTML that is embedded in the banner. It is a completely provisional solution, but it can help those of us who have this need get through it. I'm only contributing it in case someone finds it useful, but it's still minimally tested.

(function (Drupal, once) {

  'use strict';

  Drupal.behaviors.myCustomCookies = {
    attach(context, settings) {
      once('myCustomCookies', 'body', context).forEach(function (element) {
        const observer = new MutationObserver((mutations, obs) => {
          const cookiesBannerText = document.getElementsByClassName('cookiesjsr-banner--text');
          if (cookiesBannerText[0]) {
            const parser = new DOMParser();
            const textarea = document.createElement('textarea');
            textarea.innerHTML = cookiesBannerText[0].innerHTML;
            const cookiesBannerHTML = parser.parseFromString(textarea.value, 'text/html');
            cookiesBannerText[0].innerHTML = cookiesBannerHTML.firstChild.innerHTML;
            obs.disconnect();
          }
        });
        observer.observe(document.body, { attributes: true, childList: true, subtree: true });
      });
    },
  };

}(Drupal, once));

In addition to this, it would be necessary to define the library and load it with the component.

Thanks!

Will be fixed in version 2.x.

@jfeltkamp is this already fixed? Could you give us an update on the status or plan? Should this be a blocker for stable 2.0.0?

From the side of the JS-library it is fixed.
But now I want to add HTML editors for the fields in the Drupal config forms, so that this would work out of the box.

Nice, thank you @jfeltkamp! :) Looking forward to that! Should you need assistance, feel free to ping us.