Re: [webkit-dev] Do we need a "webkitBackground" property for XMLHttpRequest?

dialog from XHR. It's possible they ran into compat trouble or that it was an oversight. Adam > On 07/24/2012 11:52 PM, Brady Eidson wrote: >> On Jul 24, 2012, at 2:58 AM, Adam Barth wrote: >> >>> I don't think we should add this property. Instead we sho

Re: [webkit-dev] Do we need a "webkitBackground" property for XMLHttpRequest?

I don't think we should add this property. Instead we should not ever present HTTP auth dialogs for any requests other than the main resource for the top-level frame. Presenting HTTP auth dialogs in other contexts is a phishing risk. Adam On Tue, Jul 24, 2012 at 2:47 AM, xuewen wrote: > > Whe

Re: [webkit-dev] WebKit memory instrumentation

Is there no way to use the sizeof operator to help? That might not help if we restructure the data, but it would at least help us track the size of individual objects. Adam On Mon, Jul 23, 2012 at 8:09 AM, Yury Semikhatsky wrote: > *Hi WebKit, > > Almost all developers would like to know why t

Re: [webkit-dev] About WebIDL supplemental interfaces

f returning a Region interface for those pseudo-elements that have > been added to the region chain. > > Alan > > On 7/19/12 10:50 AM, "Adam Barth" wrote: > >>What else can become a region besides an element? If there aren't too >>many interfaces, we c

Re: [webkit-dev] About WebIDL supplemental interfaces

seemed the best way to solve them was > making Region supplemental for Element and any other object that could > become region. Right now, I'm feeling out the situation to see how feasible > this is to be implemented in WebKit. > > Andrei. > > From: Adam Barth > Date: Thur

[webkit-dev] Update on the chromium-android port

Hi WebKit, I wanted to give you an update on the progress of the chromium-android port. It's been almost a year since Andrei Popescu announced that we were refactoring the Android port to be based on Chromium: < http://lists.webkit.org/pipermail/webkit-dev/2011-August/017738.html>. Since, then w

Re: [webkit-dev] About WebIDL supplemental interfaces

On Thu, Jul 19, 2012 at 9:29 AM, Andrei Bucur wrote: > Hey Kentaro, > > On 7/19/12 6:20 PM, "Kentaro Hara" wrote: > > >Hi Andrei > > > >> I'm asking this because CSS Regions spec defines the Region interface > >>as an > >> WebIDL supplemental interface that needs to be implemented by any object

Re: [webkit-dev] Updates on Chromium's content_shell

On Mon, Jul 16, 2012 at 9:25 AM, Darin Fisher wrote: > On Mon, Jul 16, 2012 at 2:57 AM, Jochen Eisinger wrote: > >> On Fri, Jul 13, 2012 at 11:15 PM, Darin Fisher wrote: >> >>> On Fri, Jul 13, 2012 at 2:10 PM, Adam Barth wrote: >>> >>>> Yeah, Ev

Re: [webkit-dev] Updates on Chromium's content_shell

On Fri, Jul 13, 2012 at 2:24 PM, Adam Barth wrote: > On Fri, Jul 13, 2012 at 2:15 PM, Darin Fisher wrote: > >> On Fri, Jul 13, 2012 at 2:10 PM, Adam Barth wrote: >> >>> Yeah, EventSender is likely a good place to start. Here are some more >>> details about

Re: [webkit-dev] Updates on Chromium's content_shell

On Fri, Jul 13, 2012 at 2:15 PM, Darin Fisher wrote: > On Fri, Jul 13, 2012 at 2:10 PM, Adam Barth wrote: > >> Yeah, EventSender is likely a good place to start. Here are some more >> details about what I had in mind: >> >> 1) We'll need to create a new ta

Re: [webkit-dev] Updates on Chromium's content_shell

ere, so others that might want to join > the effort later can read it up? > > In general, I agree with your proposal. I guess starting with something > small like EventSender might be a good first step. > > best > -jochen > > > On Fri, Jul 13, 2012 at 10:20 PM, Adam Barth

Re: [webkit-dev] Updates on Chromium's content_shell

