Re: [webkit-dev] new APIs for strokes with dash in Canvas

The WebCore patch of Young is basically using the specified behavior of stroke-dasharray and stroke-dashoffset in the SVG specification [1]. But we wouldn't support units or percentages, just floating point numbers. Dirk Am 23.09.2011 um 07:38 schrieb Young Han Lee: > On Fri, Sep 23, 2011 at 1

Re: [webkit-dev] new APIs for strokes with dash in Canvas

On Fri, Sep 23, 2011 at 1:44 PM, Ian Hickson wrote: > > Is there any documentation on how this patch and Gecko's implementation > work and what they support? > > I spent some time trying to find it, but couldn't. This bugzilla seems to be the only place we can get information at the moment. http

Re: [webkit-dev] new APIs for strokes with dash in Canvas

On Thu, 22 Sep 2011, Darin Fisher wrote: > > Do you know if anyone is working to add this to the spec for Canvas? > It seems like it may not take much to get it added, given that FF > already has an implementation. Dashed lines are on my list but were not a high priority. If there are implemen

Re: [webkit-dev] starting implementation of postMessage tranferables

On Thu, 22 Sep 2011, Oliver Hunt wrote: > > There is not any substantive harm in prefixing, whereas there can be > real problems down the road if we don't prefix. The harm in prefixing is that people can't use the feature for years after it's implemented; q.v. CSS. -- Ian Hickson

Re: [webkit-dev] new APIs for strokes with dash in Canvas

Do you know if anyone is working to add this to the spec for Canvas? It seems like it may not take much to get it added, given that FF already has an implementation. -Darin On Thu, Sep 22, 2011 at 7:31 PM, Young Han Lee wrote: > Hi all, > > I have a patch to add webkitLineDash and webkitLineDa

Re: [webkit-dev] starting implementation of postMessage tranferables

On Sep 22, 2011, at 7:46 PM, Ian Hickson wrote: > On Thu, 22 Sep 2011, David Levin wrote: >> >> *Summary*: Implementing postMessage with transferable support as >> webkitPostMessage. >> >> *Details*: >> *Spec*: >> http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#posting-me

Re: [webkit-dev] starting implementation of postMessage tranferables

On Thu, 22 Sep 2011, David Levin wrote: > > *Summary*: Implementing postMessage with transferable support as > webkitPostMessage. > > *Details*: > *Spec*: > http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#posting-messages > > This describes window.postMessage and the same i

Re: [webkit-dev] new APIs for strokes with dash in Canvas

On Thu, Sep 22, 2011 at 7:31 PM, Young Han Lee wrote: > Hi all, > > I have a patch to add webkitLineDash and webkitLineDashOffset APIs on > CanvasRenderingContext2D on https://bugs.webkit.org/show_bug.cgi?id=63933 > > The purpose of these APIs is to support for strokes with dash in Canvas. > > Al

[webkit-dev] new APIs for strokes with dash in Canvas

Hi all, I have a patch to add webkitLineDash and webkitLineDashOffset APIs on CanvasRenderingContext2D on https://bugs.webkit.org/show_bug.cgi?id=63933 The purpose of these APIs is to support for strokes with dash in Canvas. Although the API is not specified in the HTML Canvas specification yet,

[webkit-dev] starting implementation of postMessage tranferables

*Summary*: Implementing postMessage with transferable support as webkitPostMessage. *Details*: *Spec*: http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#posting-messages This describes window.postMessage and the same is true for Message Ports and Worker Context. It doesn't me

Re: [webkit-dev] Vendor Prefixing, was Re: New feature announcement - Implement HTML5 Microdata in WebKit

TL;DR (from Charles himself): My concern, on this WebKit development mailing list, is that introducing another method -without- vendor prefixing may create some tension that WebKit developers would like to avoid. ___ webkit-dev mailing list webkit-dev@lis

Re: [webkit-dev] Starting implementation on W3C Filter Effects

Hey Dirk, On 23/09/2011, at 6:24 AM, Dirk Schulze wrote: > Dean, do you want to reuse the existing filter code, or do you plan to write > another filter implementation just for CSS? Would be interesting if we would > need to nest CSS_FILTERS and FILTERS, or if they could get enabled > independ

[webkit-dev] Vendor Prefixing, was Re: New feature announcement - Implement HTML5 Microdata in WebKit

On 9/22/2011 2:42 PM, James Robinson wrote: On Thu, Sep 22, 2011 at 2:32 PM, Charles Pritchard > wrote: On 9/22/2011 2:13 PM, Ian Hickson wrote: On Fri, 23 Sep 2011, Dean Jackson wrote: However, isn't prefixing designed to avoid in

