Re: [webkit-dev] testharness Wiki page added

Apologies - my mail server appears to have blocked the zip file I tried to attach to my previous message (for some reason it doesn't like when anyone sends .js files). If anyone is interested, the only changes I made to the anchor_href-w3c.html page were the following: (1) I included testharne

Re: [webkit-dev] testharness Wiki page added

On 5/31/12 7:55 PM, "Maciej Stachowiak" mailto:m...@apple.com>> wrote: On May 31, 2012, at 5:51 PM, Jacob Goldstein mailto:jac...@adobe.com>> wrote: I haven't found that to be the case for the tests I have written for each suite, the output from testharness can be as simple as "PASS" or "FAI

Re: [webkit-dev] Removing "type" attribute from DOMSelection

Without any data on its usage, I don't support this. -Sam On May 30, 2012, at 9:58 PM, Antaryami Pandia wrote: > Hi , > We plan to remove the "type" attribute from DOM selection. > This attribute is not part of any standard specification and the current > webkit implementation is not consiste

Re: [webkit-dev] Device and page scaling

> 1) automatically scaling content to the AutoValue (ie 160) DPI, which is what most mobile optimized sites do All WebKit-based mobile browsers I've met do target-densityDpi=auto by default, and resolve auto as 160 (and if they don't use 160, they probably have good reasons for it like expecting t

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

I think folks agree that these are important use cases. The disagreement is about how to address them. For example, another approach is to use responsive images (e.g., srcset and image-set) together with device units in CSS. Now that WebKit has support for subpixel layout, we can provide a high

Re: [webkit-dev] webkit2 with v8

Oliver - Ok, well that makes sense. I was under the mistaken impression webkit had an engine abstraction, and that it wasn't being move forward to webkit2. Darin - If by webkit developer you mean I contribute to webkit, then no. I do however use webkit in several projects. On Fri, Jun 1, 2012 at

Re: [webkit-dev] webkit2 with v8

They may have a desire for it, but certainly not a need -- Webkit includes a well maintained, guaranteed ABI stable JS engine that works on _all_ architectures, with a high performance JIT support available on numerous architectures and OS's. Being able to support two engines just in webcore ha

Re: [webkit-dev] webkit2 with v8

Are you a WebKit developer? -- Darin ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] User agent string for WebKit nightly

Hi all, I'm trying to find a way to discern between Safari and WebKit nightly based on the user agent string. Could someone explain me how and when the user agent for WebKit nightly gets updated? It seems to be based on the Safari UA, but right now it's lagging behind. And it seems to have been

Re: [webkit-dev] webkit2 with v8

What constitutes a need? Qt obviously has a need for it. Is there a threshold of ports needing a feature before it becomes blessed? On Fri, Jun 1, 2012 at 11:09 AM, Darin Adler wrote: > On Jun 1, 2012, at 9:55 AM, Jake wrote: > > > I believe it's a disservice to the community as a whole to not

Re: [webkit-dev] webkit2 with v8

On Jun 1, 2012, at 9:55 AM, Jake wrote: > I believe it's a disservice to the community as a whole to not provide proper > javascript engine abstractions in webkit. I don’t agree. We should have abstractions for things that need to be abstract. Too many abstractions make the code much harder t

Re: [webkit-dev] webkit2 with v8

I believe it's a disservice to the community as a whole to not provide proper javascript engine abstractions in webkit. On Fri, Jun 1, 2012 at 10:51 AM, Alexey Proskuryakov wrote: > > 01.06.2012, в 7:18, Balazs Kelemen написал(а): > > This is of course something non-Qt developers have to worry

Re: [webkit-dev] webkit2 with v8

01.06.2012, в 7:18, Balazs Kelemen написал(а): >> This is of course something non-Qt developers have to worry about, see e.g. >> . > > This one could be avoided with the shim (in > https://bugs.webkit.org/show_bug.cgi?id=87872). We could intro

Re: [webkit-dev] Device and page scaling

Reposting comment from Bug 88047 After discussing this internally we believe that while the current implementation of target-densitydpi is not ideal it's ability to allow you scale your viewport to a given target density as well as to allow you to not scale (deviceDPI) are both desired features

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 don't have any plans to implement the WebIDL

Re: [webkit-dev] webkit2 with v8

On 05/31/2012 07:06 PM, Alexey Proskuryakov wrote: What I'm seeing is that parts of v8 support are already leaking into cross-platform WebKit2 code. WebKitTestRunner cannot just use WebCoreTestSupport, it needs an ifdef for Qt: #if PLATFORM(QT) DumpRenderTreeSupportQt::injectInternalsObject(

Re: [webkit-dev] Adding ENABLE_HTML_MEDIA_CAPTURE to WebCore

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 don't have any plans to implement the WebIDL >> interfaces. >> >> 2) From the spec, it sounds like the ca