On Fri, Jul 13, 2012 at 1:10 PM, Jochen Eisinger wrote: > On Fri, Jul 13, 2012 at 7:46 PM, Ryosuke Niwa wrote: > >> On Fri, Jul 13, 2012 at 4:16 AM, Jochen Eisinger wrote: >> >>> I wanted to share some updates about content_shell (a multi-processed >>> version of chromium's test shell): meanwhile

Re: [webkit-dev] cr-linux-ews migration

The cr-linux-ews migration seems to have gone well. I'm now migrating the commit-queue. Please let me know if you notice any problems. Thanks! Adam On Mon, Jul 2, 2012 at 12:32 AM, Adam Barth wrote: > Hi webkit-dev, > > I've moved the cr-linux-ews from EC2 to Google Comp

Re: [webkit-dev] Web APIs and class name collisions

One common thing we do is prefix "DOM" to DOM-level concepts. For example, DOMWindow and DOMFileSystem. I'm not sure if we have an established convention for CSS-level concepts. Adam On Thu, Jul 12, 2012 at 9:18 AM, Andrei Bucur wrote: > Hello Webkittens! > > While implementing the Region in

Re: [webkit-dev] C++ unit tests for WebKit?

rage. I'm happy to discuss this topic further in #webkit if that would be helpful to you. Adam > From: Adam Barth > To: Hans Muller > Cc: Benjamin Poulain , Konrad Piascik < > kpias...@rim.com>, webkit-dev > Subject: Re: [webkit-dev] C++ unit tests for WebKit? > &g

Re: [webkit-dev] C++ unit tests for WebKit?

Generally speaking, WebKit's testing philosophy is to test at API boundaries, typically either a given port's WebKit API or the web platform API. The benefit of that approach is that it makes it easier for us to refactor the internals of WebCore without being constrained by fragile tests---only by

Re: [webkit-dev] New feature flag: ENABLE_CSS_POSITION_STICKY

Yes. Thanks for holding off for a bit. :) Adam On Wed, Jul 11, 2012 at 11:03 AM, Simon Fraser wrote: > I think we've resolved our differences around the fixed position scrolling > issues, so that's OK. > > Simon > > On Jun 27, 2012, at 6:38 PM, Adam Barth wrote:

Re: [webkit-dev] Removing BUILDING_ON / TARGETING macros in favor of system availability macros

Tony and Mark (Mentovai) would know more, but I believe the Chromium port uses these macros in order to build against a specific SDK. For example, the Chromium port currently builds against the 10.5 SDK. (This is slated to change shortly as the Chromium project has dropped support for 10.5.) Ada

Re: [webkit-dev] iOS parsing of the viewport meta tag

On Tue, Jul 10, 2012 at 9:16 AM, David Kilzer wrote: > On Jul 10, 2012, at 8:48 AM, Adam Barth wrote: >> Parse the viewport meta tag like iOS >> https://bugs.webkit.org/show_bug.cgi?id=72722 >> >> Is the parsing code for the viewport meta tag in iOS ope

[webkit-dev] iOS parsing of the viewport meta tag

Hi webkit-dev, I'm working on the following bug: Parse the viewport meta tag like iOS https://bugs.webkit.org/show_bug.cgi?id=72722 Is the parsing code for the viewport meta tag in iOS open source? If not, would it be possible for someone from Apple with access to the source to contribute it to

Re: [webkit-dev] lineNumber() and textPosition() methods in HTMLDocumentParser

They can probably be combined. It's done this way because there are other subclasses of DocumentParser besides HTMLDocumentParser. I'm not sure it's a big deal either way. Adam On Tue, Jul 3, 2012 at 9:28 PM, KwangYul Seo wrote: > Hi. > > I have a question regarding HTMLDocumentParser. I foun

[webkit-dev] cr-linux-ews migration

Hi webkit-dev, I've moved the cr-linux-ews from EC2 to Google Compute Engine. In the process, I've doubled the capacity. If you notice anything wonky, please let me know. If this transition goes well, I'll move the commit-queue (and expand its capacity) as well. Happy hacking! Adam ___

Re: [webkit-dev] Let's use only 'ENABLE_CUSTOM_SCHEME_HANDLER' flag, and remove 'ENABLE_REGISTER_PROTOCOL_HANDLER' flag.

which is likely why Chromium has the feature disabled. Adam On Thu, Jun 28, 2012 at 8:06 AM, Adam Barth wrote: > According to > <http://trac.webkit.org/browser/trunk/Source/WebKit/chromium/features.gypi>, > Chromium currently enables REGISTER_PROTOCOL_HANDLER but not > CUSTOM

Re: [webkit-dev] Let's use only 'ENABLE_CUSTOM_SCHEME_HANDLER' flag, and remove 'ENABLE_REGISTER_PROTOCOL_HANDLER' flag.

According to , Chromium currently enables REGISTER_PROTOCOL_HANDLER but not CUSTOM_SCHEME_HANDLER. Until the Chromium project decides to ship CUSTOM_SCHEME_HANDLER, having two ENABLE flags is valuable. Please do not combi

Re: [webkit-dev] New feature flag: ENABLE_CSS_POSITION_STICKY

There seems to be some amount of controversy at the moment regarding how we should implement scrolling and fixed position elements. As long as that discussion doesn't drag on too long, we might want to let the dust settle a bit before moving forward with new features in this area. Adam On Tue,

Re: [webkit-dev] [PATCH] Errors from "build-webkit --debug --minimal"

