June 2007 - webkit-dev - lists.webkit.org

WebKit Project Goals
by Maciej Stachowiak 26 Jul '07

26 Jul '07

Hi Everyone, I recently watched a video on the topic of preventing poisonous people from hurting an open source project. One of the practices it recommends for a large open source project is to have a "mission statement", so it's clear to everyone what is and isn't in scope for the project. I'm not too fond of the name "mission statement" (it sounds a little corporate) but I do think it's important to write down our goals as a project. Ultimately I'd like to put this on the WebKit site, but I wanted to throw out some ideas for discussion. I'd like to hear if anyone thinks I have missed any project goals, if any of these are worded badly, or if it is worth calling out more non-goals. WebKit Project Goals WebKit is an open source Web content engine for browsers and other applications. We value real-world web compatibility, standards compliance, stability, performance, security, portability, usability and relative ease of understanding and modifying the code (hackability). Web Content Engine - The project's primary focus is content deployed on the World Wide Web, using standards-based technologies such as HTML, CSS, JavaScript and the DOM. However, we also want to make it possible to embed WebKit in other applications, and to use it as a general-purpose display and interaction engine. Open Source - WebKit should remain freely usable for both open source and proprietary applications. To that end, we use BSD-style and LGPL licenses. Compatibility - For users browsing the web, compatibility with their existing sites is essential. We strive to maintain and improve compatibility with existing web content, sometimes even at the expense of standards. We use regression testing to maintain our compatibility gains. Standards Compliance - WebKit aims for compliance with relevant web standards, and support for new standards In addition to improving compliance, we participate in the web standards community to bring new technologies into standards, and to make sure new standards are pratical to implement in our engine. We use regression testing to maintain our standards compliance gains. Stability - The main WebKit code base should always maintain a high degree of stability. This means that crashes, hangs and regressions should be dealt with promptly, rather than letting them pile up. Performance - Maintaining and improving speed and memory use is an important goal. We never consider performance "good enough", but strive to constantly improve. As web content becomes richer and more complex, and as web browsers run on more limited devices, performance gains continue to have value even if normal browsing seems fast enough. Security - Protecting users from security violations is critical. We fix security issues promptly to protect users and maintain their trust. Portability - The WebKit project seeks to address a variety of needs. We want to make it reasonable to port WebKit to a variety of desktop, mobile, embedded and other platforms. We will provide the infrastructure to do this with tight platform integration, reusing native platform services where appropriate and providing friendly embedding APIs. Usability - To the extent that WebKit features affect the user experience, we want them to work in accordance with good human interface design principles, and to mesh well with platform-native HI conventions. Hackability - To make rapid progress possible, we try to keep the code relatively easy to understand, even though web technologies are often complex. We try to use straightforward algorithms and data structures when possible, we try to write clear, maintainable code, and we continue to improve names and code structure to aid understanding. When tricky "rocket science" code is truly needed to solve some problem, we try to keep it bottled up behind clean interfaces. Non-Goals WebKit is an engine, not a browser. We do not plan to develop or host a full-featured web browser based on WebKit. Others are welcome to do so, of course. WebKit is an engineering project not a science project. For new features to be adopted into WebKit, we strongly prefer for the technology or at least the use case for it to be proven. WebKit is not a bundle of maximally general and reusable code - we build some general-purpose parts, but only to the degree needed to be a good web content engine. WebKit is not the solution to every problem. We focus on web content, not complete solutions to every imaginable technology need.

9 13

where is a documentation?
by Oleg Sukhodolsky 06 Jul '07

06 Jul '07

