A couple updates to this thread:
1) DOMCrypt seems to be moving along the W3C path. There isn't a
working group set up yet, but there seems to be sufficient interest
that a W3C activity appears to be spinning up around this effort.
2) Ian Fette met with a number of banks in South Korean and Taiw
On Wed, Aug 24, 2011 at 8:36 AM, Scott Graham wrote:
> Hi,
>
> I wanted to let everyone know that I propose to add a new feature
> flag, JOYSTICK. http://webkit.org/b/66859
>
> This flag will enable an API and events for accessing joysticks and
> related devices. There's a prototype effort happeni
On Aug 24, 2011, at 3:20 PM, Tasneem Brutch - Samsung wrote:
> Khronos WebCL is not yet a specification, and the WebCL API has not yet been
> standardized. The WebCL members are currently discussing the security and
> interoperability issues in the WebCL Working Group. Samsung would like to
Khronos WebCL is not yet a specification, and the WebCL API has not yet
been standardized. The WebCL members are currently discussing the
security and interoperability issues in the WebCL Working Group.
Samsung would like to introduce a WebCL patch at this time, to follow
the ongoing specification
On 8/24/11 1:52 PM, "Dan Bernstein" wrote:
>
> On Aug 24, 2011, at 1:08 PM, Alan Stearns wrote:
>
>> ... Idea for platform-proofing some DumpRenderTree results
>
> You can make a text-only test that uses Ahem (you can still rely on its
> horizontal metrics, at least) and DOM API such as Range¹
On Aug 24, 2011, at 19:21 , Simon Fraser wrote:
> My main objection to adding this is that it's just one of many different
> types of input device, and if we add these piecemeal for each device that
> takes our fancy, we'll end up with a horrible mishmash of different input
> events.
>
> I'd pr
On Aug 24, 2011, at 1:08 PM, Alan Stearns wrote:
> I have an idea for writing LayoutTests where what's being tested are line
> breaks. Take the case of this recent bug fix:
>
> https://bugs.webkit.org/show_bug.cgi?id=2
>
> The problem here was that if you had a left float and text-indent co
I have an idea for writing LayoutTests where what's being tested are line
breaks. Take the case of this recent bug fix:
https://bugs.webkit.org/show_bug.cgi?id=2
The problem here was that if you had a left float and text-indent combined,
the text-indent was not being considered in the line br
If it's helpful, I can attempt to document these bits of methodology
somewhere on our wiki.
Another thing -- perhaps we could point newcomers like Scott to Whatwg
as the forum for design discussions, rather than referring to W3C
process?
:DG<
On Wed, Aug 24, 2011 at 11:25 AM, Dimitri Glazkov wr
We should do this right, you won't hear any arguments from me. But I
am also sure that "W3C time investment" is a code word for years of
soul-sucking bureaucratic drudgery. As such, I don't think you meant
we should be using W3C process as the measuring stick for doing things
"right" in WebKit. The
My main objection to adding this is that it's just one of many different types
of input device, and if we add these piecemeal for each device that takes our
fancy, we'll end up with a horrible mishmash of different input events.
I'd prefer a more general strategy of thinking about all the variou
On Wed, Aug 24, 2011 at 9:39 AM, Scott Graham wrote:
> On Wed, Aug 24, 2011 at 9:19 AM, Simon Fraser
> wrote:
>>
>> I think it's too early to implement this. We should wait until it's a W3C
>> draft at least.
>
> There's certainly work to be done in improving the design. I'm not proposing
> to sl
On Wed, Aug 24, 2011 at 9:19 AM, Simon Fraser wrote:
> I think it's too early to implement this. We should wait until it's a W3C
> draft at least.
There's certainly work to be done in improving the design. I'm not proposing
to slavishly implement the API exactly as specified there.
However, I w
I think it's too early to implement this. We should wait until it's a W3C draft
at least.
window.addEventListener("MozJoyConnected"..), really?
Simon
On Aug 24, 2011, at 8:36 AM, Scott Graham wrote:
> Hi,
>
> I wanted to let everyone know that I propose to add a new feature
> flag, JOYSTICK.
On Tue, Aug 23, 2011 at 7:44 PM, William Siegrist wrote:
> We just used "git svn reset -r " and "git svn fetch" where is the rev
> before the bad one.
This does not seem to help with my particular problem.
Xan
___
webkit-dev mailing list
webkit-dev@l
Hi,
I wanted to let everyone know that I propose to add a new feature
flag, JOYSTICK. http://webkit.org/b/66859
This flag will enable an API and events for accessing joysticks and
related devices. There's a prototype effort happening in Mozilla also
(https://wiki.mozilla.org/JoystickAPI), and the
16 matches
Mail list logo