Hopefully this email won't come off as rude, but it's not clear to me whether the WinCE port being actively developed. says that the port is maintained by Torch Mobile, but says Torch Mobile is focused on BlackBerry these days. Look

Re: [webkit-dev] Issue regarding Same Origin check with Blobs and XMLHttpRequest

[webkit-dev -> bcc] What URL are you trying to load? The error message doesn't say. I wonder if you're trying to load a relative URL, which is trying to be resolved relative to the blob URL. It might work better with an absolute URL. Adam On Thu, May 10, 2012 at 1:32 AM, Vishal Shah wrote:

Re: [webkit-dev] Feature announcement: Content-Security-Policy 1.1

On Sun, Jun 17, 2012 at 1:35 AM, Mike West wrote: > On Fri, May 4, 2012 at 3:13 AM, Adam Barth wrote: >> As CSP 1.1 matures (both in specification and >> implementation), I plan to upstream the csp11 branch using this meta >> bug: <https://bugs.webkit.org/show_bug.cgi?id=

Re: [webkit-dev] EditBugs permission

Done. Folks should feel free to ping me on #webkit rather than emailing webkit-dev abou this sort of thing. Adam On Fri, Jun 15, 2012 at 12:03 PM, Pablo Flouret wrote: > Hey, > > Could i get EditBugs for my bugzilla account? (pab...@motorola.com) > > I'm not a commiter, but i've contributed a

Re: [webkit-dev] IMAGE+TEXT WAS: TestExpectations syntax changes, last call (for a while, at least) ...

On Thu, Jun 14, 2012 at 9:02 PM, Ojan Vafai wrote: > On Thu, Jun 14, 2012 at 9:00 PM, Adam Barth wrote: >> >> On Thu, Jun 14, 2012 at 8:56 PM, Ojan Vafai wrote: >> > On Thu, Jun 14, 2012 at 4:34 PM, Dirk Pranke >> > wrote: >> >> On Thu, Jun 14, 20

Re: [webkit-dev] IMAGE+TEXT WAS: TestExpectations syntax changes, last call (for a while, at least) ...

On Thu, Jun 14, 2012 at 8:56 PM, Ojan Vafai wrote: > On Thu, Jun 14, 2012 at 4:34 PM, Dirk Pranke wrote: >> On Thu, Jun 14, 2012 at 4:22 PM, Maciej Stachowiak wrote: >> > On Jun 14, 2012, at 1:47 PM, Ryosuke Niwa wrote: >> > On Thu, Jun 14, 2012 at 1:44 PM, Peter Kasting >> > wrote: >> >> >> >

Re: [webkit-dev] TestExpectations syntax changes, last call (for a while, at least) ...

On Thu, Jun 14, 2012 at 4:22 PM, Maciej Stachowiak wrote: > On Jun 14, 2012, at 1:47 PM, Ryosuke Niwa wrote: > On Thu, Jun 14, 2012 at 1:44 PM, Peter Kasting > wrote: >> On Thu, Jun 14, 2012 at 1:39 PM, Elliot Poger wrote: >>> Can someone please remind me why IMAGE+TEXT even exists? >>> >>> Wou

Re: [webkit-dev] TestExpectations syntax changes, last call (for a while, at least) ...

On Wed, Jun 13, 2012 at 5:49 PM, Dirk Pranke wrote: > On Wed, Jun 13, 2012 at 5:42 PM, Maciej Stachowiak wrote: >> On Jun 13, 2012, at 3:58 PM, Darin Adler wrote: >>> On Jun 13, 2012, at 3:53 PM, Dirk Pranke wrote: >>> * we use "\" (backslash) as a delimiter instead of ":" and "=" >>> >>>

Re: [webkit-dev] malloc(0)

There was some discussion about how to handle malloc(0) a year or so ago. I don't remember if it was on webkit-dev, but you might want to check the archives. Eric Seidel might remember what conclusions (if any) we came to. Adam On Tue, Jun 12, 2012 at 3:03 PM, Myles C. Maxfield wrote: > Hello

Re: [webkit-dev] Adding nonstandard features (was Re: Adding ENABLE_NAVIGATOR_BUILDTYPE to WebCore)

On Mon, Jun 11, 2012 at 6:29 PM, Maciej Stachowiak wrote: > On Jun 7, 2012, at 1:10 PM, Adam Barth wrote: >> On Thu, Jun 7, 2012 at 1:00 PM, Ryosuke Niwa wrote: >>> On Wed, Jun 6, 2012 at 1:51 PM, Annie Sullivan >>> wrote: >>>> >>>> I wa

Re: [webkit-dev] can we stop using Skipped files?

On Sun, Jun 10, 2012 at 4:54 AM, Balazs Kelemen wrote: > So the unit tests are superfluous. In particular, if I had to pick >> between only having unit tests or only having regression tests, I might >> pick unit tests. But if I already have regression tests then I'm unlikely >> to want to incur