Re: [webkit-dev] Early deletion of DocumentLoader instances

On Thu, Sep 22, 2011 at 3:07 PM, Darin Adler wrote: > On Sep 22, 2011, at 11:07 AM, Steve Block wrote: > >> This change is causing problems on Android. We use the >> AllowLocalLoadsForLocalAndSubstituteData policy but >> Document::initSecurityContext() no longer calls >> securityOrigin().grantLoad

Re: [webkit-dev] Early deletion of DocumentLoader instances

> I tried to look into this, but couldn’t find a function named > DocumentLoader::loader. Sorry, typo. Thanks for CC'ing me on the bug. Will re-post the corrected version there. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit

Re: [webkit-dev] Early deletion of DocumentLoader instances

On Sep 22, 2011, at 11:07 AM, Steve Block wrote: > This change is causing problems on Android. We use the > AllowLocalLoadsForLocalAndSubstituteData policy but > Document::initSecurityContext() no longer calls > securityOrigin().grantLoadLocalResources() because of the check for > 'm_frame->docume

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

On Thu, Sep 22, 2011 at 2:32 PM, Charles Pritchard wrote: > On 9/22/2011 2:13 PM, Ian Hickson wrote: > >> On Fri, 23 Sep 2011, Dean Jackson wrote: >> >>> However, isn't prefixing designed to avoid incompatibilities in spec >>> changes, not incompatibilities between implementations? Ensuring no >>

Re: [webkit-dev] Mouse Lock API

On Thu, Sep 22, 2011 at 2:38 PM, Alexey Proskuryakov wrote: > > 22.09.2011, в 14:25, Darin Fisher написал(а): > > Our next step is to extend this to non-fullscreen, so I think it would be > counter-productive to preclude non-fullscreen at this time. > > > I think that adding an API for non-fullsc

Re: [webkit-dev] Mouse Lock API

22.09.2011, в 14:25, Darin Fisher написал(а): > Our next step is to extend this to non-fullscreen, so I think it would be > counter-productive to preclude non-fullscreen at this time. I think that adding an API for non-fullscreen mouse lock would be a detriment to the Web platform. So gating f

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

On 9/22/2011 2:13 PM, Ian Hickson wrote: On Fri, 23 Sep 2011, Dean Jackson wrote: However, isn't prefixing designed to avoid incompatibilities in spec changes, not incompatibilities between implementations? Ensuring no conflicts in implementations doesn't matter too much if the spec changes. It

Re: [webkit-dev] Mouse Lock API

On Thu, Sep 22, 2011 at 2:23 PM, Alexey Proskuryakov wrote: > > 21.09.2011, в 12:52, Darin Fisher написал(а): > > True, although there are still questions about how the user experience will > work for non-fullscreen. I think we only feel confident that we have a > decent fullscreen solution at t

Re: [webkit-dev] Mouse Lock API

21.09.2011, в 12:52, Darin Fisher написал(а): > True, although there are still questions about how the user experience will > work for non-fullscreen. I think we only feel confident that we have a > decent fullscreen solution at this point, and the plan was to restrict the > initial implement

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

On Fri, 23 Sep 2011, Dean Jackson wrote: > > However, isn't prefixing designed to avoid incompatibilities in spec > changes, not incompatibilities between implementations? Ensuring no > conflicts in implementations doesn't matter too much if the spec > changes. It's designed to ensure that aut

Re: [webkit-dev] Starting implementation on W3C Filter Effects

Interesting. It is unfortunate that we currently have no easy way to tell which ports are shipping with which defines enabled. I didn't think to check the settings on the branch. Thank you for the clarification. -eric On Thu, Sep 22, 2011 at 1:06 PM, Darin Adler wrote: > The settings in TOT a

Re: [webkit-dev] New feature flag proposal: Joystick API

Hello, Work has started on a Gamepad (Joystick) spec in the W3C WebEvents WG. If you're interested in commenting or participating, the mailing list can be found at http://lists.w3.org/Archives/Public/public-webevents/ For reference, the draft in-progress can be found at http://dvcs.w3.org/hg/web

Re: [webkit-dev] Starting implementation on W3C Filter Effects

Dean, do you want to reuse the existing filter code, or do you plan to write another filter implementation just for CSS? Would be interesting if we would need to nest CSS_FILTERS and FILTERS, or if they could get enabled independent of each other. Like previous comments mention, Apple still doe

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

