[webkit-dev] Opening New Window doesn't work in Gtk port of Webkit.

2008-04-10 Thread Srinivas Rao M Hamse
Hi,
I am using the latest build r31738. My intention is to being able to open
the href link on the same window, instead of opening a fresh window for it.
When i click New Window! button available at:

http://www.pageresource.com/jscript/jwinopen.htm

I get nothing changed on screen. I see most of these functions in
FrameLoaderClientGtk.cpp are unimplemented for GTK, But their respective
counterpart functions for mac and windows architecture are implemented.

I saw a bug being logged to handle this issue.

http://bugs.webkit.org/show_bug.cgi?id=16562

Also applied the Proposed patch
http://bugs.webkit.org/attachment.cgi?id=19530action=view  .

After applying this patch, i see that the function *
FrameLoaderClient::dispatchDecidePolicyForNewWindowAction* is still not
being called, when i click on New Window! button in the above mentioned
link.

IS there a different patch available for this feature to work on the latest
builds ?
Am i missing something trivial here.

regards,
Srinivas Rao. M

-- 
Srinivas Rao M Hamse http://msrinirao.blogspot.com
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] State of WebKit S60

2008-04-10 Thread Nicholas Shanks

On 9 Apr 2008, at 7:16 pm, Eric Seidel wrote:


There has not been a checkin to the S60 port in over 8 months:
http://trac.webkit.org/projects/webkit/browser/S60

As far as I can tell, the port is dead.

There are even 12 patches which were approved but never landed:
http://tinyurl.com/5bt4rk



I think someone should land these even if the fork is dead, so that  
anyone looking at the code in future (perhaps contemplating a similar  
port) won't have as many bugs to consider.


— Nicholas Shanks.



smime.p7s
Description: S/MIME cryptographic signature
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


[webkit-dev] We get our wince port update avaliabe now!

2008-04-10 Thread ledwinka
Hi All

We current get our wince port of webkit runnable now on windows
mobile 2003  windows mobile 5 now. Our branch start up on S60Webkit, all
code depends on Nokia-internal source files has been moved out.  
There are still a lot of work to do to make wince port more stable
and usable, welcome to join us and help us.
Our project host on 

http://sourceforge.net/projects/safarimobile/

Ledwinka



___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


[webkit-dev] Turning off blue borders on input elements in Safari?

2008-04-10 Thread Johan Lund
How can I turn off the blue borders that Safari adds around input  
elements?


Regards
Johan Lund
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Turning off blue borders on input elements in Safari?

2008-04-10 Thread Matt Lilek
On Thu, Apr 10, 2008 at 3:46 AM, Johan Lund [EMAIL PROTECTED] wrote:

 How can I turn off the blue borders that Safari adds around input
 elements?

 Regards
 Johan Lund


Add outline: none;
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] XHR XML Escaping

2008-04-10 Thread Eric Seidel
The FF/IE behavior looks to be in disagreement with the spec:

http://www.w3.org/TR/XMLHttpRequest/#send

So it seems like both the spec and our code should be changed.

Please file a bug:
http://webkit.org/quality/reporting.html

Bugs reported on the mailing list are unlikely to be fixed unless also
added to the bugs database.

-eric


