Hey all,
this is a belated announcement of the meta name=referrer feature. It
allows web sites to specify different policies for sending referrers,
without resorting to ugly redirect hacks. This feature is currently a
proposal: http://wiki.whatwg.org/wiki/Meta_referrer
The implementation of the
What happens if this extra plumbing isn't one? Is the tag just ignored?
From: webkit-dev-boun...@lists.webkit.org [webkit-dev-boun...@lists.webkit.org]
on behalf of Jochen Eisinger [joc...@chromium.org]
Sent: Tuesday, March 06, 2012 10:58 AM
To: WebKit
On Tue, Mar 6, 2012 at 5:31 PM, Joe Mason jma...@rim.com wrote:
What happens if this extra plumbing isn't one? Is the tag just ignored?
The ResourceRequest objects generated by WebCore will contain the correct
header according to the referrer policy, e.g. if you click on a link, the
generated
Yes, thank you.
From: eisin...@google.com [eisin...@google.com] on behalf of Jochen Eisinger
[joc...@chromium.org]
Sent: Tuesday, March 06, 2012 11:38 AM
To: Joe Mason
Cc: WebKit Development
Subject: Re: [webkit-dev] Adding meta name=referrer to WebCore
On Wednesday 08 February 2012 13:50:54 Milian Wolff wrote:
Hello!
Ping? Could someone be so kind as to answer my questions below?
Thanks
I am interested in improving WebKits printing capabilities. Especially a way
to define headers and footers would be most welcome. The CSS3 Paged Media
Hi,
A few of us have recently discovered that Xcode 4.3 for Lion (installed now
through the App Store rather than from a dmg) does not include by default the
command line tools required by the webkit build scripts. I've logged a bug and
submitted a patch to update the 'Installing Developer
it should work exactly the same way. If it doesn't, please let me know :)
Or, use garden-o-matic, which is more friendly and better for nearly
every purpose.
Cheers,
-- Dirk
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
Hello all,
We are still working on WG approval, but have submitted the proposal for
changes to the notifications spec, based on our previous discussions. I hope we
can get consensus and update the spec promptly.
In the meantime I will begin to file bugs under
In preparation for moving the WTF code out of JavaScriptCore, support
for including WTF headers as JavaScriptCore.framework private
headers will shortly be removed:
#include JavaScriptCore/Unicode.h // No longer possible
#include wtf/unicode/Unicode.h // The proper way.
Similarly:
#include
Whoops, I forgot to mention this also:
I would like to add a new ENABLE(LEGACY_NOTIFICATION_DEPRECATION) flag which
allows ports to deprecate the legacy API. This saves us from the hazards of
refactoring the code to use a different ENABLE flag for the legacy API, and
allows ports to opt-in
On Mar 6, 2012, at 9:00 PM, Jon Lee wrote:
Whoops, I forgot to mention this also:
I would like to add a new ENABLE(LEGACY_NOTIFICATION_DEPRECATION) flag which
allows ports to deprecate the legacy API. This saves us from the hazards of
refactoring the code to use a different ENABLE flag
On Wed, Feb 8, 2012 at 4:50 AM, Milian Wolff milian.wo...@kdab.com wrote:
I wonder, has anyone begun working on this? If not, I am willing to give it a
shot. I realize that this is a big task, and it will probably be hard for a
newcomer like me to do properly. Hence take this email also as a
12 matches
Mail list logo