Re: [webkit-dev] Adding ENABLE_NAVIGATOR_BUILDTYPE to WebCore

On Thu, Jun 7, 2012 at 1:00 PM, Ryosuke Niwa wrote: > On Wed, Jun 6, 2012 at 1:51 PM, Annie Sullivan > wrote: >> >> I wanted to let you know that I plan to add support for >> navigator.buildType (e.g., "nightly", "beta", "final") to WebKit. This >> feature isn't on the standards track (but neithe

Re: [webkit-dev] Adding ENABLE_NAVIGATOR_BUILDTYPE to WebCore

On Thu, Jun 7, 2012 at 12:53 PM, Annie Sullivan wrote: > On Thu, Jun 7, 2012 at 3:43 PM, Dean Jackson wrote: >> On 07/06/2012, at 12:05 PM, Annie Sullivan wrote: >>> In many browsers in the past, it's been >>> pretty easy to determine from "a" and "b" characters in the user agent >>> of many bro

Re: [webkit-dev] Adding ENABLE_NAVIGATOR_BUILDTYPE to WebCore

On Thu, Jun 7, 2012 at 11:48 AM, Konstantin Tokarev wrote: > > > 07.06.2012, 21:07, "Annie Sullivan" : >> Oops, forgot to reply-all. >> >> On Thu, Jun 7, 2012 at 9:05 AM, Annie Sullivan wrote: >> >>> On Wed, Jun 6, 2012 at 4:59 PM, Darin Adler wrote: Our past experience with this sort of

Re: [webkit-dev] EditBugs permissions for bugs.webkit.org account

Done. On Thu, Jun 7, 2012 at 8:35 AM, Simon Pena wrote: > Hi, > > I'd like to request EditBugs permissions to be added to my > bugs.webkit.org account (spena at igalia.com) > > I'm not a committer, but I have worked on several patches already, > mainly for the GTK port. > > Thanks in advance, > >

Re: [webkit-dev] Renaming DumpRenderTree to WebKitTestRunner or merging those two

On Mon, Jun 4, 2012 at 10:51 AM, Sam Weinig wrote: > On Jun 3, 2012, at 6:10 PM, Ryosuke Niwa wrote: > > On Sun, Jun 3, 2012 at 6:01 PM, Adam Barth wrote: > >> On Sun, Jun 3, 2012 at 5:54 PM, Ryosuke Niwa wrote: >> >>> On Sun, Jun 3, 2012 at 5:33 PM, Maciej St

Re: [webkit-dev] Renaming DumpRenderTree to WebKitTestRunner or merging those two

On Sun, Jun 3, 2012 at 5:54 PM, Ryosuke Niwa wrote: > On Sun, Jun 3, 2012 at 5:33 PM, Maciej Stachowiak wrote: >> >> On Jun 3, 2012, at 8:05 PM, Ryosuke Niwa wrote: >> >> On Sun, Jun 3, 2012 at 3:55 PM, Maciej Stachowiak wrote: >> >>> I am on vacation so I won't be able to review your patch in

Re: [webkit-dev] Renaming DumpRenderTree to WebKitTestRunner or merging those two

We might also want to define the layoutTestController object with IDL so we don't have to hand-write bindings every time we change it. Using IDL for window.internals seems to have worked out well. It would be nice to replicate that success with layoutTestController. Adam On Sat, Jun 2, 2012 at

[webkit-dev] Removing target-densitydpi (was Re: Device and page scaling)

rfect rendering on a given device. > > -Konrad > > From: webkit-dev-boun...@lists.webkit.org > [webkit-dev-boun...@lists.webkit.org] on behalf of Adam Barth > [aba...@webkit.org] > Sent: Friday, June 01, 2012 2:21 AM > To: Maciej Stachowiak > C

Re: [webkit-dev] Adding ENABLE_HTML_MEDIA_CAPTURE to WebCore

On Fri, Jun 1, 2012 at 2:39 AM, Anssi Kostiainen wrote: > Hi Adam, > On 10.5.2012, at 14.20, ext Anssi Kostiainen wrote: >> On 9.5.2012, at 23.22, ext Adam Barth wrote: >> >>> Thanks.  I just have two pieces of feedback: >>> >>> 1) As far as I know, we

Re: [webkit-dev] Device and page scaling

I've posted a patch to remove target-densitydpi: https://bugs.webkit.org/show_bug.cgi?id=88047 There's some concern that target-densitydpi is used by some apps that are bundled with Android, but folks appear willing to deprecate the feature and to migrate those apps to using other mechanisms, suc

Re: [webkit-dev] Settings::devicePixelRatio and Settings::defaultDeviceScaleFactor

ixelRatio() belongs in settings. It should be either >> be obtained from the platform code in WebCore/WebKit, or pushed in via API. >> >> Simon >> >> On May 31, 2012, at 3:48 PM, Adam Barth wrote: >> >> > Is there any difference between Settings::devicePixelR

[webkit-dev] Settings::devicePixelRatio and Settings::defaultDeviceScaleFactor

Is there any difference between Settings::devicePixelRatio [1] and Settings::defaultDeviceScaleFactor [2] ? They appear to be used by disjoint sets of ports. Shall we delete one in favor of the other? Adam [1] http://trac.webkit.org/browser/trunk/Source/WebCore/page/Settings.h#L478 [2] http://t

Re: [webkit-dev] [webkit-changes] [119113] trunk/Source/WebKit/gtk

+mrobinson Looks like the odd ChangeLog was in a patch uploaded by mrobinson: https://bugs.webkit.org/attachment.cgi?id=143171&action=review Adam On Thu, May 31, 2012 at 1:43 PM, Dan Bernstein wrote: > > > On May 31, 2012, at 9:36 AM, commit-qu...@webkit.org wrote: > > Revision119113Authorcom

Re: [webkit-dev] Device and page scaling

On Wed, May 30, 2012 at 12:08 AM, Kenneth Rohde Christiansen wrote: > I don't think we are doing that much differently. > > Desktop Safari is scaling directly in WebCore using the > pageScaleFactor whereas Qt like iOS scales outside of WebCore (using a > tiled backing store), resulting in the Fram

Re: [webkit-dev] Device and page scaling

how_bug.cgi?id=87407>. The short answer is that they will be keyed off of Page::deviceScaleFactor, which means they won't be affected by changes to the target-densitydpi. Adam > - Original Message - > From: Adam Barth [mailto:aba...@webkit.org] > Sent: Tuesday, May 29,

Re: [webkit-dev] Device and page scaling

On Tue, May 29, 2012 at 7:03 PM, Fady Samuel wrote: > This sounds good to me, but is there any reason why we can't support > physical device changes (switching monitors) and support target-densitydpi? > This would be highly desirable for us. We can support that. We just need to decide how to cha

[webkit-dev] Device and page scaling

There's a lot of confusion in the code base about how page and device scaling works. Different ports are using Page::deviceScaleFactor for incompatible purposes. On Mac, Page::deviceScaleFactor represents the actual scaling factor of the physical device. It can change over time because a given P

Re: [webkit-dev] Block 3rd part cookies implementation

This list is not the appropriate forum for your questions. Adam On May 29, 2012 11:39 AM, "Giorgio Mazzucchelli" wrote: > Is the mechanism of handling 3rd part cookies by WebKit documented > somewhere? Not directly referring to source code. > > > Giorgio > __

Re: [webkit-dev] Block 3rd part cookies implementation

On Tue, May 29, 2012 at 10:55 AM, Giorgio Mazzucchelli wrote: > Thank you for replying me and for your suggestions. > > Through trac, I a looking up for the class (not sure if technically speaking > is a class): > > FirstPartyForCookies > > It compares in many files: how to understand which one is

Re: [webkit-dev] Block 3rd part cookies implementation

On Tue, May 22, 2012 at 12:29 PM, Giorgio Mazzucchelli wrote: > Is Safari's privacy option, which allows users to block 3rd part cookies, > implemented in WebKit or in the browser itself? Any code reference would be > very helpful. Parts are implemented in WebKit and parts are implemented outsi

Re: [webkit-dev] A more detailed source tree overview

Unfortunately, the information in WebKitSourceLayout.md is much too detailed. It contains many facts that happen to be true at this moment, but are likely to change at any moment. It's unlikely that we'll keep this documentation up to date, which means it's just going to get stale and perhaps cau

Re: [webkit-dev] Regarding cr-linux bot and the test failure

Have you tried building Chromium locally? That's likely to be a tighter debugging loop than using the bot. There are instructions on the wiki: http://trac.webkit.org/wiki/Chromium Adam On Mon, May 14, 2012 at 3:18 AM, Vivek Galatage wrote: > Hello Webkit-dev, > > I am having issues with one

Re: [webkit-dev] spamming the developer console

On Fri, May 11, 2012 at 2:29 PM, Ojan Vafai wrote: > On Fri, May 11, 2012 at 2:25 PM, Adam Barth wrote: >> >> On Fri, May 11, 2012 at 2:21 PM, Ojan Vafai wrote: >> > The amount of spam we throw in the developer console has grown quite a >> > bit. >> >

Re: [webkit-dev] spamming the developer console

On Fri, May 11, 2012 at 2:21 PM, Ojan Vafai wrote: > The amount of spam we throw in the developer console has grown quite a bit. > > spam == things logged to the console that web developers have no control > over > > Unlike uncaught javascript exceptions (which can easily just be caught), > there

