You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty sure that it's not a bug in CookieConsent, but I still have to ask here because I don't think I can solve it any other way. As you can see in the screenshot, the toggles are not exactly in the middle of the lines, but a bit too high. The checkmarks and crosses are also slightly misplaced as a result. The sub-toggles are also not in the middle of the rows, but a bit too high.
Is there a way in the CSS (locally installed) to set the toggles a bit further down (with margin or padding)? The bug is probably caused by the fact that the CookieConsent CSS is not compatible with Bootstrap v4.4.1. If I deactivate Bootstrap CSS, the toggles in CookieConsent are correct...
Current Behavior
Toggles misplaced
Steps to reproduce
Try CookieConsent Css together with Bootstrap 4.4.1
Proposed fix or additional info.
No response
Version
3.0.1
On which browser do you see the issue?
Chrome
The text was updated successfully, but these errors were encountered:
Expected Behavior
I'm pretty sure that it's not a bug in CookieConsent, but I still have to ask here because I don't think I can solve it any other way. As you can see in the screenshot, the toggles are not exactly in the middle of the lines, but a bit too high. The checkmarks and crosses are also slightly misplaced as a result. The sub-toggles are also not in the middle of the rows, but a bit too high.
Is there a way in the CSS (locally installed) to set the toggles a bit further down (with margin or padding)? The bug is probably caused by the fact that the CookieConsent CSS is not compatible with Bootstrap v4.4.1. If I deactivate Bootstrap CSS, the toggles in CookieConsent are correct...
Current Behavior
Toggles misplaced
Steps to reproduce
Try CookieConsent Css together with Bootstrap 4.4.1
Proposed fix or additional info.
No response
Version
3.0.1
On which browser do you see the issue?
Chrome
The text was updated successfully, but these errors were encountered: