Bug 98936

Summary: [GTK] Add support for date and time input UIs
Product: WebKit Reporter: Zan Dobersek <zan>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: aperez, bugs-noreply, changseok, clopez, mcatanzaro, m.kurz+webkitbugs, mrobinson, spamfaenger
Priority: P2 Keywords: Gtk, LayoutTestFailure
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=119175
Bug Depends on: 224921, 224924    
Bug Blocks:    

Description Zan Dobersek 2012-10-10 11:48:05 PDT
The master bug for these features is bug #29359. GTK port should support these UIs at least in developer builds for starters.
Comment 1 Carlos Alberto Lopez Perez 2016-06-27 14:12:40 PDT
*** Bug 127167 has been marked as a duplicate of this bug. ***
Comment 2 m.kurz+webkitbugs 2017-01-09 01:33:20 PST
Is there a chance we'll see this in Safari on macOS soon?
Comment 3 m.kurz+webkitbugs 2017-03-08 01:37:04 PST
Can someone please give an update on this issue?

With Firefox 54 having date inputs behind a flag soon Safari will be the last major browser left lacking support for it. See http://caniuse.com/#feat=input-datetime
Comment 4 Michael Catanzaro 2017-03-08 07:05:22 PST
This bug is for implementing date and time inputs for the GTK+ port. Drawing native widgets is necessarily platform-specific -- we're going to surely want to use GtkCalendar, for example -- so adding a date picker for the GTK+ port is not going to do any good for Safari. You might want to file a new bug report for the macOS or iOS ports.
Comment 5 Carlos Alberto Lopez Perez 2020-03-09 12:13:40 PDT
See bug 119175(In reply to Michael Catanzaro from comment #4)
> You might want to file a new bug report for the macOS or iOS ports.

See bug 119175
Comment 6 Diego Pino 2023-01-25 19:27:50 PST
There are no references to this bug in any TestExpectations. It's probable this bug was solved at some point but it wasn't marked as closed. I'm closing this bug now. If you think this bug report is still valid, please reopen it and add an entry to TestExpectations.