Re: [webkit-dev] Issue regarding Same Origin check with Blobs and XMLHttpRequest

Just to close the loop on this topic, I spoke with Vishal off-list and we figured out the problem. Thanks everyone. Adam On Thu, May 10, 2012 at 1:32 AM, Vishal Shah wrote: > Hello, > > I have implemented a web worker that handles XMLHttpRequest object for my > application > When I create a se

Re: [webkit-dev] Adding ENABLE_HTML_MEDIA_CAPTURE to WebCore

On Wed, May 9, 2012 at 1:12 PM, Anssi Kostiainen wrote: > On 9.5.2012, at 11.44, ext TAMURA, Kent wrote: > >> I wonder if the standardization is active.  Even the editor's draft has not >> been updated for one year. > > Good that you ask -- the spec has been waiting for implementors' feedback :)

Re: [webkit-dev] Adding ENABLE_HTML_MEDIA_CAPTURE to WebCore

That's a good question. I happened upon this feature because it's implemented in Chrome on Android, and we want to fully merge Chrome on Android's WebKit with upstream. Adam On Wed, May 9, 2012 at 1:44 AM, TAMURA, Kent wrote: > I wonder if the standardization is active.  Even the editor's draf

Re: [webkit-dev] Adding ENABLE_HTML_MEDIA_CAPTURE to WebCore

Jongseok Yang. > > > > --- Original Message --- > Sender : Adam Barth > Date : 2012-02-20 13:57 (GMT+09:00) > Title : Re: [webkit-dev] Adding ENABLE_HTML_MEDIA_CAPTURE to WebCore > > How does this feature relate to WebRTC ? > > Adam > > > On Sun, Feb 1

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

vendor prefixes > To: Adam Barth > Cc: Alexey Proskuryakov , webkit-dev@lists.webkit.org > > > On Fri, Apr 6, 2012 at 4:27 PM, Adam Barth wrote: >> >> 2012/4/5 Alexey Proskuryakov : >> > 05.04.2012, в 01:08, Adam Barth написал(а): >> > >> >> Ba

[webkit-dev] Feature announcement: Content-Security-Policy 1.1

Hi webkit-dev, Content-Security-Policy 1.0 is nearing Working Group Last Call in the W3C WebAppSec working group. Over the next few weeks, I'm going to polish up our implementation of CSP 1.0 to match the final specification. Our implementation is quite close to the spec, so these changes should

Re: [webkit-dev] Feature Announcement: Adding

On Wed, May 2, 2012 at 12:11 PM, Maciej Stachowiak wrote: > On May 2, 2012, at 11:48 AM, Jarred Nicholls wrote: > On Wed, May 2, 2012 at 2:03 PM, Maciej Stachowiak wrote: >> On May 2, 2012, at 6:14 AM, Jarred Nicholls wrote: >> On Tue, May 1, 2012 at 7:39 PM, Maciej Stachowiak wrote: >>> I'm n

[webkit-dev] Maciej's prefixing questions (was Re: webkitPostMessage)

On Sun, Apr 29, 2012 at 7:33 PM, Maciej Stachowiak wrote: > In the longer term, here's a few things we should think about: > > - Historically, we've almost never removed prefixed versions of features that > get promoted to unprefixed. The marginal maintenance cost is low and there's > usually so

Re: [webkit-dev] Feature Announcement: Adding

On Tue, May 1, 2012 at 3:50 PM, Maciej Stachowiak wrote: > On May 1, 2012, at 3:31 PM, Eric Seidel wrote: >> Is your goal to be able to disable the feature to prevent a late-known >> security issue? >> >> Or is your goal to universally disable seamless for a port entirely? > > I'm not sure I unde

Re: [webkit-dev] webkitPostMessage

On Sun, Apr 29, 2012 at 2:25 PM, Maciej Stachowiak wrote: > > On Apr 29, 2012, at 1:35 PM, Adam Barth wrote: > > > There is very little cost on the WebKit project to maintain > webkitPostMessage in addition to postMessage. Instead, supporting > webkitPostMessage impo

Re: [webkit-dev] webkitPostMessage

On Sun, Apr 29, 2012 at 1:06 PM, Maciej Stachowiak wrote: > > On Apr 29, 2012, at 12:53 PM, Ryosuke Niwa wrote: > > On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak wrote: > >> On Apr 29, 2012, at 11:01 AM, Adam Barth wrote: >> >> I read <https://trac

Re: [webkit-dev] webkitPostMessage

On Sun, Apr 29, 2012 at 12:34 PM, Maciej Stachowiak wrote: >On Apr 29, 2012, at 11:01 AM, Adam Barth wrote: >> I read <https://trac.webkit.org/wiki/DeprecatingFeatures>, but I'm >> still unsure how to proceed with removing webkitPostMessage and >> aligning po

