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
The naming logic of inverted form elements is not consistent.
This could be considered a feature instead of a Bug but currently it's an inconsistent behaviour, which somehow breaks the "inverted" logic for Form Elements:
Input
has two inverted variants:
ui inverted input
ui inverted transparent input
Checkbox
has only one variant: ui inverted checkbox
The matching "inverted transparent" variant according to input logic is completely missing for checkbox.
Dropdown
also has only one variant, But this time "inverted" is completely black without adding "transparent". This breaks the logic acording to input and checkbox
Textarea
does not have any inverted variant at all 😞
This does not feel consistent and makes clearly inverted forms using the default framework nearly impossible.
Solution
I suggest implementing the following class additions :
ui inverted transparent dropdown (which behaves as it currently is without "transparent") ui inverted dropdown (that will be a breaking change) ui inverted textarea ui inverted transparent textarea
Poll
What do you guys think?
The text was updated successfully, but these errors were encountered:
Yes, I agree that the inverted variation is pretty inconsistent between different components. But for now Fomantic's purpose is to be fully compatible with Semantic, on already existing components, so we're tied with these inconsistencies for now. Maybe for an eventual 3.0 ! 😃
I do and don't agree with this, inverted and transparent are 2 different variations the only reason you get these results is because semantic "combines" them. I think this is due to the inverted variation not being implemented for every component like as you mentioned the textarea.
Currently if we implemented a inverted variation of the textarea you would be able to get the same results as the input component since textarea already has a transparent variation.
As for the checkbox/toggles I think it would be more suitable as ui inverted outline checkbox and ui inverted outline toggle because they aren't exactly "transparent".
The dropdown I do agree with and as you said it would be a breaking change so will have to wait but I think that is something we should do.
Problem
The naming logic of inverted form elements is not consistent.
This could be considered a feature instead of a Bug but currently it's an inconsistent behaviour, which somehow breaks the "inverted" logic for Form Elements:
Input
has two inverted variants:
ui inverted input
ui inverted transparent input
Checkbox
has only one variant:
ui inverted checkbox
The matching "inverted transparent" variant according to input logic is completely missing for checkbox.
Dropdown
also has only one variant, But this time "inverted" is completely black without adding "transparent". This breaks the logic acording to input and checkbox
Textarea
does not have any inverted variant at all 😞
This does not feel consistent and makes clearly inverted forms using the default framework nearly impossible.
Solution
I suggest implementing the following class additions :
ui inverted transparent checkout
Suggested Example:
ui inverted transparent dropdown
(which behaves as it currently is without "transparent")ui inverted dropdown
(that will be a breaking change)ui inverted textarea
ui inverted transparent textarea
Poll
What do you guys think?
The text was updated successfully, but these errors were encountered: