[webkit-dev] Webkit SMp support
hi, Recently I read the Multi-processor support coming for Firefox. http://mozillalinks.org/wp/2009/05/multi-processor-support-coming-for-firefox/ I would like analyze webkit behaviour on a single core and multi core system. I hope that this is the right place for the discussion to put my question. I could find many threads are being created within webkit, i used android port of webkit for this. Modifying the procstat revealed that these threads shows the CPU affinity and some tasks get bounced across different CPUs. So on multi processor system defintly webkit should get full advantage and I see webkit should fly on SMP. Could some one tell what are the other aspects to check in webkit for multi core platfrom? how about Javascritpcore , sunspider, DOM, input content parsing, image files handling. Any hints towards optimization for SMP in webkit ? OR is it already complient/Done ? Are there any tools in general avaialble to measure/benchmark browser behaviour? thanks -Vinay ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] How to get the version of 3rdparty lib?
I get webkit's source code, and I know there is webkit port of some 3rd party lib, such as Skia,Qt. Now I want to know the version of these 3rd party lib, such as Skia's version. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] The origin of HTML parser in WebKit
Hi Does someone know the origin of HTML parser in WebKit? I mean _the_ origin (I know it was part of KHTML). Piotr Dobrogost ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] glib bindings
Why did you break the thread? On Mon, 2009-05-11 at 14:19 -0700, Jerry Spicklemire wrote: When you say, you'll have to wait a bit more, I would like to take that as an encouraging sign, but I don't have any point of reference. Roughly how long is a bit more, in Webkit? I can get started with the existing Deb downloads, but by the time I have to start delivering a cross platform version, it will be too late to switch horses. Thanks again, Jerry S. This needs to happen: https://bugs.webkit.org/show_bug.cgi?id=16401 Someone will need to step up and carry on the work by following Sam Weinig's advice, and doing a smaller initial patch. See you, -- Gustavo Noronha g...@gnome.org GNOME contributor ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Controling HTML5 local storage/ databases programmatically
Heya, inspired by bug 25629 [1] I came to wonder how far webkit applications are able to control HTML5 local storage and databases. The bug report is mainly about enabling or disabling these features. So how far does WebCore allow for limiting stored data, in the form of an expiration date and in the form of disk quota? And how can one listen to changes, and manipulate data? I am thinking of ways similar to HTTP cookies, where I can easily see what is added, changed, removed and where data is coming from. Any tips as for how to do this from within WebCore, so that WebKit, specifically WebKitGTK+, can provide API for this, would be greatly appreciated. Apologies for throwing local storage and databases in the same pot here. I'm aware these are distinct features. Yours, Christian [1] https://bugs.webkit.org/show_bug.cgi?id=25629 ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] SessionStorage being serialized to disk
Is anyone here dead set against window.sessionStorage ever being written out to disk (in an unencrypted form)? Session storage needs to be stored for the life of the Page class since the user can always navigate back to a site or hit the back button. This means that a very long lived tab could start wasting a lot of memory in a world where session storage is commonly used. The only reason I've heard against writing session storage to disk is security. For example, a web site storing some security token client side. Unfortunately, you never know when your memory is going to get paged to disk, so if we're serious about keeping session storage secure, we'd need to address that--at least for sites using HTTPS. The spec itself doesn't explicitly say either way. It does suggest that the lifetime of a browsing context (and thus session storage) is not necessarily connected to the lifetime of a browsing process. Since some crash recovery implementations work by serializing the browsers state to disk, the spec seems to be suggesting that it _can_ be written to disk, but I'm not aware of any browsers actually doing this yet. If we did feel strongly about making security guarantees for session storage, we should probably suggest on WhatWG that it be guaranteed by the spec. J ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Support for ESMP and other mobile web standards
On 30-Mar-09, at 5:22 PM, Cameron Zwarich wrote: For some time now there has been a bug in Bugzilla about adding conditional support for ECMA Script Mobile Profile: https://bugs.webkit.org/show_bug.cgi?id=24114 I am capable of reviewing the technical content of the patch, but I don't know how the greater WebKit community feels about adding support for ESMP and related technologies. To what extent do we want support for them in the main WebKit tree? 6 weeks in and no opposition to this. Given that we just rebased the patches against trunk again, and they've already gone through many changes due to review, I'd like to start landing them. Constantly adjusting them is growing tiring, and they do not impact anything unless the macros are enabled. -- George Staikos Torch Mobile Inc. http://www.torchmobile.com/ ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Controling HTML5 local storage/ databases programmatically
On Tue, May 12, 2009 at 11:12 AM, Christian Dywan christ...@twotoasts.dewrote: Heya, inspired by bug 25629 [1] I came to wonder how far webkit applications are able to control HTML5 local storage and databases. The bug report is mainly about enabling or disabling these features. So how far does WebCore allow for limiting stored data, in the form of an expiration date and in the form of disk quota? And how can one listen to changes, and manipulate data? There's no quota support in local storage (yet..I'll probably be looking at this eventually). I don't believe there's any intention to have expiration dates for database, LocalStorage, or AppCache, but there has been talk of a LRU policy of eviction when devices are running out of storage space. I am thinking of ways similar to HTTP cookies, where I can easily see what is added, changed, removed and where data is coming from. Any tips as for how to do this from within WebCore, so that WebKit, specifically WebKitGTK+, can provide API for this, would be greatly appreciated. There's no standard across the APIs for doing anything like this. It shouldn't be too hard to add to localStorage since it already has an event system. Not sure about the others, but I assume it'd take more work. Apologies for throwing local storage and databases in the same pot here. I'm aware these are distinct features. Yours, Christian [1] https://bugs.webkit.org/show_bug.cgi?id=25629 ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Support for ESMP and other mobile web standards
On May 12, 2009, at 3:58 PM, George Staikos wrote: On 30-Mar-09, at 5:22 PM, Cameron Zwarich wrote: For some time now there has been a bug in Bugzilla about adding conditional support for ECMA Script Mobile Profile: https://bugs.webkit.org/show_bug.cgi?id=24114 I am capable of reviewing the technical content of the patch, but I don't know how the greater WebKit community feels about adding support for ESMP and related technologies. To what extent do we want support for them in the main WebKit tree? 6 weeks in and no opposition to this. Given that we just rebased the patches against trunk again, and they've already gone through many changes due to review, I'd like to start landing them. Constantly adjusting them is growing tiring, and they do not impact anything unless the macros are enabled. I'm not a fan of these changes (I don't like divergence in core behavior in the engine). But I think they are reasonable in light of the proposed new way of thinking about ports as a set of policy decisions, and leaving those decisions up to the port maintainers. ENABLE(ESMP) is definitely a policy decision. Let's just make sure we minimize impact on the normal code path and allow for reasonable long- term maintainability. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] SessionStorage being serialized to disk
I don't see a security problem with writing sessionStorage to disk. Site already aren't guaranteed that their memory won't be paged out to disk. Adam On Tue, May 12, 2009 at 3:50 PM, Jeremy Orlow jor...@chromium.org wrote: Is anyone here dead set against window.sessionStorage ever being written out to disk (in an unencrypted form)? Session storage needs to be stored for the life of the Page class since the user can always navigate back to a site or hit the back button. This means that a very long lived tab could start wasting a lot of memory in a world where session storage is commonly used. The only reason I've heard against writing session storage to disk is security. For example, a web site storing some security token client side. Unfortunately, you never know when your memory is going to get paged to disk, so if we're serious about keeping session storage secure, we'd need to address that--at least for sites using HTTPS. The spec itself doesn't explicitly say either way. It does suggest that the lifetime of a browsing context (and thus session storage) is not necessarily connected to the lifetime of a browsing process. Since some crash recovery implementations work by serializing the browsers state to disk, the spec seems to be suggesting that it _can_ be written to disk, but I'm not aware of any browsers actually doing this yet. If we did feel strongly about making security guarantees for session storage, we should probably suggest on WhatWG that it be guaranteed by the spec. J ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] How to detect the parameters in object tag?
Hi, everyone Recently, I met a HTML page which has a object tag like this: OBJECT id=player style=LEFT: 0px; WIDTH:100%; TOP: 0px; HEIGHT:100% codebase= classid= param name=URL value=? PARAM NAME=ShowUI VALUE=1 PARAM NAME=volume VALUE=90 PARAM NAME=autoPlay VALUE=2 PARAM NAME=mute VALUE=0 PARAM NAME=DropEnable VALUE=0 PARAM NAME=EnableFullScreen VALUE=0 PARAM NAME=ShowVideo VALUE=1 param name=loop value=2/ /OBJECT script language=JavaScript document.player.URL = urlpath+file; /Script I have two questions 1.how to detect the parameters in object tag? 2.specially, how to detect the URL param which is changed by Javascript? Thank you! ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] How to detect the parameters in object tag?
Hi, For the first question, you can implement a NPAPI plugin. You can get all the parameters in the plugin-side functions API(NPPluginFuncs-newp). Thanks. -Xiong On Wed, May 13, 2009 at 8:56 AM, naixuan guan guannaix...@gmail.com wrote: Hi, everyone Recently, I met a HTML page which has a object tag like this: OBJECT id=player style=LEFT: 0px; WIDTH:100%; TOP: 0px; HEIGHT:100% codebase= classid= param name=URL value=? PARAM NAME=ShowUI VALUE=1 PARAM NAME=volume VALUE=90 PARAM NAME=autoPlay VALUE=2 PARAM NAME=mute VALUE=0 PARAM NAME=DropEnable VALUE=0 PARAM NAME=EnableFullScreen VALUE=0 PARAM NAME=ShowVideo VALUE=1 param name=loop value=2/ /OBJECT script language=JavaScript document.player.URL = urlpath+file; /Script I have two questions 1.how to detect the parameters in object tag? 2.specially, how to detect the URL param which is changed by Javascript? Thank you! ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Support for ESMP and other mobile web standards
On 12-May-09, at 7:24 PM, Maciej Stachowiak wrote: On May 12, 2009, at 3:58 PM, George Staikos wrote: On 30-Mar-09, at 5:22 PM, Cameron Zwarich wrote: For some time now there has been a bug in Bugzilla about adding conditional support for ECMA Script Mobile Profile: https://bugs.webkit.org/show_bug.cgi?id=24114 I am capable of reviewing the technical content of the patch, but I don't know how the greater WebKit community feels about adding support for ESMP and related technologies. To what extent do we want support for them in the main WebKit tree? 6 weeks in and no opposition to this. Given that we just rebased the patches against trunk again, and they've already gone through many changes due to review, I'd like to start landing them. Constantly adjusting them is growing tiring, and they do not impact anything unless the macros are enabled. I'm not a fan of these changes (I don't like divergence in core behavior in the engine). But I think they are reasonable in light of the proposed new way of thinking about ports as a set of policy decisions, and leaving those decisions up to the port maintainers. ENABLE(ESMP) is definitely a policy decision. Let's just make sure we minimize impact on the normal code path and allow for reasonable long-term maintainability. Thanks Maciej. We wrote and rewrote this code many times over to try to keep it clean. Yichao will be updating the bug reports with new patches. I'll help review and land them but I really encourage others to help review. -- George Staikos Torch Mobile Inc. http://www.torchmobile.com/ ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
