On Wed, Jun 29, 2011 at 1:01 PM, Geoffrey Garen gga...@apple.com wrote:
On Jun 28, 2011, at 5:15 PM, Dimitri Glazkov wrote:
On Tue, Jun 28, 2011 at 4:49 PM, Geoffrey Garen gga...@apple.com wrote:
Hi Dmitri.
Since this is an experimental API, here are the actual API names we want
to use:
I had the same idea a year ago, and got only negative feedback.
My main intention was/is the performance of the parser (see [1]). I improved
the performance of it a lot in the meantime (see dependencies of [2])
[2] tries to remove this UTF-8 - UTF-16 - UTF-8 overhead. The patch isn't
perfect at
29.06.2011, 07:42, TAMURA, Kent tk...@chromium.org:
I'm a little negative of developing a new XML parser. I'm afraid that the new
parser introduces a lot of security/stability problems which existing parsers
already resolved.
How about importing Expat parser to WebKit repository and
Do you have a master bug for them?
On Fri, Jun 24, 2011 at 12:16, Kenichi Ishibashi ba...@chromium.org wrote:
Hi webkit-dev,
I'm thinking about adding CSS3 font feature properties[1] support to
WebKit. It allows page authors to control over advanced typographic
features. Firefox has an
Hi,
On Wed, Jun 29, 2011 at 7:18 PM, TAMURA, Kent tk...@chromium.org wrote:
Do you have a master bug for them?
Not yet, but I'll make a master bug for them when I don't see a strong
objection.
On Fri, Jun 24, 2011 at 12:16, Kenichi Ishibashi ba...@chromium.orgwrote:
Hi webkit-dev,
I'm
On Jun 28, 2011, at 11:33 PM, Dominic Cooney wrote:
On Wed, Jun 29, 2011 at 1:01 PM, Geoffrey Garen gga...@apple.com wrote:
On Jun 28, 2011, at 5:15 PM, Dimitri Glazkov wrote:
On Tue, Jun 28, 2011 at 4:49 PM, Geoffrey Garen gga...@apple.com wrote:
Hi Dmitri.
Since this is an
On Jun 29, 2011, at 2:13 AM, Konstantin Tokarev wrote:
29.06.2011, 07:42, TAMURA, Kent tk...@chromium.org:
I'm a little negative of developing a new XML parser. I'm afraid that the
new parser introduces a lot of security/stability problems which existing
parsers already resolved.
How
On Tue, Jun 28, 2011 at 6:41 PM, Jeffrey Pfau jp...@apple.com wrote:
See responses inline:
On Jun 28, 2011, at 6:26 PM, Adam Barth wrote:
A question and a comment:
1) Will this let us to remove the code for both the libxml2 and the
QtXml parsers? I'd certainly much rather have one XML
On Wed, Jun 29, 2011 at 7:35 PM, Maciej Stachowiak m...@apple.com wrote:
On Jun 28, 2011, at 11:33 PM, Dominic Cooney wrote:
On Wed, Jun 29, 2011 at 1:01 PM, Geoffrey Garen gga...@apple.com wrote:
On Jun 28, 2011, at 5:15 PM, Dimitri Glazkov wrote:
On Tue, Jun 28, 2011 at 4:49 PM,
On Tue, Jun 28, 2011 at 6:50 PM, Eric Seidel e...@webkit.org wrote:
I'm in general in favor of this effort (having worked extensively on
the existing XML parsers).
But I would caution you that xml is a ridiculously tiny fraction of
the web. And it may not be worth the engineering effort to
On Wed, Jun 29, 2011 at 3:39 AM, Maciej Stachowiak m...@apple.com wrote:
Both RapidXml and Expat apparently have not been updated in quite some time
(since 2009 and 2007 respectively). Copying an unmaintained project into the
WebKit repository and forking it is certainly a possible
On Wed, Jun 29, 2011 at 6:49 AM, Dominic Cooney domin...@chromium.org wrote:
On Wed, Jun 29, 2011 at 7:35 PM, Maciej Stachowiak m...@apple.com wrote:
On Jun 28, 2011, at 11:33 PM, Dominic Cooney wrote:
On Wed, Jun 29, 2011 at 1:01 PM, Geoffrey Garen gga...@apple.com wrote:
On Jun 28,
On Wed, Jun 29, 2011 at 5:01 AM, Geoffrey Garen gga...@apple.com wrote:
On Jun 28, 2011, at 5:15 PM, Dimitri Glazkov wrote:
On Tue, Jun 28, 2011 at 4:49 PM, Geoffrey Garen gga...@apple.com
wrote:
Hi Dmitri.
Since this is an experimental API, here are the actual API names we
want to
On Tue, Jun 28, 2011 at 10:10 PM, Dirk Schulze k...@webkit.org wrote:
Am 29.06.2011 um 05:42 schrieb TAMURA, Kent:
I'm a little negative of developing a new XML parser. I'm afraid that the
new parser introduces a lot of security/stability problems which existing
parsers already resolved.
On Wed, 29 Jun 2011 06:55:57 -0700, Alex Milowski a...@milowski.org
wrote:
I know the parser's speed is terrible as I've measured it recently.
This is partially due to some of the things we are doing to deal with
Unicode decoding to work around libxml2 issues. I think moving to
native strings
On Wed, Jun 29, 2011 at 7:18 AM, par...@paroga.com wrote:
On Wed, 29 Jun 2011 06:55:57 -0700, Alex Milowski a...@milowski.org
wrote:
I know the parser's speed is terrible as I've measured it recently.
This is partially due to some of the things we are doing to deal with
Unicode decoding to
On Wed, Jun 29, 2011 at 3:35 AM, Maciej Stachowiak m...@apple.com wrote:
On Jun 28, 2011, at 11:33 PM, Dominic Cooney wrote:
On Wed, Jun 29, 2011 at 1:01 PM, Geoffrey Garen gga...@apple.com wrote:
On Jun 28, 2011, at 5:15 PM, Dimitri Glazkov wrote:
On Tue, Jun 28, 2011 at 4:49 PM, Geoffrey
Dear Martin,
Thanks a lot for your prompt response.
Now I am trying to build WebKit-GTK port on X11 using CygWin on Windows. I
will try to load my plug-ins with the help of new set-up. Is this the
right approach?
Or is it possible that just for plugin I will open XP_UNIX flag, compile it
and
On Wed, Jun 29, 2011 at 6:55 AM, Alex Milowski a...@milowski.org wrote:
On Tue, Jun 28, 2011 at 6:50 PM, Eric Seidel e...@webkit.org wrote:
I'm in general in favor of this effort (having worked extensively on
the existing XML parsers).
But I would caution you that xml is a ridiculously
On Tue, Jun 28, 2011 at 6:12 PM, Jeffrey Pfau jp...@apple.com wrote:
Currently, WebCore uses libxml2, or, if available, QtXml to parse incoming
XML. However, QtXml isn't always available, and using libxml2 exposes its own
share of problems. As such, I'm undertaking writing an XML parser that
Hi;
On Wed, Jun 29, 2011 at 3:12 AM, Jeffrey Pfau jp...@apple.com wrote:
Currently, WebCore uses libxml2, or, if available, QtXml to parse incoming
XML. However, QtXml isn't always available, and using libxml2 exposes its
own share of problems. As such, I'm undertaking writing an XML parser
I think considerable effort should be put into building up a suite of
performance tests in advance of the new parser (probably culled from xml
encountered in the wild, but also a number of extreme edge cases wouldn't go a
miss either).
We should also put effort into reducing any/all recursion
For what it's worth, we've got an extremely primitive XML parser
PerformanceTest already:
http://trac.webkit.org/browser/trunk/PerformanceTests/Parser/xml-parser.html
Adam
On Wed, Jun 29, 2011 at 9:22 AM, Oliver Hunt oli...@apple.com wrote:
I think considerable effort should be put into
On Wed, Jun 29, 2011 at 10:01 AM, Adam Barth aba...@webkit.org wrote:
For what it's worth, we've got an extremely primitive XML parser
PerformanceTest already:
http://trac.webkit.org/browser/trunk/PerformanceTests/Parser/xml-parser.html
I also have some tests I could post as a patch.
--
On 29 June 2011 01:10, Dirk Schulze k...@webkit.org wrote:
Am 29.06.2011 um 05:42 schrieb TAMURA, Kent:
I'm a little negative of developing a new XML parser. I'm afraid that the
new parser introduces a lot of security/stability problems which existing
parsers already resolved.
I feel the
On Jun 29, 2011, at 7:14 AM, Alex Milowski wrote:
On Tue, Jun 28, 2011 at 10:10 PM, Dirk Schulze k...@webkit.org wrote:
Am 29.06.2011 um 05:42 schrieb TAMURA, Kent:
I'm a little negative of developing a new XML parser. I'm afraid that the
new parser introduces a lot of
Thanks Adam!
I've filed an Enhancement with Apple: Bug ID# 9697244.
-Paul
-Original Message-
From: aba...@gmail.com [mailto:aba...@gmail.com] On Behalf Of
Adam Barth
Sent: June 28, 2011 1:28 PM
To: Mossman, Paul (Paul)
Cc: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev]
28.06.2011, в 8:39, Mossman, Paul (Paul) написал(а):
Can this behaviour be implemented in WebKit as the resolution to issue 41419?
Which of the below most accurately describes what you would like implemented?
Some of these would actually be WebKit issues.
1. If the user has already accepted
Hi Alexey,
Definitely #1 - same certificate, same domain, and same port.
-Paul
From: Alexey Proskuryakov [mailto:a...@webkit.org]
Sent: June 29, 2011 2:03 PM
To: Mossman, Paul (Paul)
Cc: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Unverified cert:
From: webkit-dev-boun...@lists.webkit.org
[mailto:webkit-dev-boun...@lists.webkit.org] On Behalf Of Alexey Proskuryakov
Sent: Wednesday, June 29, 2011 2:03 PM
To: Mossman, Paul (Paul)
Cc: webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] Unverified cert: Allow wss:// if user has
29.06.2011, в 11:30, Nick Guenther написал(а):
5. As the only good use for invalid certificates is development, there
should be an option in browser's Development menu to disable certificate
checks, perhaps until browser restart or just in current window. We don't
want users to make the
Hi Dimitri,
First of all, nice work on getting to this point!
It is not clear to me why we wouldn't stick with XBL2 for now, at least until
there is more community consensus on going another way, and a spec and editor
are available to take the API forward. I think it would help if you could
32 matches
Mail list logo