On Thu, Apr 10, 2008 at 7:37 PM, Keith Kowalczykowski [EMAIL PROTECTED] wrote:
 Hi Everyone,

 I'm having a little problem with Safari (3.1) and the escaping of XML
  when using XmlHttpRequest. The behavior that I'm seeing is that
  Safari/Webkit is not properly escaping  and  when sending an XML document
  to the server. For example, if I have the following XML document:

  foo foo=abab/foo

  On Firefox/IE, the value sent to the server is:

  foo fooaamp;baamp;b/foo

  However, on Safari, the value is:

  foo foo=abab/foo

  I have included some proof-of-concept code at the end of this email. Please
  let me know if there is something obvious that I'm doing wrong, or if this
  is really a bug in Safari/Webkit. Thanks.

 -Keith

  Sample Code:

  This code simply creates an XML document that is the same as the example I
  gave above. It then creates an XHR object and sends it to the server. The
  server simply sends the received value back to the client, which is then
  displayed using an alert dialog. Under IE and FF, this code works fine.
  Under Safari, however, it does not.

  test.html

  html
 head
 /head

 body
 /body
 script type=text/javascript
 // Create a new document
 var dom = document.implementation.createDocument(,, null);

 // Create the root node
 var root = dom.appendChild(dom.createElement(foo));

 // Add an attribute
 root.setAttribute(foo, ab);

 // Add a text node
 var txt = dom.createTextNode(ab);

 // Append it
 root.appendChild(txt);

 // Create the XHR object
 var xhr = new XMLHttpRequest();
 xhr.open(POST, test.php, true);
 xhr.onreadystatechange = function()
 {
 if (xhr.readyState == 4  xhr.status == 200)
 {
 alert(xhr.responseText);
 }
 };
 xhr.send(dom);



 /script

  /html

  test.php

  ?php
 print @file_get_contents('php://input');
  ?


  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  http://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Adding Javascript object to Webkit

2008-04-10 Thread Lee Ka Yuk
Dear all,

I've tested with JSCore/API and JSCore/binding.
To my surprise, none of the test apps is working.

I don't have CoreFoundation/CoreFoundation.h in my platform
(Qtopia/Ubuntu) so I could not pass the build of
JSCore/API/JSStringRefCF.h.
How can I use JSCore/API then?

Then I switched to JSCore/binding and found that testbindings.cpp and
testqtbindings.cpp are out of date.
(Interpreter class has changed its API.)
I see that the latest SVN trunk have JSCore/binding removed (I'm using
r28997).
So I think the only way to go is to get JSCore/API working.

And I still have some questions about JSCore.
What's the correspondence of the life cycle of the JS object to the C++
object?
More specifically, when will the C++ object be constructed? At the same
time a corresponding JSObject is created?
Will the C++ object be deleted when the JSObject is garbage collected?
If not, when should we free the C++ object?

Thanks,
LEE

~
This message (including any attachments) is for the named
addressee(s)'s use only. It may contain sensitive, confidential,
private proprietary or legally privileged information intended for a
specific individual and purpose, and is protected by law. If you are
not the intended recipient, please immediately delete it and all copies
of it from your system, destroy any hard copies of it
and notify the sender. Any use, disclosure, copying, or distribution of
this message and/or any attachments is strictly prohibited.


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Webkit with directfb on linux

2008-04-10 Thread Giri Rao
Mike,

When I can get the patches?

Thanks
Giri

On Wed, Apr 9, 2008 at 3:47 PM, Mike Emmel [EMAIL PROTECTED] wrote:

 I added zoom support into the gtk layer and I have some patches needed
 to build directfb if no X11 is installed some files import X11 still
 mainly the plugin stuff.

 Turns out to keep zooming in you have to set min font size to zero.

 And yes I have a few different builds for gtk directfb.

 Mike


 On Wed, Apr 9, 2008 at 12:33 AM, Srinivas Rao M Hamse
 [EMAIL PROTECTED] wrote:
  Mike,
 
 
   Finally if your using this for thumbnails I also have so zooming
 patches.
 
 
  What do you mean by zooming patches ?. Is the full page zooming works ?
 Do
  you have it for Gtk+DirectFB builds ?
 
  regards,
 
  Srinivas
 
 
 
 
 
 
  On Thu, Apr 3, 2008 at 11:34 PM, Mike Emmel [EMAIL PROTECTED]
 wrote:
 
   Yes if you need help with your setup i.e no X11 I have some patches.
   Also I have some pure memory driver patches for DirectFB itself that I
   need to push.
   Finally if your using this for thumbnails I also have so zooming
 patches.
  
  
  
  
   On Thu, Apr 3, 2008 at 10:06 AM, Giri Rao [EMAIL PROTECTED] wrote:
Hello,
   
I was wondering if anyone has successfully built webkit with target
 set
  to
