On Mon, Jun 1, 2009 at 8:29 PM, Jeremy Orlow jor...@chromium.org wrote:
If this is the only issue, the parsing code could work around it. There are
3 parts to the identifier: the protocol (should never have a _ in it,
right?), the domain, and the port (once again, should never have a _). It
On Mon, Jun 1, 2009 at 11:30 PM, Adam Barth aba...@webkit.org wrote:
On Mon, Jun 1, 2009 at 8:29 PM, Jeremy Orlow jor...@chromium.org wrote:
If this is the only issue, the parsing code could work around it. There
are
3 parts to the identifier: the protocol (should never have a _ in it,
FYI: https://bugs.webkit.org/show_bug.cgi?id=26143
On Tue, Jun 2, 2009 at 12:45 AM, Jeremy Orlow jor...@chromium.org wrote:
On Mon, Jun 1, 2009 at 11:30 PM, Adam Barth aba...@webkit.org wrote:
On Mon, Jun 1, 2009 at 8:29 PM, Jeremy Orlow jor...@chromium.org wrote:
If this is the only issue,
I have 2 questions about SecurityOrigins.
First of all, in SecurityOrigin::databaseIdentifier() (in
http://trac.webkit.org/browser/trunk/WebCore/page/SecurityOrigin.h) the
following comment appears: Serialize the security origin for storage in the
database. This format is deprecated and should
Hi Jeremy,
Some of this has evolved and could likely be cleaned up.
2009/6/1 Jeremy Orlow jor...@chromium.org:
First of all, in SecurityOrigin::databaseIdentifier() (in
http://trac.webkit.org/browser/trunk/WebCore/page/SecurityOrigin.h) the
following comment appears: Serialize the security
On Mon, Jun 1, 2009 at 3:50 PM, Jeremy Orlow jor...@chromium.org wrote:
I have 2 questions about SecurityOrigins.
First of all, in SecurityOrigin::databaseIdentifier() (in
http://trac.webkit.org/browser/trunk/WebCore/page/SecurityOrigin.h) the
following comment appears: Serialize the
6 matches
Mail list logo