Re: [webkit-dev] webkitPostMessage

with the > spec behavior, but if you wish to try this, I don't know of any big reason > not to. Ok, I'll make these changes in separate patches in case either causes trouble down the line. Thanks! Adam > On Sun, Apr 29, 2012 at 11:01 AM, Adam Barth wrote: >> >>

Re: [webkit-dev] webkitPostMessage

2012 at 9:08 PM, Adam Barth wrote: > I'm trying to understand why we have both DOMWindow.webkitPostMessage > and DOMWindow.postMessage.  I'm also trying to understand the > following comment in {JS,V8}DOMWindowCustom.cpp: > >    // This function has variable argum

Re: [webkit-dev] github mirror

Tor, I think we should retire the author rewriting script on GitHub. Jame's is right that there's a lot of value in having git.webkit.org and GitHub using the same hashes. For example, both Eric and Gavin requested that when they started using GitHub. We would have some trouble adopting the aut

Re: [webkit-dev] Using GitHub to Contribute to WebKit (Experimental)

On Tue, Apr 24, 2012 at 6:14 AM, Adam Roben wrote: > On Fri, Mar 16, 2012 at 5:40 PM, Adam Barth wrote: >> >> On Fri, Mar 16, 2012 at 2:32 PM, Ryosuke Niwa wrote: >> > Can we do some Bugzilla integration as Jarred suggested? >> >> If you're excited about

Re: [webkit-dev] webkitPostMessage

[+dslomov] I found a thread on public-webapps that seems related to this question. Dmitry, do you know what current status is here? I'd like to make sure we're on a path towards interoperability with other browsers. Thanks, Adam On Tue, Apr 10, 2012 at 9:08 PM, Adam Barth wr

[webkit-dev] webkitPostMessage

I'm trying to understand why we have both DOMWindow.webkitPostMessage and DOMWindow.postMessage. I'm also trying to understand the following comment in {JS,V8}DOMWindowCustom.cpp: // This function has variable arguments and can be: // Per current spec: // postMessage(message, target

Re: [webkit-dev] Is it OK to remove Frame::setIsDisconnected() and isDisconnected() ?

On Mon, Apr 9, 2012 at 3:24 PM, Maciej Stachowiak wrote: > On Apr 9, 2012, at 12:27 PM, Adam Barth wrote: >> On Wed, Apr 15, 2009 at 2:21 PM, Maciej Stachowiak wrote: >>> On Apr 15, 2009, at 1:29 PM, Sverrir Á. Berg wrote: >>>> Hi Adam, >>>> Thanks for

Re: [webkit-dev] Is it OK to remove Frame::setIsDisconnected() and isDisconnected() ?

On Wed, Apr 15, 2009 at 2:21 PM, Maciej Stachowiak wrote: >On Apr 15, 2009, at 1:29 PM, Sverrir Á. Berg wrote: >> Hi Adam, >> Thanks for the links.  These are simply exposing the functions as a formal a >> API's.  I understand that you typically don't want to change externally >> exposed API's but

[webkit-dev] List of prefixed APIs in WebKit

As you might be aware, there's been some amount of debate in the browser community recently about the use of vendor prefixes in the web platform. I'm sure many of you have opinions on this topic, but rather than triggering a long thread about this topic, I'd like to start by gathering some data ab

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

2012/4/5 Alexey Proskuryakov : > 05.04.2012, в 01:08, Adam Barth написал(а): > >> Based on this information, I've posted a patch that limits the -apple- >> and -khtml- vendor prefixes to ENABLE(DASHBOARD_SUPPORT): >> >> https://bugs.webkit.org/show_bug.cgi?id=8

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

(Previous email got cut off) ...release blocking bugs. On Apr 5, 2012 2:25 PM, "Adam Barth" wrote: > One option is to start evaluating the compat implications by disabling the > prefixes in Chrome. If we have a positive experience we can disable them > in more ports/confi

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

lexey Proskuryakov" wrote: > > 05.04.2012, в 01:08, Adam Barth написал(а): > > > Based on this information, I've posted a patch that limits the -apple- > > and -khtml- vendor prefixes to ENABLE(DASHBOARD_SUPPORT): > > > > https://bugs.webkit.org/show_bug.cgi?id=

