Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: The IntervalBeforeClose of NotificationService works incorrectly #5358

Closed
tuanhoan opened this issue Mar 13, 2024 · 7 comments
Closed
Assignees
Labels
Type: Bug 🐞 Something isn't working
Projects
Milestone

Comments

@tuanhoan
Copy link

Blazorise Version

1.5.0-preview2

What Blazorise provider are you running on?

None

Link to minimal reproduction, or a simple code snippet

return NotificationService.Warning( "This is a simple notification message!", "Hello", options => options.IntervalBeforeClose = 10000 );

Steps to reproduce

  1. Go to https://rcbootstrapdemo.blazorise.com/tests/utilities/services
  2. Click Show arter! in Notification Service section

image

What is expected?

the snackbar must shows 10000ms

What is actually happening?

The value is set to 10000ms but the snackbar only shows 5000ms as default

What browsers are you seeing the problem on?

No response

Any additional comments?

No response

@tuanhoan tuanhoan added the Type: Bug 🐞 Something isn't working label Mar 13, 2024
@stsrki stsrki self-assigned this Mar 13, 2024
@stsrki stsrki added this to 🔙 Triage in Development via automation Mar 13, 2024
@stsrki stsrki added this to the 1.5 milestone Mar 13, 2024
@David-Moreira
Copy link
Contributor

@stsrki not sure if related : #5313

@stsrki
Copy link
Collaborator

stsrki commented Mar 13, 2024

I have tested it, and it works in the 1.5 version. The demo on https://rcbootstrapdemo.blazorise.com/tests/utilities/services is still running on an older 1.4.0 version. I think simply uploading a new demo would also fix it there.

@stsrki
Copy link
Collaborator

stsrki commented Mar 13, 2024

Uploaded new demos and it is working now.

@stsrki stsrki closed this as completed Mar 13, 2024
Development automation moved this from 🔙 Triage to ✔ Done Mar 13, 2024
@David-Moreira
Copy link
Contributor

Uploaded new demos and it is working now.

Isn't the point of rc to run a preview version?

@stsrki
Copy link
Collaborator

stsrki commented Mar 13, 2024

Do you mean rc in here? rcbootstrapdemo.blazorise.com/tests/utilities/services

That is not for preview. The rc part comes from Razor Components. It is from long ago when Microsoft first introduced Blazor server, and they named it Razor Components. So I released the bootstrap server demo with that prefix. I know, I know, terrible naming. :)

@David-Moreira
Copy link
Contributor

Do you mean rc in here? rcbootstrapdemo.blazorise.com/tests/utilities/services

That is not for preview. The rc part comes from Razor Components. It is from long ago when Microsoft first introduced Blazor server, and they named it Razor Components. So I released the bootstrap server demo with that prefix. I know, I know, terrible naming. :)

AH right... In my personal opinion, I would rename it or just remove the demo as to not cause confusion...

@stsrki
Copy link
Collaborator

stsrki commented Mar 13, 2024

We need to find better naming for our demos that would indicate server vs wasm mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug 🐞 Something isn't working
Projects
Development
  
✔ Done
Development

No branches or pull requests

3 participants