Re: [webkit-dev] Safari not connecting to IPv6 server with numeric address

2008-01-18 Thread Andre-John Mas


On 18-Jan-08, at 23:47 , Steve Atkins wrote:



On Jan 18, 2008, at 8:39 PM, Darin Adler wrote:


On Jan 18, 2008, at 8:18 PM, Andre-John Mas wrote:

If I try connecting to my web server, on my local network, which  
is running Apache 2 with IPv6, the following fails:


http://[fe80::230:65ff:fed6:b164%en0]/

Yet at the same time, from the command line:

telnet -6 "fe80::230:65ff:fed6:b164%en0" 80

connects. Typing in:

GET /

results in a returned page. Is this a webkit issue or a safari  
issue?


Neither WebKit nor Safari.

In WebKit on Mac OS X, host names in URLs are interpreted by the  
NSURL family of classes in the Foundation framework.


So if that's not working, it's most likely an issue in either  
Foundation or the CFNetwork library that is used by the NSURL  
classes. You can report the bug at .


It's not a valid URL, I don't believe. The %en0 on the end looks  
suspicious, not least because the '%' symbol is an escape character  
in a URL.



The error given by Safari is: "Safari can’t open the page “http:// 
[fe80::230:65ff:fed6:b164%en0]/” because it’s an invalid address."


I did a little research and from what I can tell its seems to be a  
case of RFC 3986 being out of date with regards to RFC 4007. The  
second RFC adds the notion of a "zone indice" to the IPv6 address, yet  
the specification for the "Universal Resource Identifier" has not been  
updated to reflect this. Currently I can't see any documented way to  
specify the address with the URI.


I will see whether I can find someone IETF related who could give me  
an answer.


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


Re: [webkit-dev] Safari not connecting to IPv6 server with numeric address

2008-01-18 Thread Steve Atkins


On Jan 18, 2008, at 8:39 PM, Darin Adler wrote:


On Jan 18, 2008, at 8:18 PM, Andre-John Mas wrote:

If I try connecting to my web server, on my local network, which is  
running Apache 2 with IPv6, the following fails:


http://[fe80::230:65ff:fed6:b164%en0]/

Yet at the same time, from the command line:

telnet -6 "fe80::230:65ff:fed6:b164%en0" 80

connects. Typing in:

GET /

results in a returned page. Is this a webkit issue or a safari issue?


Neither WebKit nor Safari.

In WebKit on Mac OS X, host names in URLs are interpreted by the  
NSURL family of classes in the Foundation framework.


So if that's not working, it's most likely an issue in either  
Foundation or the CFNetwork library that is used by the NSURL  
classes. You can report the bug at .


It's not a valid URL, I don't believe. The %en0 on the end looks  
suspicious, not least because the '%' symbol is an escape character in  
a URL.


Cheers,
  Steve

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


Re: [webkit-dev] Safari not connecting to IPv6 server with numeric address

2008-01-18 Thread Darin Adler

On Jan 18, 2008, at 8:18 PM, Andre-John Mas wrote:

If I try connecting to my web server, on my local network, which is  
running Apache 2 with IPv6, the following fails:


http://[fe80::230:65ff:fed6:b164%en0]/

Yet at the same time, from the command line:

telnet -6 "fe80::230:65ff:fed6:b164%en0" 80

connects. Typing in:

GET /

results in a returned page. Is this a webkit issue or a safari issue?


Neither WebKit nor Safari.

In WebKit on Mac OS X, host names in URLs are interpreted by the NSURL  
family of classes in the Foundation framework.


So if that's not working, it's most likely an issue in either  
Foundation or the CFNetwork library that is used by the NSURL classes.  
You can report the bug at .


-- Darin

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


[webkit-dev] Safari not connecting to IPv6 server with numeric address

2008-01-18 Thread Andre-John Mas

Hi,

If I try connecting to my web server, on my local network, which is  
running Apache 2 with IPv6, the following fails:


http://[fe80::230:65ff:fed6:b164%en0]/

Yet at the same time, from the command line:

telnet -6 "fe80::230:65ff:fed6:b164%en0" 80

connects. Typing in:

GET /

results in a returned page. Is this a webkit issue or a safari issue?

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


Re: [webkit-dev] Runtime JSObject

2008-01-18 Thread jligman
Hi Ankush,Not sure if this is exactly the right way to do this, or what your looking for, but I think something like the following might work. KJS::Window* window  = KJS::Window::retrieveWindow(frame);if (window) {    ExecState* exec = window->interpreter()->globalExec();    window->put( exec, "your object name here", your object here, KJS::DontDelete );}ThanksJoe-Original Message-
From: ankush tiwari <[EMAIL PROTECTED]>
Sent: Jan 18, 2008 7:55 AM
To: webkit-dev@lists.webkit.org
Subject: [webkit-dev] Runtime JSObject

Hi All,We are creating a run time JSObject "myImplementation" by using the NPN framework (C binding) available in webkit. Currently we are facing a problem that our object is not getting recognized when we navigate to a new page.
(Note: Our object is not released, its just not getting recognized in the new page's interpreter context)We want to retain our object till the time the interpreter is valid but we are not able to do so. We observed that for every script handler a context is created and if we put our code in KJSProxy::evaluate and insert our object every time its working fine.
But this way we are creating too many unnecessary instances of our object.Can someone suggest a better way for retaining the object throughout the interpreters life cycle?Thanks,Ankush.

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


[webkit-dev] Runtime JSObject

2008-01-18 Thread ankush tiwari
Hi All,

We are creating a run time JSObject "myImplementation" by using the NPN
framework (C binding) available in webkit. Currently we are facing a problem
that our object is not getting recognized when we navigate to a new page.

(Note: Our object is not released, its just not getting recognized in the
new page's interpreter context)

We want to retain our object till the time the interpreter is valid but we
are not able to do so. We observed that for every script handler a context
is created and if we put our code in KJSProxy::evaluate and insert our
object every time its working fine.

But this way we are creating too many unnecessary instances of our object.

Can someone suggest a better way for retaining the object throughout the
interpreters life cycle?

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


[webkit-dev] Avoid extra page layout on resize

2008-01-18 Thread Artem Ananiev

Hi,

I have a question about the way webkit layouts page contents, and what 
is the right way to implement ScrollView class. In my current 
implementation (Java platform) I see the following:


1. Suppose user resizes the window, so the top-most frame/scroll view 
has the size 800x600.


2. Scroll view updates its values (frame geometry, visible rect, etc.) 
and calls layout() to relayout the page.


3. If the page doesn't fit into 800x600, say, it is 1200 in height, then 
WebKit calls scroll view's resizeContents() method with 800x1200.


4. As the requested contents height is greater than scroll view height, 
vertical scrollbar appears, and the page needs relayout again.


5. In the second layout, WebKit calls resizeContens() with the smaller 
width (say, 780, if scrollbar is 20 pixels wide) and some height (say, 
1230).


This two-steps layout process looks strange to me. It also leads to 
extra repaints, and the performance is not as good as desired. The 
question is: (at the step 3) why resizeContents() is called with 800 as 
a value of width, while it is clear that contents doesn't fit to the 
page and vertical scrollbar is required? What methods must be 
implemented by platform, so WebKit may take vertical scrollbar into 
consideration before it actually appear?


Thanks,

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