I don't think that the suite is testing much besides what we already have
regression tests for. For the most part, it just has different expectations.
There doesn't seem to be any harm in importing it as a whole now, but looking
over the failing tests, categorizing them and sending feedback to
Filed https://bugs.webkit.org/show_bug.cgi?id=46164 for the script to pull
the tests into our repo.
On Tue, Sep 21, 2010 at 3:27 PM, Maciej Stachowiak wrote:
>
> On Sep 20, 2010, at 10:19 PM, Ojan Vafai wrote:
>
> >
> > How about we create http/tests/xmlhttprequest/w3c-experimental or
> somethin
On Sep 20, 2010, at 10:19 PM, Ojan Vafai wrote:
>
> How about we create http/tests/xmlhttprequest/w3c-experimental or something
> like that? That can tide us over until the official version comes out, at
> which point, we can delete the w3c-experimental directory and just add a w3c
> director
On Tue, Sep 21, 2010 at 2:55 PM, Maciej Stachowiak wrote:
> On Sep 20, 2010, at 9:34 PM, Luke Macpherson wrote:
>
> > WebKit (or at least Chrome) is currently failing a bunch opera's tests
> > located at: http://tc.labs.opera.com/apis/XMLHttpRequest/
> >
> > It seems that it would be a good idea
On Sep 20, 2010, at 9:34 PM, Luke Macpherson wrote:
> WebKit (or at least Chrome) is currently failing a bunch opera's tests
> located at: http://tc.labs.opera.com/apis/XMLHttpRequest/
>
> It seems that it would be a good idea for us to make use of these
> tests in WebKit, so I was thinking of i
WebKit (or at least Chrome) is currently failing a bunch opera's tests
located at: http://tc.labs.opera.com/apis/XMLHttpRequest/
It seems that it would be a good idea for us to make use of these
tests in WebKit, so I was thinking of importing them into the
codebase. This raises the question:
Shoul
--
Regards
" Navigate Today For Better Tomorrow!!!"
mEeT mE LivE wItH tEcH cAkE @
http://hitechi.19.forumer.com/
http://go4expert.com/
http://www.liveperson.com/asadullah-ansari/
http://go4hitech.wordpress.com/
___
webkit-dev mailing list
webkit-dev@lis
On Sep 20, 2010, at 11:36 AM, Maciej Stachowiak wrote:
>
> On Sep 20, 2010, at 11:32 AM, Darin Adler wrote:
>
>> On Sep 20, 2010, at 10:22 AM, Darin Fisher wrote:
>>
>>> How about this?
>>>
>>> If any annotations were made to the patch, then "the button" gets named
>>> Preview. Else, the bu
On Sep 20, 2010, at 11:36 AM, Adam Roben wrote:
> On Sep 20, 2010, at 2:34 PM, Oliver Hunt wrote:
>
>> I really would like to be able to select some text and add a comment that
>> uses the selection as context, a single line of context is frequently
>> insufficient, this is about the only thin
On Sep 20, 2010, at 11:32 AM, Darin Adler wrote:
> On Sep 20, 2010, at 10:22 AM, Darin Fisher wrote:
>
>> How about this?
>>
>> If any annotations were made to the patch, then "the button" gets named
>> Preview. Else, the button is named "Publish" and when clicked performs its
>> work in one
On Sep 20, 2010, at 2:34 PM, Oliver Hunt wrote:
> I really would like to be able to select some text and add a comment that
> uses the selection as context, a single line of context is frequently
> insufficient, this is about the only thing that still makes the new review
> tool less effective
I really would like to be able to select some text and add a comment that uses
the selection as context, a single line of context is frequently insufficient,
this is about the only thing that still makes the new review tool less
effective than the old review mechanism (for me at least).
--Olive
On Mon, Sep 20, 2010 at 11:12 AM, David Hyatt wrote:
>
>
> This is going to be tricky. You basically want to walk the line box tree
> rather than the renderobject tree and then look at surrounding text.
>
> > About turning off the underline if the ruby is in a link: I've looked at
> the styles and
On Sep 20, 2010, at 10:22 AM, Darin Fisher wrote:
> On Mon, Sep 20, 2010 at 10:10 AM, Adam Barth wrote:
> On Mon, Sep 20, 2010 at 8:37 AM, Alexey Proskuryakov wrote:
> > 16.09.2010, в 18:39, Darin Fisher написал(а):
> >> Push the publish button to review your comments :-)
> >
> > Alas, not any
On Sep 20, 2010, at 10:22 AM, Darin Fisher wrote:
> How about this?
>
> If any annotations were made to the patch, then "the button" gets named
> Preview. Else, the button is named "Publish" and when clicked performs its
> work in one shot.
>
> Was there a strong outcry for removing the previ
On Sep 17, 2010, at 8:07 PM, Eric Mader wrote:
> Hi,
>
> I'm working on making the following enhancements to Ruby Text:
>
> 1) Implement the behavior of ruby-overhang:auto
>
> 2) implement the behavior of ruby-line-stacking:exclude-ruby
>
> 3) Add some Mac OS specific character properties to t
On Mon, Sep 20, 2010 at 10:10 AM, Adam Barth wrote:
> On Mon, Sep 20, 2010 at 8:37 AM, Alexey Proskuryakov
> wrote:
> > 16.09.2010, в 18:39, Darin Fisher написал(а):
> >> Push the publish button to review your comments :-)
> >
> > Alas, not any more!
> >
> > https://bugs.webkit.org/show_bug.cgi?
On Mon, Sep 20, 2010 at 8:37 AM, Alexey Proskuryakov wrote:
> 16.09.2010, в 18:39, Darin Fisher написал(а):
>> Push the publish button to review your comments :-)
>
> Alas, not any more!
>
> https://bugs.webkit.org/show_bug.cgi?id=46074
Yeah. The machinery is still there for the preview, I'm jus
16.09.2010, в 18:39, Darin Fisher написал(а):
> Push the publish button to review your comments :-)
>
Alas, not any more!
https://bugs.webkit.org/show_bug.cgi?id=46074
- WBR, Alexey Proskuryakov
___
webkit-dev mailing list
webkit-dev@lists.webkit.o
19 matches
Mail list logo
