Hi and sorry for my delayed reply. Yes I've done some re-work in the
date code recently, which should treat dates outside of 2038
correctly, but which are not available in any Safari version that has
shipped yet.
I wouldn't be too sure that it's not Safari's fault just because
someone sh
I have also encountered problems with the date code in WebKit. I was
able to fix the bugs I care about ( windows port crashed ) by upgrading
to the latest code from WebKit.org. Since it sounds as though you are
an AJAX developer trying to get your app working in Safari, that might
not help you to
Don't worry -- your question is really reasonable!
Other browsers implement some or all of the date/time stack on their
own, so it's not surprising that you would see variability.
10.3.9 is pretty old, so it's possible that this was a bug that was
fixed in 10.4.x (Tiger).
I don't have a 1
Jason,
Are you able to upgrade from Panther (10.3.9) to Tiger (10.4.x)?
Apple will be releasing Leopard (10.5) within the next few months,
and Panther will be end-of-lifed (for all intents and purposes) after
that.
Dave
On Feb 13, 2007, at 3:20 PM, Jason White wrote:
Hmm. Yes, that's
Hmm. Yes, that's it. The machines having the problem all run 10.3.9
and Safari reports being 1.3.2. I suppose it could be a problem that
was fixed, but since I think people would have noticed this I've got a
feeling that it's probably something external to Safari.. I'm just
really puzzled by why i
Jason,
I tried this in Safari on 10.4.8:
javascript:alert(new Date('01/19/2039').getTime())
and got:
217903680
which is greater than 214748364700.
Am I testing the right thing?
Geoff
On Feb 13, 2007, at 12:57 PM, Jason White wrote:
If I'm posting to a very wrong place, please let me
If I'm posting to a very wrong place, please let me know. I'm having a
problem with a Javascript date in Safari that is preventing me from
supporting it alongside Firefox, IE, and Navigator.
It appears that Safari has a problem when I attempt to use new Date()
and pass in a string formatted date
On 2/13/07, Krzysztof Kowalczyk <[EMAIL PROTECTED]> wrote:
On 2/13/07, atul <[EMAIL PROTECTED]> wrote:
> We (me & shri) both have a worked on GTK+Webcore
> (http://gtk-webcore.sourceforge.net/ ) for sometime & as we are new to
> the current WEBKIT ToT we need someone to guide/help us for
On 2/13/07, atul <[EMAIL PROTECTED]> wrote:
We (me & shri) both have a worked on GTK+Webcore
(http://gtk-webcore.sourceforge.net/ ) for sometime & as we are new to
the current WEBKIT ToT we need someone to guide/help us for understand &
contribute to the latest Webkit For GDK port. This m
Great !
Some history on the port.
My initial plans for the port where to have it gdk only with all widgets in svg.
I am continuing to experiment with a fork of webkit that does not
depend on traditional
widget toolkits. The GDK port can easily be turned into a normal GTK port.
For use with GTK
El Mar, 13-02-2007 a las 17:34 +0530, atul escribió:
> I had a discussion with many people on #webkit & it seems people
> consider Gtk-Webcore Project ( http://gtk-webcore.sourceforge.net/ ) as
> dead project. Well but still, if people had any plans to do Integrate
> the GTK-Webcore project then pl
On Feb 13, 2007, at 2:55 AM, Juan Antonio Suarez Romero wrote:
Hi all!
In the WebKit homepage, one of the projects that people can contribute
is to integrate the existing Gtk port into the source tree. I suppose
the "existing Gtk port" is the Gtk-Webcore" port
( http://gtk-webcore.sourceforge.
hi Juan
On Tue, 2007-02-13 at 11:55 +0100, Juan Antonio Suarez Romero wrote:
> Hi all!
>
> In the WebKit homepage, one of the projects that people can contribute
> is to integrate the existing Gtk port into the source tree. I suppose
> the "existing Gtk port" is the Gtk-Webcore" port
> ( http://g
Hi all!
In the WebKit homepage, one of the projects that people can contribute
is to integrate the existing Gtk port into the source tree. I suppose
the "existing Gtk port" is the Gtk-Webcore" port
( http://gtk-webcore.sourceforge.net/ ).
What is the relation between this port and the existing Gd
Hii.
This is mail in regard of the GDK port Of Webkit.. It seems Qt Port for
Linux is quite well maintained but that's not same for GDK port. I & my
colleague Shri want to contribute for the GDK port of Webkit Which can
meet long needed demand of gnome users having a KHTML+GTK browser.
We
El Lun, 12-02-2007 a las 16:38 -0500, George Staikos escribió:
> The Qt build uses the standard build-webkit and qmake. It's a
> self-contained build, really. CMake is used by the KDE build, which
> is Qt plus KDE libraries.
>
Yes. Each port has its own build system:
Gdk -> BakeFiles
16 matches
Mail list logo
