> Has a test suite been published we can test against?
I didn't see a test suite which is opened to everyone yet.
Is this a problem for dropping prefix?
> Are there any other implementations of the APIs? Besides the time-based
> requirement of dropping vendor prefixes when a specification goes to
Hello, webkit-dev
I would like to let you know, I am planning to add Proximity Events to
WebCore.
This feature will be behind the ENABLE_PROXIMITY_EVENTS. Please see :
http://www.w3.org/TR/proximity/
https://bugs.webkit.org/show_bug.cgi?id=92837
If you have any comments, please let me kn
Another possibility is --extraverbose. That is more verbose (!), but perhaps
more obviously related to --verbose than --debug is.
John
On Jul 31, 2012, at 7:28 PM, Ryosuke Niwa wrote:
> Let's rename --verbose --verbose to --debug at least.
>
> I'd also prefer renaming --details to --trace or s
Please make sure the new text decoration values don't break editing (rich
text editing & execCommand). In particular, we probably need to update
ApplyStyleCommand/EditingStyle to handle -webkit-text-decoration*.
On Tue, Jul 31, 2012 at 7:35 PM, Bruno Abinader wrote:
> Hi all :)
>
> As suggested b
Hi all :)
As suggested by Ojan, I am writing a mail to you about my intention to
implement all updated and missing text-decoration* properties from
CSS3 spec (currently in development), named below:
-webkit-text-decoration ( https://bugs.webkit.org/show_bug.cgi?id=92000 )
CSS3 dev spec: http://de
Let's rename --verbose --verbose to --debug at least.
I'd also prefer renaming --details to --trace or something because
--details sounds less detailed than --debug but I'm not strongly
opinionated about this.
- Ryosuke
On Tue, Jul 31, 2012 at 7:09 PM, Dirk Pranke wrote:
> On Tue, Jul 31, 2012
On Tue, Jul 31, 2012 at 7:02 PM, Ryosuke Niwa wrote:
> On Tue, Jul 31, 2012 at 6:59 PM, Dirk Pranke wrote:
>>
>> On Tue, Jul 31, 2012 at 6:36 PM, Ryosuke Niwa wrote:
>> > On Tue, Jul 31, 2012 at 6:29 PM, Dirk Pranke
>> > wrote:
>> >>
>> >> I'm finally getting around to cleaning up the byzantine
On Tue, Jul 31, 2012 at 6:59 PM, Dirk Pranke wrote:
> On Tue, Jul 31, 2012 at 6:36 PM, Ryosuke Niwa wrote:
> > On Tue, Jul 31, 2012 at 6:29 PM, Dirk Pranke
> wrote:
> >>
> >> I'm finally getting around to cleaning up the byzantine mass of
> >> options in new-run-webkit-tests that controls what
On Tue, Jul 31, 2012 at 6:36 PM, Ryosuke Niwa wrote:
> On Tue, Jul 31, 2012 at 6:29 PM, Dirk Pranke wrote:
>>
>> I'm finally getting around to cleaning up the byzantine mass of
>> options in new-run-webkit-tests that controls what gets printed to
>> stderr and stdout during a test run.
>>
>> The
On Tue, Jul 31, 2012 at 6:29 PM, Dirk Pranke wrote:
> I'm finally getting around to cleaning up the byzantine mass of
> options in new-run-webkit-tests that controls what gets printed to
> stderr and stdout during a test run.
>
> The patch is posted in https://bugs.webkit.org/show_bug.cgi?id=9243
Hi all,
I'm finally getting around to cleaning up the byzantine mass of
options in new-run-webkit-tests that controls what gets printed to
stderr and stdout during a test run.
The patch is posted in https://bugs.webkit.org/show_bug.cgi?id=92432.
To quote the changelog:
[All of the --print X,Y,Z
Hi,
Can we enable performance.webkitNow on all ports?
The last time "performance" feature was discussed, there were some privacy
concerns about performance.navigation, etc... but webkitNow doesn't seem to
pose any significant privacy concerns and is quite useful for benchmark
purposes. e.g. in o
I've been working on WebKit for 64-bit windows. I've gotten the whole
thing to compile using my repository (
https://github.com/achristensen07/webkit64prep.git) and Brent Fulgham's
repository (https://github.com/bfulgham/WinCairoRequirements.git).
Javascript and Cairo work and WinLauncher opens,
Fixed again. I'm still trying to debug the locking thats getting stuck. I
appreciate everyone letting me know when it happens.
-Bill
On Jul 31, 2012, at 1:03 PM, Peter Kasting wrote:
> It looks like the timeline has once again stopped updating.
>
> PK
__
It looks like the timeline has once again stopped updating.
PK
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
On Tue, 31 Jul 2012, Arko Saha wrote:
>
> test(function () {
> assert_equals( makeEl('div',{itemtype:' '}).itemType[0],
> window.undefined );
> }, 'itemType[index] must be undefined for out-of-range index');
>
> DOMSettableTokenList returns null for out-of-range index.
This is incorrect. Whi
Has anything been done to verify security and stability of the feature, for
example, fuzz testing? I'd like to request that before enabling for Apple's
ports.
- Maciej
On Jul 30, 2012, at 11:35 PM, Arko Saha wrote:
> I am planning to enable MICRODATA feature by default in WebKit.
>
> Micro
NRWT is producing a large number of apparent regressions on ML. A
build/test run I performed last night shows 294 unexpected fails on WK1
tests [1] and 150 unexpected fails on WK2 tests [2]. My question is whether
platform/mac has been rebaselined for ML or not? If not, then are there
plans to do s
On Tue, Jul 31, 2012 at 3:02 AM, Kihong Kwon wrote:
> Hi, webkit-dev
>
> ** **
>
> As you can see with these links,
>
> http://www.w3.org/TR/battery-status/
>
> http://www.w3.org/TR/vibration/
>
> the status of Battery Status API and Vibration API have been changed to
> the CR quit
On Tue, Jul 31, 2012 at 12:55 AM, Arko Saha wrote:
> For an example :
>
> test(function () {
> assert_equals( makeEl('div',{itemtype:' '}).itemType[0],
> window.undefined );
> }, 'itemType[index] must be undefined for out-of-range index');
>
> makeEl method creates an element with empty item
For an example :
test(function () {
assert_equals( makeEl('div',{itemtype:' '}).itemType[0],
window.undefined );
}, 'itemType[index] must be undefined for out-of-range index');
makeEl method creates an element with empty itemtype(0 tokens). Test
expects itemTpye[0] should return undefined, i
For those of you who didn't see the original announcement of perf-o-matic,
it's located at:
webkit-perf.appspot.com.
- Ryosuke
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
Hi,
I've fixed a bunch of bugs in perf-o-matic; in particular, I've determined
the culprit of the performance issue of perf-o-matic and fixed it.
Dashboard, custom graphs, etc... should load almost instantly now.
Best,
Ryosuke Niwa
Software Engineer
Google Inc.
__
On Mon, Jul 30, 2012 at 11:51 PM, Arko Saha wrote:
> I have tested the test :
> http://w3c-test.org/html/tests/submission/Opera/microdata/001.html
> 255 Pass
> 82 Fail
>
> Most of the failed cases are specific to their implementation and for
> others, I need to check.
>
What do you mean by "spec
24 matches
Mail list logo