On 23/09/2011, at 5:59 AM, Ian Hickson wrote: > On Thu, 22 Sep 2011, Charles Pritchard wrote: >> >> Regardless of an ENABLE flag, be certain to use the webkit prefix. >> document.getItems(typeNames) turns into >> document.webkitGetItems(typeNames) >> >> Note that it's easy to implement this in

Re: [webkit-dev] Starting implementation on W3C Filter Effects

The settings in TOT are the settings for nightly builds. They don't necessarily make it clear what Apple does for releases. There are features like this one that we’ve been turning off on release branches. -- Darin ___ webkit-dev mailing list webk

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

On Thu, 22 Sep 2011, Charles Pritchard wrote: > > Regardless of an ENABLE flag, be certain to use the webkit prefix. > document.getItems(typeNames) turns into > document.webkitGetItems(typeNames) > > Note that it's easy to implement this in pure javascript as a prototype. Assuming the patch imp

Re: [webkit-dev] Starting implementation on W3C Filter Effects

On Thu, Sep 22, 2011 at 11:44 AM, Dean Jackson wrote: > > On 23/09/2011, at 4:38 AM, Eric Seidel wrote: > >> I was actually considering removing ENABLE(FILTERS) since it seemed to >> be on everywhere. > > Sorry to bring bad news, but Apple currently turns off ENABLE(FILTERS) on > desktop and iOS.

Re: [webkit-dev] Starting implementation on W3C Filter Effects

On Thu, Sep 22, 2011 at 11:44 AM, Dean Jackson wrote: > On 23/09/2011, at 4:38 AM, Eric Seidel wrote: >> I was actually considering removing ENABLE(FILTERS) since it seemed to >> be on everywhere. > > Sorry to bring bad news, but Apple currently turns off ENABLE(FILTERS) on > desktop and iOS. In

Re: [webkit-dev] Starting implementation on W3C Filter Effects

Maybe the best course of action is to remove ENABLE(FILTERS) by always enabling the code and then have the CSS API for filters developed behind ENABLE(CSS_FILTERS)? Adam On Thu, Sep 22, 2011 at 11:38 AM, Eric Seidel wrote: > I was actually considering removing ENABLE(FILTERS) since it seemed to

Re: [webkit-dev] Starting implementation on W3C Filter Effects

On 23/09/2011, at 4:38 AM, Eric Seidel wrote: > I was actually considering removing ENABLE(FILTERS) since it seemed to > be on everywhere. Sorry to bring bad news, but Apple currently turns off ENABLE(FILTERS) on desktop and iOS. > It would probably be better for us to remove it > first and

Re: [webkit-dev] Starting implementation on W3C Filter Effects

I was actually considering removing ENABLE(FILTERS) since it seemed to be on everywhere. It would probably be better for us to remove it first and this feature to exist under its own define (if it even needs a define?). If you'll want folks to be able to turn this off w/o affecting their existing

[webkit-dev] Starting implementation on W3C Filter Effects

Dirk (known in these parts as krit) reminded me that I had not emailed webkit-dev about the plans to start an implementation of W3C's new Filter Effects specification. https://dvcs.w3.org/hg/FXTF/raw-file/tip/filters/publish/Filters.html The quick summary is that this exposes the 'filter' prop

Re: [webkit-dev] Early deletion of DocumentLoader instances

It looks like this was resolved in https://bugs.webkit.org/show_bug.cgi?id=61494, which resulted in http://trac.webkit.org/changeset/87756. I can't access the bug, so I'm following up here ... This change is causing problems on Android. We use the AllowLocalLoadsForLocalAndSubstituteData policy bu

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

Regardless of an ENABLE flag, be certain to use the webkit prefix. document.getItems(typeNames) turns into document.webkitGetItems(typeNames) Note that it's easy to implement this in pure javascript as a prototype. -Charles On 9/22/2011 8:00 AM, Adam Barth wrote: Just so I understand, you'r

Re: [webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

Just so I understand, you're talking about the DOM APIs for interacting with microdata, right? I know there was some controversy in the HTML working group about Microdata versus RDFa. It's not 100% clear to me which of those technologies will "win out" in the end, but it seems valuable to impleme

[webkit-dev] New feature announcement - Implement HTML5 Microdata in WebKit

Hi, I have been looking at HTML5 Microdata implementation in Webkit. Microdata is a specification used to nest semantics within existing content on web pages. Search engines, web crawlers, and browsers can extract and process Microdata from a web page and use it to provide a richer browsing expe