Re: [webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

, 2012 10:14 AM, "Alexey Proskuryakov" wrote: > > 05.04.2012, в 01:08, Adam Barth написал(а): > > > Based on this information, I've posted a patch that limits the -apple- > > and -khtml- vendor prefixes to ENABLE(DASHBOARD_SUPPORT): > > > > https://bu

[webkit-dev] Following up on removing -khtml- and -apple- CSS vendor prefixes

In July 2010, there was a thread on webkit-dev about removing support for the -khtml- and -apple- vendor prefixes: https://lists.webkit.org/pipermail/webkit-dev/2010-July/013519.html At the time, we tried an approach recommended by David Hyatt

[webkit-dev] [Chromium] Changing how WebKit interfaces with Chromium

tl;dr: We're changing how WebKit interfaces with Chromium. This email describes what we're changing and why. If you've not interested in the Chromium port, you should feel free to skip this message. == Overview == Chromium is removing the PlatformSupport abstraction. Platform support exists ju

Re: [webkit-dev] XSSAuditor Bypass Question

The XSS auditor isn't able to detect injections into script contexts. Sometimes it will catch these sorts of injections "by accident", but often there's a way to bypass the auditor in these scenarios. The auditor is much better at catching injections in attribute values and between tags. The IE f

[webkit-dev] Feature Announcement: Adding

Per http://www.webkit.org/coding/adding-features.html I'm working on adding support to WebKit: . Because I'm enamored with GitHub at the moment, I'm working on the feature on a branch:

Re: [webkit-dev] Hosting the webkitgtk.org site on svn.webkit.org

By a new top-level directory, do you mean a peer to "trunk" and "branches"? If so, I'm not sure expected about that prospect. It sort of goes against the normal layout of SVN repositories. We already have , which would seem like the natural place to

Re: [webkit-dev] Throwing SECURITY_ERR on cross-origin window.location property accesses

I've started a thread on whatwg in case folks with like to discuss this topic further: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-March/035188.html Thanks, Adam On Thu, Mar 22, 2012 at 9:21 PM, Adam Barth wrote: > I wonder if we could expose the parent document's o

Re: [webkit-dev] Throwing SECURITY_ERR on cross-origin window.location property accesses

That's a risk, but you could also worry that the name would leak in the iframe's document.referrer property. Adam On Mar 23, 2012 12:02 PM, "David Levin" wrote: > > > On Thu, Mar 22, 2012 at 9:21 PM, Adam Barth wrote: > >> I wonder if we could expose the

Re: [webkit-dev] Throwing SECURITY_ERR on cross-origin window.location property accesses

I wonder if we could expose the parent document's origin, so you could write the check as follows: if (parent.location.origin != location.origin) return; It's slightly subtle because we wouldn't want to expose the origin of child frames (then you could probe the redirect structure of private

Re: [webkit-dev] UPDATED Re: Version control survey

On Sat, Mar 10, 2012 at 12:49 PM, Maciej Stachowiak wrote: > I made a bad choice of survey site. They want to charge me to see more than > 100 responses or to export the data, but they won't take my money. Sadness. > Please try this survey instead, it will run through the 17th. The survey seems t

Re: [webkit-dev] ChangeLogs

On Wed, Mar 21, 2012 at 3:45 PM, Timothy Hatcher wrote: > On Mar 21, 2012, at 2:46 PM, Adam Barth wrote: >> On Wed, Mar 21, 2012 at 2:29 PM, Timothy Hatcher wrote: >>> Lately I have observed more and more and more changes going into WebKit that >>> lack any details ab

Re: [webkit-dev] ChangeLogs

On Wed, Mar 21, 2012 at 2:29 PM, Timothy Hatcher wrote: > Lately I have observed more and more and more changes going into WebKit that > lack any details about why a particular change was made. It is intended that > the ChangeLog (and commit message) contain some details about your change, > not j

Re: [webkit-dev] "Magic Iframe" removal proposed

Yeah, normally I would have waited longer, but the patch fixed a crash in WebKit2 that was making the bots red. There was a discussion in another bug (sorry, don't have the link handy) where folks graciously held off fixing the crash, and I didn't want them to wait any longer than necessary. Adam

Re: [webkit-dev] Using GitHub to Contribute to WebKit (Experimental)

On Fri, Mar 16, 2012 at 2:32 PM, Ryosuke Niwa wrote: > Can we do some Bugzilla integration as Jarred suggested? If you're excited about using GitHub, you should feel free to do that work. Note: I'm not advocating for the use of GitHub. I'm just documenting a way that contributors can experiment

Re: [webkit-dev] Upstreaming Support for W3C Sensor API

on and receive feedback from the WebKit community without being blocked on merging your feature into trunk. Adam 2012/3/16 Adam Barth : > The specification appears to be here: > http://dvcs.w3.org/hg/dap/raw-file/tip/sensor-api/Overview.html > > Has this specification reached FPWD ye

Re: [webkit-dev] Using GitHub to Contribute to WebKit (Experimental)

On Fri, Mar 16, 2012 at 12:41 PM, Ariya Hidayat wrote: >> See point 3  of "Landing your code". Reviewer adds a link to pull >> request  in changelog. > > But now it means I have to search in two places: Bugzilla and Github, > in case I want to look up some past issues/problems. GitHub does have a

<    1   2   3   4   5   6   7   8   9   10   >