Hi, I'm investigating possibility to use WebKit as a embedded html renderer, but I've failed to find any documentation on API I could use for this :( It would be also interesting to guidelines/recommendation on porting the WebKit to new platforms. Is there any documentation about this? Thanks, Oleg.

2 4

Cookies in GDK Port
by sachin J Puranik 05 Jul '07

05 Jul '07

Can anybody please explain me , how the Cookies in the WebKit are Handled. Three functions setCookies, cookies, enableCookies are called only from the Java Script. Where is the place actually cookies are added to request , in WebKit. What do i need to do if i want to make my cookies persistent. Thanks Sac

2 6

Firefox spoofing in Safari 3.0 and Gmail issues
by Andre-John Mas 03 Jul '07

03 Jul '07

Hi, In Safari 3.0 it is now possible to change the user agent to Firefox 2.0.0.2. In doing so the Gmail site does not render at all. Well it displays but no formatting is provided, not even HTML elements. Is this a known issue? Build is 522.11. Andre

3 6

XMLHttpRequest and readyState==3
by Christopher Allen 02 Jul '07

02 Jul '07

We are in the process of trying to make SynchroEdit <www.synchroedit.com> work with Safari 3.0, with the eventual goal of seeing if it is possible to synchroedit documents using an iPhone. SynchroEdit is an open-source simultaneous web editor (in the style of SubEthaEdit) that currently only works in Mozilla/Firefox/Camino browsers. The technique it uses is to synchronize the DOM tree between multiple machines, so it potentially has some interesting uses beyond synchronous editing. For the most part, things seem to be working well, but one feature we make use of heavily is the readyState==3 effect which is supported by Firefox. We have read that this feature is unsupported by the WHATWG spec, and that it will most likely not be implemented into Safari. The reason why we need this functionality is that we are building highly-interactive web applications, and we have found that we need to cut down on the number of connections to and from the HTTP server, in order to gain performance. Opening a new connection for every input/output request would slow the browser, and the server, down substantially. As the browser is the initiator of all requests, pending output (from server to client) requests can only be determined by repeatedly polling the server for updates, or by keeping some form of streaming connection using a technique like the readystate technique as described below. Basically, the Firefox technique involves reading the <XMLHttpRequest>.responseText value while the request itself stays in readyState==3 (loading). The responseText buffer updates as new input appears, and in this manner a "streaming data connection" is achieved. Whenever new data is sent to the browser from the server via the XMLHttpRequest, Firefox triggers another "readystatechange", even though the readyState changes "from 3 to 3". This lets coders put in code akin to "onRead" for a regular TCP connection interface, but in AJAX apps. This technique has been hugely effective not only for SynchroEdit, but for other applications that keep a continuous connection to the server such as interactive chat applications. As an alternative approach that might work with WebKit, which we've tested in r23558, is to instead make a setInterval() "check_data" style function, which simply checks the size of the responseText string for updates. Example code* would look like: var rt_index = 0; var req = null; function itv_check_data() { var curr_index = req.responseText.length; if (rt_index == curr_index) return; // no new data var s = req.responseText.substring(rt_index); rt_index = curr_index; alert("new input: " + s); } function start_reading() { req = new_XHR(); // new XMLHttpRequest() in FF req.open("POST", "foo.cgi", true); req.send("test"); setInterval("itv_check_data()", 333); // run itv_check_data thrice/sec } * The above code is untested and may be bugged. This alternative technique worked fine in Firefox (but had a higher latency then the readystate==3 technique), but it does not seem to work in WebKit r23558 either. It appears WebKit is not setting the responseText variable until the request has completed. Is there a way to access this text prior to state 4? Another possible approach which we are investigating is to close the connection server-side, whenever new data is available. The connection is immediately reopened and stays open until new data is available or until the connection times out. This would remove the need for readyState==3 but may have too large an impact on performance. Any suggestions or ideas for us? -- Christopher Allen P.S. We think SynchroEdit would be an interested test-bed for WebKit as it makes extensive use of designMode-enabled frames and our the DOM synchronization tends to expose bugs in DOM. Let us know if you are interested in helping us port it to support WebKit/Safari.

4 7

Reflections on FontPlatformData, FontCache
by Holger Freyther 30 Jun '07

30 Jun '07

Hi, is it right that FontData owns the FontPlatformData it gets assigned? And that FontData::platformInit and ::platformDestroy define the lifetime of the FontDataPlatform. So if I destroy the "platform specific objects" created by FontPlatformData I will not interact badly with the cache? This ownerhip in the Gdk port was wrong and I needed some time to figure that out. While reading the code I think I have found a oversight in the FontPlatformData of the Mac port. The FontCache uses a HashMap. This HashMap will use the (implicit) Copy-Constructor and the (implicit) Assignment-Operator of the FontPlatformData to store objects in the cache. I'm not that familiar with CoreFoundations reference counting, but CFRetain is called in the explicit Copy-Constructor for the NSFont* and I wonder why there isn't an explicit assignment operator increasing the reference on the other font and decreasing it on the current one. Why does this implicit copy operator work here? Comments would be appreciated. z.

2 1

Re: [webkit-dev] Re: Spinneret build issue (on Windows)
by Double-Dee Zee 30 Jun '07

30 Jun '07

Hi All, I was able to get Spinneret to build: I just needed to update the paths in the .sln file so that the defendant project files were being found correctly. (Previously, I was building WebKit in a separate solution. I had assumed this was OK. But apparently, there were some dependencies that were being resolved automatically by Visual Studio when all the projects are in the same solution.) Now (of course), I am having problems getting it to run. I had to find a handful off dll's and now it launches, but at this line: HRESULT hr = CoCreateInstance(CLSID_WebView, 0, CLSCTX_ALL, IID_IWebView, (void**)&gWebView); I get the error: Runtime Error! An application has made an attempt to load the C runtime library incorrectly. Somebody out there must be using Spinneret, can you please help? Is Spinneret now defunct? If yes, then why was that Win32 build issue resolved just 10 days ago? Is someone successfully using Spinneret with the new Win32 build? Thanks, Double-D On 6/29/07, Jerry <jerry(a)chordia.co.uk> wrote: > > DD. > > 1. Find the file(s) that contain your missing GUIDs (_IID_IWebViewPrivate > for example). I'd put racing odds on these being located in a .H file. > 2. See what flags are used to compile said file(s) when Safari is built. > There is sometimes preprocessor hackery involved to avoid multiple-reference > linker errors. > 3. You can double-check 2) by getting the linker to create a .MAP file and > finding the locations of the missing GUIDs there. > 4. Ensure the results of 1 and 2 are included in the Spinneret project. > 5. Report results to the panel. > > Clear? > > HtH and BoL. > > Jerry. > > > ----- Original Message ----- > *From:* Double-Dee Zee <doubledeezee(a)gmail.com> > *To:* Christopher Brichford <chrisb(a)adobe.com> > *Cc:* webkit-dev(a)lists.webkit.org > *Sent:* Friday, June 29, 2007 9:53 PM > *Subject:* Re: [webkit-dev] Re: Spinneret build issue (on Windows) > > Hi Chris, > > Thanks for the reply! It is good to see at least someone is reading my > emails :). > > >>There are instructions on webkit.org for building WebKit on windows > and running it with the windows version of Safari. > > Thanks for the pointer. I do already have WebKit building and running > with Safari. However, I need a windows application that is not Safari for > the demo I am working on. > > >>My understanding is that spinneret is not being worked on anymore. > > I would have suspected that, however this bug fix: > http://trac.webkit.org/projects/webkit/changeset/23566 > for this bug: http://bugs.webkit.org/show_bug.cgi?id=14154 > > shows "Bug 14154: Spinneret doesn't build against the new Win32 port." is > now resolved. The change is from 06/18/07 which is only 11 days ago. > > So apparently, Spinneret is both being worked on and does build against > the new Win32 port. > > > So, can someone please help me with the linking error I see > below....Pretty please.....At least tell me what library I need to link. > > Thanks, > Double-D > > On 6/29/07, Christopher Brichford <chrisb(a)adobe.com> wrote: > > > > My understanding is that spinneret is not being worked on anymore. > > There are instructions on webkit.org for building WebKit on windows > > and running it with the windows version of Safari. > > > > If you have trouble getting your questions answered on the mailing > > list, you can try the webkit irc channel. There are instructions for > > connecting to the IRC channel on webkit.org . > > > > Chris Brichford > > Adobe Systems Inc. > > > > On Jun 29, 2007, at 9:31 AM, Double-Dee Zee wrote: > > > > > Dear Webkit Team, > > > > > > It's been almost 24 hours and no one has replied to my posting. > > > > > > I would really appreciate if someone could point me in the right > > > direction toward solving this problem. > > > > > > I see that another posting ( http://lists.macosforge.org/pipermail/ > > > webkit-dev/2007-June/001940.html) asking for help with Spinneret > > > also went unanswered. Is there something with Spinneret that I > > > should know about? > > > > > > Is it politically incorrect to use Spinneret? > > > > > > Is my question a stupid one that anyone should know the answer to? > > > > > > Even so, I'd really appreciate some help with this so that I can > > > move my project forward. > > > > > > Thanks, > > > Double-D > > > > > > > > > > > > On 6/28/07, Double-Dee Zee <doubledeezee(a)gmail.com> wrote: Dear > > > Webkit Team, > > > > > > I would like to build Spinneret on windows. (I need a windows test > > > application for windows other than Safari.exe). > > > > > > I did see one post that said Spinneret was an outdated test > > > application and implied you shouldn't waste your time on it. > > > However, I also see there was a code fix recently on 2007-06-18 to > > > fix the Spinneret build against the new Win32 port, so I assume > > > Spinneret is still supported. Anyway, this seems like a very > > > useful tool. > > > > > > To build, I simply added the include path: $(WebKitOutputDir) > > > \include\webkit > > > but, then the build fails at the link step (see error message below) > > > > > > This looks to me like a very simple problem to fix, but my COM > > > knowledge is not very deep (I think this is a COM issue) so I could > > > use some help. > > > > > > Can someone please let me know how to resolve this? > > > > > > Thanks, > > > Double-D > > > > > > > > > ------ Build started: Project: Spinneret, Configuration: Debug > > > Win32 ------ > > > Linking... > > > Spinneret.obj : error LNK2001: unresolved external symbol > > > _IID_IWebFrameLoadDelegate > > > Spinneret.obj : error LNK2001: unresolved external symbol > > > _IID_IWebViewPrivate > > > Spinneret.obj : error LNK2001: unresolved external symbol > > > _CLSID_WebView > > > Spinneret.obj : error LNK2001: unresolved external symbol > > > _IID_IWebView > > > Spinneret.obj : error LNK2001: unresolved external symbol > > > _CLSID_WebMutableURLRequest > > > Spinneret.obj : error LNK2001: unresolved external symbol > > > _IID_IWebMutableURLRequest > > > c:\source\WebKit\WebKitBuild\Debug\Spinneret.exe : fatal error > > > LNK1120: 6 unresolved externals > > > Build log was saved at "file://c:\source\WebKit\WebKitBuild > > > \DumpRenderTree.intermediate\Debug\DumpRenderTree.intermediate > > > \BuildLog.htm" > > > Spinneret - 7 error(s), 0 warning(s) > > > ========== Build: 0 succeeded, 1 failed, 3 up-to-date, 0 skipped > > > ========== > > > > > > _______________________________________________ > > > webkit-dev mailing list > > > webkit-dev(a)lists.webkit.org > > > http://lists.webkit.org/mailman/listinfo/webkit-dev > > > > > ------------------------------ > > _______________________________________________ > webkit-dev mailing list > webkit-dev(a)lists.webkit.org > http://lists.webkit.org/mailman/listinfo/webkit-dev > >