directfb (as opposed to X11) on linux.  I have a successful gtk
 build
  which
is running fine.  However, I would like to run webkit on a headless
  linux
machine hence the question.
   
Thanks
Giri
   
___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo/webkit-dev
   
   
   ___
   webkit-dev mailing list
   webkit-dev@lists.webkit.org
   http://lists.webkit.org/mailman/listinfo/webkit-dev
  
 
 
 
  --
  Srinivas Rao M Hamse
 

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] XHR XML Escaping

2008-04-10 Thread Eric Seidel
My apologies.

I misread your message.  You are correct.  Our behavior seems wrong to
me too.  Please file a bug.

-eric

On Thu, Apr 10, 2008 at 10:20 PM, Keith Kowalczykowski
[EMAIL PROTECTED] wrote:
 Hi Eric,

 Thanks for the quick response. Based upon the way I interpret the spec,
  it seems as though FF and IE are in agreement. Specifically, the spec states
  that send() should Serialize data into a namespace well-formed XML document
  and encoded using the encoding given by data.xmlEncoding, if specified, or
  UTF-8 otherwise. Looking at the XML spec (
  http://www.w3.org/TR/2006/REC-xml-20060816/#sec-well-formed), a well formed
  document should exclude  and  from attribute and entity values. Therefore,
  it seems as though FF/IE are doing the correct thing in escaping these
  characters, where-as Safari is not. Maybe I'm interpreting something wrong,
  though?

 I have filed a bug #18421 about the issue. What is the general processes
  for looking at/prioritizing bugs within WebKit?

 Thanks,
 Keith



   The FF/IE behavior looks to be in disagreement with the spec:
  
   http://www.w3.org/TR/XMLHttpRequest/#send
  
   So it seems like both the spec and our code should be changed.
  
   Please file a bug:
   http://webkit.org/quality/reporting.html
  
   Bugs reported on the mailing list are unlikely to be fixed unless also
   added to the bugs database.
  
   -eric
  
  
   On Thu, Apr 10, 2008 at 7:37 PM, Keith Kowalczykowski [EMAIL PROTECTED]
   wrote:
   Hi Everyone,
  
   I'm having a little problem with Safari (3.1) and the escaping of XML
when using XmlHttpRequest. The behavior that I'm seeing is that
Safari/Webkit is not properly escaping  and  when sending an XML 
 document
to the server. For example, if I have the following XML document:
  
foo foo=abab/foo
  
On Firefox/IE, the value sent to the server is:
  
foo fooaamp;baamp;b/foo
  
However, on Safari, the value is:
  
foo foo=abab/foo
  
I have included some proof-of-concept code at the end of this email. 
 Please
let me know if there is something obvious that I'm doing wrong, or if 
 this
is really a bug in Safari/Webkit. Thanks.
  
   -Keith
  
Sample Code:
  
This code simply creates an XML document that is the same as the example 
 I
gave above. It then creates an XHR object and sends it to the server. The
server simply sends the received value back to the client, which is then
displayed using an alert dialog. Under IE and FF, this code works fine.
Under Safari, however, it does not.
  
test.html
  
html
   head
   /head
  
   body
   /body
   script type=text/javascript
   // Create a new document
   var dom = document.implementation.createDocument(,, null);
  
   // Create the root node
   var root = dom.appendChild(dom.createElement(foo));
  
   // Add an attribute
   root.setAttribute(foo, ab);
  
   // Add a text node
   var txt = dom.createTextNode(ab);
  
   // Append it
   root.appendChild(txt);
  
   // Create the XHR object
   var xhr = new XMLHttpRequest();
   xhr.open(POST, test.php, true);
   xhr.onreadystatechange = function()
   {
   if (xhr.readyState == 4  xhr.status == 200)
   {
   alert(xhr.responseText);
   }
   };
   xhr.send(dom);
  
  
  
   /script
  
/html
  
test.php
  
?php
   print @file_get_contents('php://input');
?
  
  
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
  


  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  http://lists.webkit.org/mailman/listinfo/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev