I also created a new issue for the Svelte library to reduce the banner size.
https://github.com/jfeltkamp/cookiesjsr/issues/38
This will also help to let the banner not be the largest content element.
We found out, that async breaks the COOKiES UI display.
Let us try a shorter text for the banner.
"Please agree to the use of cookies on this website, which serve to collect personal data and pass it on to third-party service partners. You can revoke your consent at any time under "Cookie settings"."
[2.x 29b110f] Issue #3493869: Added documentation to config fields privacyUri and imprintUri how to achieve target="_blank" and rel="noopener nofollow" to links.
Based on the changes in the JS library cookiesjsr I documented in the form fields how link attribution behaves based on the given URI.
See: https://github.com/jfeltkamp/cookiesjsr/issues/23
anybody → credited jfeltkamp → .
anybody → credited jfeltkamp → .
Hey @sourojeetpaul, I'm here :-)
The missing buttons in mobile layouts are technically and legally not required, but general shortcuts for "configure all/none + save".
The reason why the buttons are missing is the missing space for button labels.
In English everything looks fine, but if you translate the plugin to German, then:
Save | Deny all | Accept all
Speichern | Alle ablehnen | Alle akzeptieren
This will break the layout.
If you have a good solution for that problem I would be pleased.
@Anybody: I respect but don't understand the idea and intention, why to use HTMX here. That would be a very major overhaul of the entire system. HTMX intends to generate the entire markup in the backend and is not supporting APIs. Then we will need additional Javascript to map the frontend dynamics, instead of (as it is now with Vue or React) directly controlling its own markup and event management as a really autonomous frontend component with the full service. Instead of Vue you would then have HTMX as a dependency, which means no independence is gained. - My opinion to that: I don't think this is the right way. I don't agree.
Because I think, that HTMX is NOT an innovative concept, and has some really ugly pitfals in consequence: I would also recommend this article by heise online: https://www.heise.de/blog/HTMX-Die-perfekte-UI-Technologie-9633960.html
But I'm still open for arguments: What exactly are the problematic Issues? Why do you think HTMX is a good idea? Or maybe I would be convinced by a prototype that shows that all concepts can be implemented well.
I will add a video, how to use the tool. Sorry, that I couldn't make that clear. But I think it will take 10 days I have time for that.
Okay, I changed the first sentence in the introduction. Please have a look if this is sufficient.
D10 patch applied and tested
Don't understand explanation of asked changes.
applied patch
Available >= 1.0.0-beta1
As marco.b said: This module supports form modes for existing entity base routes as 'add' or 'edit_form'.
Fixed issue. (Thanks to IzabelaTina)
To have no duplicated code I extended the if clause.
Available >= 2.0.2
Patch applied.
Available >= 2.0.1
Patch applied.
Available >= 2.0.1
Thank you for the offer, but I think a new maintainer is not required.
If you want to add changes, you can offer a MR.
Update to D10 will be done today.
Merged patch. (Thanks to @dineshkumarbollu)
Available >= 8.x-1.6
Yes OK I understand. You are absolutly right, that it is a problem that I'm th only maintainer.
So I will give you full access to all repos on GitHub.
> Could we open-source the vue code directly in the module instead of a separate repository?
My idea was, to left the JS library an independent tool, that can be used with any type of backend, not just Drupal.
Why do you think, this step could make sense.
Hello Kostia, very pleased to see this. Thank you for sharing this with us. I just took a very brief look at the module. Congrats!! This can be a nice extension for the COOKiES ecosystem. I will review the module at the next opportunity.
Already added the last missing permission: "Administer maintainers" for Julian.
Is that correct?
Hello @apderno and @Anybody,
Oh, I'm so sorry for not answering my emails.
Sure, I definitely agree that "Anybody" (aka) becomes maintainer with full access to all resources.
I still love the project but don't have the time to devote to it at all and I'm very grateful that he's been doing such a great job for so long.
Definitly planed to update and become stable for D10.
It's just a question of time.
No new comments are good news ...
Merged the patch.
Available in >= 8.x-1.5
Patch applied.