2 1

Spinneret build issue (on Windows)
by Double-Dee Zee 29 Jun '07

29 Jun '07

Dear Webkit Team, I would like to build Spinneret on windows. (I need a windows test application for windows other than Safari.exe). I did see one post that said Spinneret was an outdated test application and implied you shouldn't waste your time on it. However, I also see there was a code fix recently on 2007-06-18 to fix the Spinneret build against the new Win32 port, so I assume Spinneret is still supported. Anyway, this seems like a very useful tool. To build, I simply added the include path: $(WebKitOutputDir)\include\webkit but, then the build fails at the link step (see error message below) This looks to me like a very simple problem to fix, but my COM knowledge is not very deep (I think this is a COM issue) so I could use some help. Can someone please let me know how to resolve this? Thanks, Double-D ------ Build started: Project: Spinneret, Configuration: Debug Win32 ------ Linking... Spinneret.obj : error LNK2001: unresolved external symbol _IID_IWebFrameLoadDelegate Spinneret.obj : error LNK2001: unresolved external symbol _IID_IWebViewPrivate Spinneret.obj : error LNK2001: unresolved external symbol _CLSID_WebView Spinneret.obj : error LNK2001: unresolved external symbol _IID_IWebView Spinneret.obj : error LNK2001: unresolved external symbol _CLSID_WebMutableURLRequest Spinneret.obj : error LNK2001: unresolved external symbol _IID_IWebMutableURLRequest c:\source\WebKit\WebKitBuild\Debug\Spinneret.exe : fatal error LNK1120: 6 unresolved externals Build log was saved at "file://c:\source\WebKit\WebKitBuild\DumpRenderTree.intermediate\Debug\DumpRenderTree.intermediate\BuildLog.htm" Spinneret - 7 error(s), 0 warning(s) ========== Build: 0 succeeded, 1 failed, 3 up-to-date, 0 skipped ==========

2 3

How to make S60 webkit installed on a symbian 3rd cellphone such as n71
by 黎明 28 Jun '07

28 Jun '07

Thanks. I will try petran tool to remove unnecessary capabilities. The capabilities which independent developer get through developer certificate is very limited. S60 webkit needs ALL- TCB capabilities! I’m still wondering that is there anybody actual make s60 webkit run on Symbian mobile phone except Nokia guys. Best Regard -黎明 E-mail：ledwinka(a)126.com ledwinkasmall

1 0

WWDC 2007 WebKit SVG Demos
by Antoine Quint 27 Jun '07

27 Jun '07

Hi all, Dean Jackson and myself just posted the demos that we presented at WWDC 2007 about Vector Graphics and Rich Media in WebKit. These mostly showcase SVG, but also its integration with other core technologies such as XHTML, CSS, XMLHttpRequest, JavaScript and the DOM. http://the.fuchsia-design.com/2007/06/wwdc-2007-webkit-svg-demos.html Hope this proves useful to showcase the great SVG support the WebKittens have been building for the last few years. Antoine -- Blog — http://the.fuchsia-design.com

1 0