> I guess what I'm really asking is -- as they share so much,
> is it generally OK to assume that if something renders
> properly in Safari/WebCore that it will do so in Konqueror/KHTML?
Although I think Apple has made it easier for the KHTML team to
incorporate their changes[1], I don't think it's safe to assume that
your layout or code will paint/render your web page the same in Safari
and Konqueror.
> Perhaps not good questions as I'm after a simple answer to a
> technical and presumably complex question? But, how
> responsible is it *really* to assume that if it works in one
> it will work in the other?
This is all a little murky to me, so perhaps others can clarify how
Webkit works but I test on both Firefox and Camino because although they
both use the same rendering engine, Camino seems to lag behind Firefox
because the Mozilla Foundation actually pays developers to work on
Firefox and I don't think that's the case for Camino; the same could be
said for Safari v. Konqueror. Apple has a bunch of engineers on their
payroll to work on Safari; Konqueror is a labor-of-love and obviously,
both browsers evolve and improve at different paces.
> Also, what do people think will happen in the future between
> these two technologies under the new arrangement?
Dunno, but I think David Hyatt's blog is a good source to follow along.
[1] weblogs.mozillazine.org/hyatt/
HTH,
..dean
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Web-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/web-dev/email@hidden
This email sent to email@hidden
