On Fri, May 19, 2017 at 5:24 PM, Isaac Devine wrote:
> On 19 May 2017 at 16:16, Fujii Hironori wrote:
>>
> I have a linker warning because it was no longer linked to the
> MultiThreadedDLL, and was statically linked instead. The behavior
> > Sure, it is good to test conformance, but there is no longer regression
> > testing on the deprecated feature behavior itself.
> > Ideally, this would require tighter syncing between the browsers. Might
> have
> > positive and/or negative consequences.
>
> I don't think we should be changing
On Fri, May 19, 2017 at 10:17 AM, youenn fablet wrote:
>
>
> Le ven. 19 mai 2017 à 09:44, Anne van Kesteren a écrit :
>>
>> On Fri, May 19, 2017 at 5:11 PM, youenn fablet wrote:
>> > When a spec gets updated, the WPT tests will ideally be
Le ven. 19 mai 2017 à 09:44, Anne van Kesteren a écrit :
> On Fri, May 19, 2017 at 5:11 PM, youenn fablet wrote:
> > When a spec gets updated, the WPT tests will ideally be updated at the
> same
> > time.
> > The updated tests will no longer ensure
On Fri, May 19, 2017 at 5:11 PM, youenn fablet wrote:
> When a spec gets updated, the WPT tests will ideally be updated at the same
> time.
> The updated tests will no longer ensure non-regression until the browser
> implements the new behavior.
Ideally if importing test
Le jeu. 18 mai 2017 à 05:09, Philip Jägenstedt a écrit :
>
>> FWIW, I think it makes sense to treat wpt as both regression tests and
> conformance tests. They're regression tests because they can in fact catch
> regressions. And they're conformance tests because they're
On 19 May 2017 at 16:16, Fujii Hironori wrote:
> On Fri, May 19, 2017 at 8:18 AM, Isaac Devine
> wrote:
> > Hi,
> >
> > I'm looking at linking against WebKit in my application, which is linked
> > against the MultiThreadedDLL CRT (i.e.
7 matches
Mail list logo