We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Windows notification timestamp is always January 1. (probably 1970-01-01)
Windows 11 22H2 Microsoft Edge 108.0.1462.54
HTML5 Notification.timestamp is number format.
From Spec
A notification has an associated timestamp which is an EpochTimeStamp representing the time.
From MDN
A number representing a timestamp, given as Unix time in milliseconds.
But this library pass timestamp as string format. ISO 8601
ISO 8601
blazor-components/src/Majorsoft.Blazor.Components.Notifications/HTML5/HtmlNotificationData.cs
Line 74 in 879e425
blazor-components/src/Majorsoft.Blazor.Components.Notifications/HTML5/HtmlNotificationService.cs
Lines 61 to 77 in 879e425
blazor-components/src/Majorsoft.Blazor.Components.Notifications/wwwroot/notification.js
Lines 37 to 53 in 879e425
The text was updated successfully, but these errors were encountered:
Fix majorimi#121
5dd0fe6
89ec6db
No branches or pull requests
Bug
Windows notification timestamp is always January 1. (probably 1970-01-01)
Environment
Windows 11 22H2 Microsoft Edge 108.0.1462.54
Bug reason
HTML5 Notification.timestamp is number format.
From Spec
From MDN
But this library pass timestamp as string format.
ISO 8601
blazor-components/src/Majorsoft.Blazor.Components.Notifications/HTML5/HtmlNotificationData.cs
Line 74 in 879e425
blazor-components/src/Majorsoft.Blazor.Components.Notifications/HTML5/HtmlNotificationService.cs
Lines 61 to 77 in 879e425
blazor-components/src/Majorsoft.Blazor.Components.Notifications/wwwroot/notification.js
Lines 37 to 53 in 879e425
The text was updated successfully, but these errors were encountered: