Re: [webkit-dev] New feature: Implement command API in webkit

2011-11-22 Thread Ryosuke Niwa 
As I'm not sure if we should implement the spec as is. The last time I
checked, no other UA implemented command API, and I don't necessarily agree
with all the design decisions they've made.

For example, I'm not sure if command's state should be directly tied with
the element that defines a command. Also it seems odd that an element that
defines commands can be a part of UI.

In particular, I would not want to see us implementing
http://dev.w3.org/html5/spec/Overview.html#building-menus-and-toolbars.

I think we should start from listing use cases first.

- Ryosuke

On Tue, Nov 22, 2011 at 11:09 PM, Rakesh Chaitanya wrote:

> Hi WebKit,
>
> I am planning to implement the command API in WebKit. The specificationfor 
> the same is
> here .
>
> Command API defines DOM apis for the elements which are commands. Any
> element with a 'accesskey' attribute defines a command except few(like 'a',
> 'button') where the condition to define a command is different. A command
> is one of the component in 
> menu
> .
>
> Please let me know your suggestions and inputs on the same.
>
> The WebKit bug for this is https://bugs.webkit.org/show_bug.cgi?id=72955,
> I have put up a basic implementation here.
>
> --
> Regards,
> Rakesh
>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] New feature: Implement command API in webkit

2011-11-22 Thread Rakesh Chaitanya 
Hi WebKit,

I am planning to implement the command API in WebKit. The specification for
the same is here .

Command API defines DOM apis for the elements which are commands. Any
element with a 'accesskey' attribute defines a command except few(like 'a',
'button') where the condition to define a command is different. A command
is one of the component in
menu
.

Please let me know your suggestions and inputs on the same.

The WebKit bug for this is https://bugs.webkit.org/show_bug.cgi?id=72955, I
have put up a basic implementation here.

-- 
Regards,
Rakesh
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Web Intents update

2011-11-22 Thread James Hawkins 
Hey folks,

Web Intents [1] is moving along steadily in the W3C arena.  We recently
created a Joint Task Force between the Webapps WG and DAP WG that will
serve as the home for the Web Intents API.

The current draft of the API is at [2], but we're working to convert the
draft to the W3C spec format to upload to w3.org ASAP.

Please take some time to review the API and send us your feedback at
public-web-inte...@w3.org.  To subscribe to the ML, please visit [3].

The prototype in Chrome is moving along swiftly, and we're ready to start
upstreaming patches to WebKit; the first patch has just finished the review
process [4].

We're looking forward to hearing from you!

[1] webintents.org
[2] www.chromium.org/developers/design-documents/webintentsapi
[3] http://lists.w3.org/Archives/Public/public-web-intents/
[4] https://bugs.webkit.org/show_bug.cgi?id=69870

Thanks,
James Hawkins
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

[webkit-dev] Regarding Problem in Launching in MiniBrowser for Webkit2

2011-11-22 Thread ajith kumar 
Hi All,
 I am facing some issues while launching the MiniBrowser.exe from
Visual Studio during checking of the Webkit2 process flows. Errors are
likes this;
"*This application has failed to start because CFNetwork.dll was not found.
Re-installing the application may fix this problem.*"

Note: Normal Webkit is able to launch using Safari setup. But Webkit
application is failing. I am building Webkit Version 84325, similar to
Android Ice Cream Sandwich code.
Please help me if you get any clue on this to proceed further. I
already tried the available helps in net by reinstalling the Quick Time
SDK, and replace the CFNetwork.dll with downloaded version etc.

Thanks & Regards,
Ajithkumar V
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] getComputedStyle returns percentage values for left / right / top / bottom

2011-11-22 Thread Jarred Nicholls 
2011/11/22 Jarred Nicholls 

> Indeed it is correct.  The CSS W3 draft also states that those properties
> return the "specified value", which if a percentage should return a
> percentage by definition.


By that I meant the *older* CSS drafts - the point being that it's always
been defined in that way for those properties.


>
>
> On Mon, Nov 21, 2011 at 10:49 PM, Xianzhu Wang (王显著) <
> wangxian...@chromium.org> wrote:
>
>> Sorry my previous post might be misleading. Just verified that in the
>> CSSOM draft the list of properties that getComputedStyle() may return the
>> used value doesn't include left/right/top/bottom. That is, according to the
>> draft, WebKit's current behavior about left/right/top/bottom is correct.
>>
>>
>> On Tue, Nov 22, 2011 at 10:50 AM, Xianzhu Wang (王显著) <
>> wangxian...@chromium.org> wrote:
>>
>>> A related bug is: https://bugs.webkit.org/show_bug.cgi?id=42799
>>> It's about the problem of pixelXXX CSS properties. Is these pixelXXX
>>> properties a workaround of bug 29084? I think after we fix 29084 we can
>>> drop the pixelXXX properties.
>>>
>>> The current draft CSSOM says getComputedStyle() should return the
>>> resolved values, and for width, height etc., "if the property applies to
>>> the element or pseudo-element and the resolved value of the 'display'
>>> property is not none, the resolved value is the used value. Otherwise the
>>> resolved value is the computed value."
>>>
>>> On Tue, Nov 22, 2011 at 8:02 AM, Ryosuke Niwa  wrote:
>>>
 Per bugzilla discusion, FF, IE, and Opera all return pixel values so we
 should just fix this bug.

 - Ryosuke

 On Mon, Nov 21, 2011 at 3:19 PM, Mike Sherov wrote:

> I'd like to begin working on this bug (
> https://bugs.webkit.org/show_bug.cgi?id=29084), and making sure that
> getComputedStyle() always returns a pixel value "used value" when 
> expected,
> although I suspect this is a controversial change, and
> http://www.webkit.org/coding/contributing.html#writecode says to ask
> in this mailing list before making a controversial change. Can anyone give
> me some feedback here on whether or not I can and should move forward on
> this?
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>

 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


>>>
>>
>> ___
>> webkit-dev mailing list
>> webkit-dev@lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>>
>
>
> --
> 
>
> *Sencha*
> Jarred Nicholls, Senior Software Architect
> @jarrednicholls
> 
>
>


-- 


*Sencha*
Jarred Nicholls, Senior Software Architect
@jarrednicholls

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] getComputedStyle returns percentage values for left / right / top / bottom

2011-11-22 Thread Jarred Nicholls 
Indeed it is correct.  The CSS W3 draft also states that those properties
return the "specified value", which if a percentage should return a
percentage by definition.

On Mon, Nov 21, 2011 at 10:49 PM, Xianzhu Wang (王显著) <
wangxian...@chromium.org> wrote:

> Sorry my previous post might be misleading. Just verified that in the
> CSSOM draft the list of properties that getComputedStyle() may return the
> used value doesn't include left/right/top/bottom. That is, according to the
> draft, WebKit's current behavior about left/right/top/bottom is correct.
>
>
> On Tue, Nov 22, 2011 at 10:50 AM, Xianzhu Wang (王显著) <
> wangxian...@chromium.org> wrote:
>
>> A related bug is: https://bugs.webkit.org/show_bug.cgi?id=42799
>> It's about the problem of pixelXXX CSS properties. Is these pixelXXX
>> properties a workaround of bug 29084? I think after we fix 29084 we can
>> drop the pixelXXX properties.
>>
>> The current draft CSSOM says getComputedStyle() should return the
>> resolved values, and for width, height etc., "if the property applies to
>> the element or pseudo-element and the resolved value of the 'display'
>> property is not none, the resolved value is the used value. Otherwise the
>> resolved value is the computed value."
>>
>> On Tue, Nov 22, 2011 at 8:02 AM, Ryosuke Niwa  wrote:
>>
>>> Per bugzilla discusion, FF, IE, and Opera all return pixel values so we
>>> should just fix this bug.
>>>
>>> - Ryosuke
>>>
>>> On Mon, Nov 21, 2011 at 3:19 PM, Mike Sherov wrote:
>>>
 I'd like to begin working on this bug (
 https://bugs.webkit.org/show_bug.cgi?id=29084), and making sure that
 getComputedStyle() always returns a pixel value "used value" when expected,
 although I suspect this is a controversial change, and
 http://www.webkit.org/coding/contributing.html#writecode says to ask
 in this mailing list before making a controversial change. Can anyone give
 me some feedback here on whether or not I can and should move forward on
 this?
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


>>>
>>> ___
>>> webkit-dev mailing list
>>> webkit-dev@lists.webkit.org
>>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>>
>>>
>>
>
> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
>


-- 


*Sencha*
Jarred Nicholls, Senior Software Architect
@jarrednicholls

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev