Kubuntu Settings in KDE

Chani chanika at gmail.com
Sat Mar 29 04:35:25 GMT 2008

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 
sending a different set of code when the user presses the "try ajaxy mode 
anyways even though it isn't supported" button. there is code that will work, 
and code that will not work, and right now the user gets code that does not 
work when they press that button even though working code could be sent just 
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 
understand why it can't be working and unsupported in the meantime.

This message brought to you by evyl bananas, and the number 3.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080328/6ab87cb6/attachment.sig>

More information about the kde-core-devel mailing list