fix(EditableTypography): fix specificity issues when changing types a…

[shaharzil]

https://monday.monday.com/boards/3532714909/pulses/6244033346

fixes #1998

[YossiSaadi]

Great! do we plan on removing the typographyClassName usage on both EditableX components? or is there a reason they're still there?

edit: I wasn't clear I think, I know we agreed on leaving both for the solution, but do we plan on removing the class later?

[shaharzil]

Great! do we plan on removing the typographyClassName usage on both EditableX components? or is there a reason they're still there?

edit: I wasn't clear I think, I know we agreed on leaving both for the solution, but do we plan on removing the class later?

It is problematic for 2 reasons:

1. It can be a breaking change
2. the input needs it, otherwise it won't have the correct style (can be solved of course with some specificity with the selector)

So yes, we want to remove it but not now :) (I can open a task for it)

[YossiSaadi]

Great! do we plan on removing the typographyClassName usage on both EditableX components? or is there a reason they're still there?
edit: I wasn't clear I think, I know we agreed on leaving both for the solution, but do we plan on removing the class later?

It is problematic for 2 reasons:

1. It can be a breaking change
2. the input needs it, otherwise it won't have the correct style (can be solved of course with some specificity with the selector)

So yes, we want to remove it but not now :) (I can open a task for it)

hmm got ya
we can create a task with a very low priority, yep