[Feature Request] Specify size of the toast. about toast HOT 7 CLOSED

Hi @Delpire, why do you feel overriding the CSS is a bad idea?

from toast.

@chrissainty Hello! Perhaps just my lack of css experience. I can give it a try. I like how bootstrap often provides different classes I can pass to an html element to specify the size, I just thought it would be nice to provide this to the Blazored Toast element.

from toast.

I understand where you’re coming from. The problem is what sizes do we provide? Small, medium, large? What’s small? What’s large? One persons small is another persons medium or vice versa.

I’m open to ideas.

from toast.

Well right off the bat, having an option to remove the header would reduce the height. That being said, it probably isn't a good idea to depend purely on color.

I could see maybe providing a "compact" option where the padding is reduced, the font size is reduced, and perhaps the header and text could be on the same line. Kind of like how Slack provides Clean vs Compact messages:

I think you are right though. It is a difficult thing to decide as far as fixed values.

An alternative would be to provide some levers that a user could customize. I just overrode the css by reducing the font-size and the width of the blazored-toast class. If these were parameters to the BlazoredToast component then a user could customize it. I'm not sure how well the support for this is in Blazor. It might have to be applied directly to the html, which with my limited understanding might be a bad decision.

Overall, I'm pretty new to Web UI design, so I am not very familiar with best practices, and Blazor is so new a lot of best practices probably haven't been determined yet. 😅

from toast.

We could definitely expose some levers for people to tweak but if I’m honest, CSS does all of this. I’m reluctant to adds loads of options into the component and make the code far more complex when everything is infinitely customisable with CSS.

from toast.

That's fair. I am okay with this simply being closed.

One last option that I am also not sure about the feasibility of, would be to provide some kind of empty toast type that we could pass a render fragment to.

<Blazored.EmptyToast>
content...
</Blazored.EmptyToast>

Regardless, thank you for taking the time to discuss this!

from toast.

@Delpire We have added a custom toast option now that might be of interest to you

from toast.