From kde-core-devel  Sat Mar 29 04:35:25 2008
From: Chani <chanika () gmail ! com>
Date: Sat, 29 Mar 2008 04:35:25 +0000
To: kde-core-devel
Subject: Re: Kubuntu Settings in KDE
Message-Id: <200803282135.38320.chanika () gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=120685895403166
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2014894.DHMbF6ihg8"

--nextPart2014894.DHMbF6ihg8
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On March 28, 2008 19:53:40 Gary Greene wrote:
> On Friday 28 March 2008 09:34:11 am Kevin Krammer wrote:
> > On Friday 28 March 2008, Gary Greene wrote:
> > > On Wednesday 26 March 2008 10:30:10 pm Chani wrote:
> > > > it would be quite enough if, after their "this browser is not
> > > > supported" warning, they would give the user the code that *works*
> > > > with konqueror, the code that it gives to firefox, instead of
> > > > insisting on sending it code that does not work.
> > >
> > > Unfortunately, that would very likely not meet Google's QA team's
> > > approval, so we have to deal with what we get.
> >
> > Sending code that is known not to work is considered better quality than
> > sending code that will?
> > Coporate policies never stop to amaze me :-/
> >
> > Cheers,
> > Kevin
>
> This is less the matter of what works and what does not, but more so how
> many people can be allocated to maintaining support for a browser or not.
> If we were to turn on Firefox mode for Konqueror versus just plain not
> supporting it, Google'd be short changing you as well as ourselves as we

but that's just the thing: this isn't about changing modes. this is about=20
sending a different set of code when the user presses the "try ajaxy mode=20
anyways even though it isn't supported" button. there is code that will wor=
k,=20
and code that will not work, and right now the user gets code that does not=
=20
work when they press that button even though working code could be sent jus=
t=20
as easily.

*that* is what is driving me nuts here.
maybe something got lost in translation?

>
> Laying it out in a nutshell, my goal is to get KHTML working with Google's
> apps, not the other way around, as Google has very good (albeit, not what

that's great, I'd love to see it working *and* supported. but I still don't=
=20
understand why it can't be working and unsupported in the meantime.

=2D-=20
This message brought to you by evyl bananas, and the number 3.
www.chani3.com

--nextPart2014894.DHMbF6ihg8
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBH7ccaeGbAwpIS3GwRAqWbAJ40045MdbgM7HmuV+f4VsrCP/TjCACfSwl1
c78cwC4RTLqbT7pKVyE2+TY=
=VUhf
-----END PGP SIGNATURE-----

--nextPart2014894.DHMbF6ihg8--