----- Original Message -----
From: "Einav Cohen" <ecohen(a)redhat.com>
To: "Andrew Cathrow" <acathrow(a)redhat.com>
Cc: engine-devel(a)ovirt.org
Sent: Thursday, September 6, 2012 8:14:22 AM
Subject: Re: [Engine-devel] GUI patches: verify on 2 browsers
> ----- Original Message -----
> From: "Andrew Cathrow" <acathrow(a)redhat.com>
> Sent: Thursday, September 6, 2012 1:49:38 PM
>
> ----- Original Message -----
> > From: "Einav Cohen" <ecohen(a)redhat.com>
> > To: "Yaniv Kaul" <ykaul(a)redhat.com>
> > Cc: engine-devel(a)ovirt.org
> > Sent: Thursday, September 6, 2012 3:37:08 AM
> > Subject: Re: [Engine-devel] GUI patches: verify on 2 browsers
> >
> > > ----- Original Message -----
> > > From: "Yaniv Kaul" <ykaul(a)redhat.com>
> > > Sent: Thursday, September 6, 2012 10:32:59 AM
> > >
> > > On 09/06/2012 10:28 AM, Einav Cohen wrote:
> > > > oVirt-engine developers/reviewers: oVirt-engine patches that
> > > > involve GUI changes (i.e. web admin and/or user portal)
> > > > *must*
> > > > be
> > > > verified on at least two different browsers out of the
> > > > following:
> > > > firefox/chrome/ie
> > >
> > > What happens when it fails on Chrome? We know of several issues
> > > with
> > > it
> > > already.
> >
> > we will handle the already-existing chrome issues eventually.
> > my e-mail is about not introducing any new GUI features/changes
> > from
> > now on that haven't been verified on at least two browsers.
>
> Why not 3? Obviously that's 50% more work but saying 2 our of
> firefox/chrome/ie doesn't make sense to me. Someone could pick to
> test on IE and Chrome and leave something that's broken in Firefox.
>
Even testing on these 3 different browsers is not really enough - the
GUI might look/behave differently even between different versions of
FF, or between FF on Linux vs. FF on Windows.
Testing on two browsers (instead of one) should improve compatibility
issue detection.
I think the idea of saying two browsers Firefox + one other that was made elsewhere is the
right way to go.
>
> >
> > > Y.
> > >
> > > >
> > > > ----
> > > > Thanks,
> > > > Einav
> > > > _______________________________________________
> > > > Engine-devel mailing list
> > > > Engine-devel(a)ovirt.org
> > > >
http://lists.ovirt.org/mailman/listinfo/engine-devel
> > >
> > > _______________________________________________
> > > Engine-devel mailing list
> > > Engine-devel(a)ovirt.org
> > >
http://lists.ovirt.org/mailman/listinfo/engine-devel
> > >
> > >
> > >
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel(a)ovirt.org
> >
http://lists.ovirt.org/mailman/listinfo/engine-devel
> >
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/engine-devel
>
>
>