mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-04-26 14:28:49 +00:00
Userland: Remove remaining users of Duration::now_realtime()
This is a clear sign that they want to use a UnixDateTime instead. This also adds support for placing durations and date times into SQL databases via their millisecond offset to UTC.
This commit is contained in:
parent
82c681e44b
commit
effcd080ca
Notes:
sideshowbarker
2024-07-17 01:23:08 +09:00
Author: https://github.com/kleinesfilmroellchen
Commit: effcd080ca
Pull-request: https://github.com/SerenityOS/serenity/pull/17842
Reviewed-by: https://github.com/me-minus
Reviewed-by: https://github.com/timschumi
16 changed files with 62 additions and 45 deletions
|
@ -59,7 +59,7 @@ WebIDL::ExceptionOr<JS::NonnullGCPtr<File>> File::create(JS::Realm& realm, Vecto
|
|||
|
||||
// 3. If the lastModified member is provided, let d be set to the lastModified dictionary member. If it is not provided, set d to the current date and time represented as the number of milliseconds since the Unix Epoch (which is the equivalent of Date.now() [ECMA-262]).
|
||||
// Note: Since ECMA-262 Date objects convert to long long values representing the number of milliseconds since the Unix Epoch, the lastModified member could be a Date object [ECMA-262].
|
||||
last_modified = options->last_modified.has_value() ? options->last_modified.value() : Duration::now_realtime().to_milliseconds();
|
||||
last_modified = options->last_modified.has_value() ? options->last_modified.value() : UnixDateTime::now().milliseconds_since_epoch();
|
||||
}
|
||||
|
||||
// 4. Return a new File object F such that:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue