A huge request to the developers: provide an address field for custom_style.css This address must be saved in the settings. This means that BITWARDEN will be updated without deleting custom_style.css.
But it’s even better – to the database with logins
Rather, it is not precisely this implementation that is important here.
But the ability to style the previous and subsequent elements. You can set the rest as you like.
You may to mod simple this code for styling +/-2 elements regarding :hover
Here I use a simple one: Border: 2px. Its width is initially 0. The border is adjusted by TailWind.
I can’t redefine it right away.
The outer border increases the TailWind border, and causes each element to be offset by the thickness of the border – it is incorrect.
But here the theme is not for accurate reproduction, but for possibilities.
Immediately after creating this theme, 3 days later, Opera disabled the ability to edit CSS properties. And the entire code as a whole.
Not 3 years later, not 3 years before the creation of this theme. .But after 3 days.
You can guess for yourself “where the legs grow from.” What “legs” ? More precisely, whose “ears are sticking out”
In other words, you won’t see this beauty in the Opera. You won’t be able to apply your knowledge.
I understand that BW’s whole concern is in the danger of editing JS. That is, you can edit your JS on your computer and steal your own passwords.
But that doesn’t justify disabling CSS editing. And as the name of this topic suggests, there are ways to both ensure the integrity of BW and leave children’s entertainment modding to their users.
in variant 1 you can delete “transform” from the 1st and last line.
This is set the transition time for all properties. You can add your own properties.