Re: [webkit-dev] Removing support for the -khtml- (and -apple-?) vendor prefixes
On Mon, Jul 12, 2010 at 22:28, David Hyatt hy...@apple.com wrote: On Jul 12, 2010, at 12:09 PM, Maciej Stachowiak wrote: The reason for these is historical. Originally, we didn't use a separate vendor prefix for WebKit, just -khtml. Later we changed to -apple. That's not quite right. Originally we just had -khtml- for CSS extensions, and then we used -apple- for features that we were Apple-specific, i.e., that we knew nobody else would care about. Those features include Dashboard regions and Safari RSS line clamping). Eventually we just decided to merge both into a common prefix, but we wanted to keep the old property names working for compatibility. It was convenient to just map both to -webkit- rather than actually checking the specific property names and only supporting either -khtml- or -apple-. My recommendation would be as follows: (1) Drop support for -khtml- completely. (2) Continue to support -apple- for -apple-dashboard-region and -apple-line-clamp only. dave (hy...@apple.com) I have submitted a patch[1] following your recommendations. Regards, Peter Beverloo [1] https://bugs.webkit.org/show_bug.cgi?id=42093 ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application
Hi, I have asked this same question in (wha...@lists.whatwg.org), but haven't got many responses, so I want to ask here again. In spec HTML5 for offline web application (http://www.whatwg.org/specs/web-apps/current-work/#offline) chapter 6.6.6, item 3, 4, 5 state that for resources that is in online whitelist (or has wildcard whitelist), or fallback list, it should be fetched “normally”. I would like to know does it mean the user agent (browser) should bypass its own caches (besides html5 appcache), like the WebKit cache and browser http stack cache? If we don't, like WebKit (and Opera) doing now, once browser starts with network connection, it won't detect network connection loss, which happened not that common for a PC but common for a mobile device. And it will effectively defeat the intention of fallback resources in a offline web application, as the content for a fallback namespace from cache will be used, instead of the content of its mapping fallback entry. Best Regards Lyon Chen - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application
Sorry I forgot to mention I have reported a bug (https://bugs.webkit.org/show_bug.cgi?id=42051) for this. -Original Message- From: webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Lianghui Chen Sent: Tuesday, July 13, 2010 11:15 AM To: webkit-dev@lists.webkit.org Subject: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application Hi, I have asked this same question in (wha...@lists.whatwg.org), but haven't got many responses, so I want to ask here again. In spec HTML5 for offline web application (http://www.whatwg.org/specs/web-apps/current-work/#offline) chapter 6.6.6, item 3, 4, 5 state that for resources that is in online whitelist (or has wildcard whitelist), or fallback list, it should be fetched “normally”. I would like to know does it mean the user agent (browser) should bypass its own caches (besides html5 appcache), like the WebKit cache and browser http stack cache? If we don't, like WebKit (and Opera) doing now, once browser starts with network connection, it won't detect network connection loss, which happened not that common for a PC but common for a mobile device. And it will effectively defeat the intention of fallback resources in a offline web application, as the content for a fallback namespace from cache will be used, instead of the content of its mapping fallback entry. Best Regards Lyon Chen - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application
(b) Revalidating cached items once their freshness lifetime expires. But this will create dependence on the http stack cache implementation? And for some hosting services, the site might not allow the web application to change the http headers in the response? -Original Message- From: Maciej Stachowiak [mailto:m...@apple.com] Sent: Tuesday, July 13, 2010 11:41 AM To: Lianghui Chen Cc: webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application On Jul 13, 2010, at 8:14 AM, Lianghui Chen wrote: Hi, I have asked this same question in (wha...@lists.whatwg.org), but haven't got many responses, so I want to ask here again. In spec HTML5 for offline web application (http://www.whatwg.org/specs/web-apps/current-work/#offline) chapter 6.6.6, item 3, 4, 5 state that for resources that is in online whitelist (or has wildcard whitelist), or fallback list, it should be fetched normally. I would like to know does it mean the user agent (browser) should bypass its own caches (besides html5 appcache), like the WebKit cache and browser http stack cache? As the spec is currently written, I think the browser should not bypass its own caches. Other caches should have their normal behavior, and will revalidate once the freshness lifetime of the resource expires. If we don't, like WebKit (and Opera) doing now, once browser starts with network connection, it won't detect network connection loss, which happened not that common for a PC but common for a mobile device. And it will effectively defeat the intention of fallback resources in a offline web application, as the content for a fallback namespace from cache will be used, instead of the content of its mapping fallback entry. Clients have other ways to detect loss of connection: (a) platform-specific APIs that track the state of network interfaces. (b) Revalidating cached items once their freshness lifetime expires. That being said, if you think there is a problem with the spec, you should report it to the W3C Web Apps WG or the WHATWG. Regards, Maciej - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application
13.07.2010, в 9:21, Lianghui Chen написал(а): And actually there's another small issue to leave the browser or webkit cache to do the revalidation of the freshness: when it's offline they just cannot do it, and it will quite possibly return the expired resource. So when it's offline, we will always get the fallback namespace item instead of its mapping fallback entry, until the cache is cleared. As I mentioned in the bug, the resource can be served with pragma no- store. In that case, there will be no expired resource in the cache. If a hosting service doesn't allow .htaccess or any kind of CGI scripts, it's pretty much unsuitable for serving offline applications anyway, since one needs a custom content type for the manifest. - WBR, Alexey Proskuryakov ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application
As I mentioned in the bug, the resource can be served with pragma no- store. In that case, there will be no expired resource in the cache. Will WebKit cache respect the cache-controls in http headers? -Original Message- From: Alexey Proskuryakov [mailto:a...@webkit.org] Sent: Tuesday, July 13, 2010 12:27 PM To: Lianghui Chen Cc: Maciej Stachowiak; webkit-dev@lists.webkit.org Subject: Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application 13.07.2010, в 9:21, Lianghui Chen написал(а): And actually there's another small issue to leave the browser or webkit cache to do the revalidation of the freshness: when it's offline they just cannot do it, and it will quite possibly return the expired resource. So when it's offline, we will always get the fallback namespace item instead of its mapping fallback entry, until the cache is cleared. As I mentioned in the bug, the resource can be served with pragma no- store. In that case, there will be no expired resource in the cache. If a hosting service doesn't allow .htaccess or any kind of CGI scripts, it's pretty much unsuitable for serving offline applications anyway, since one needs a custom content type for the manifest. - WBR, Alexey Proskuryakov - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] About bypassing caches for URLs listed in Fallback and/or Network section in a HTML5 Offline Web Application
13.07.2010, в 9:55, Lianghui Chen написал(а): Will WebKit cache respect the cache-controls in http headers? Yes. - WBR, Alexey Proskuryakov ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Debugging Webkit?
I don't have answers for you. But the information should be added to: http://webkit.org/building/debug.html or http://trac.webkit.org/wiki/QtWebKit once found. :) -eric On Tue, Jul 13, 2010 at 7:22 PM, Yuchen Zhou yz...@virginia.edu wrote: Hi all- I am newbie to webkit dev and I am trying to debug Webkit with gdb. I tried to build the Qtwebkit with ./build-webkit --debug --qt, and then gdb WebKitBuild/Debug/bin/QtTestBrowser, however seems gdb was not able to add breakpoints for class::functions. It cannot find them. I wonder what is the debugging process for Qtwebkit. Thanks all, 2010-07-13 Yuchen ___ 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] Debugging Webkit?
See http://www.mail-archive.com/webkit-h...@lists.webkit.org/msg00659.html -- Ariya Hidayat http://www.linkedin.com/in/ariyahidayat ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Debugging Webkit?
I once also had issues setting break points inside WebCore. Gdb claimed the break points have been set but the source code showing up after hitting the break point always messed up. The problem was resolved by updating my ubuntu to latest version (10.4LTS). I am not sure if this is the same problem you have. Another tip is to check the size of your webcore.dll. It should be huge. Hopefully it helps. Chang From: webkit-dev-boun...@lists.webkit.org [mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of ext Chinmaya Sn Sent: Tuesday, July 13, 2010 10:09 PM To: Yuchen Zhou Cc: webkit-dev Subject: Re: [webkit-dev] Debugging Webkit? Try This 1. As you already did run ./buid-webkit --debug --qt 2. cd WEBKIT_DIR/WebKitBuild/Debug/bin 3. Assuming you have WEBKIT_DIR/WebCore , WEBKIT_DIR/WebKit source directories try $ gdb -cd . -d ../../../ --args ./QtLauncher args-to-QtLauncher 4. Now at gdb prompt (gdb) break main # to add breakpoint to main function (gdb) break WebCore::FrameLoader::init # make sure you use fully-qualified namespace Alternatively 1. same as above 2. same as above 3. Create a text file with gdb commands $ cat EOF commands.txt start break main break WebCore::FrameLoader::init continue EOF 4. run gdb as $ gdb -x comands.txt -d ../../../ -cd . --args ./QtLauncher Qt comes with (std distribution) with gdb 6.8 or something, if you gdb 7.01 or above you will be able to leverage some of the python gdb scripts distributed with WebKit See this WEBKIT_DIR/WebKitTools/gdb/webcore.py -- Chinmaya On Tue, Jul 13, 2010 at 8:22 PM, Yuchen Zhou yz...@virginia.edumailto:yz...@virginia.edu wrote: Hi all- I am newbie to webkit dev and I am trying to debug Webkit with gdb. I tried to build the Qtwebkit with ./build-webkit --debug --qt, and then gdb WebKitBuild/Debug/bin/QtTestBrowser, however seems gdb was not able to add breakpoints for class::functions. It cannot find them. I wonder what is the debugging process for Qtwebkit. Thanks all, 2010-07-13 Yuchen ___ webkit-dev mailing list webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev -- -- chinmaya sn ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
