Hi all,

I concluded it once again - Safari and Apple stinks! Now I have waited for a
long time for the support for rich text editing (designMode) in Safari, and
yes - it came in Safari 2.0!

Well - "YES!" was my thought of it until I actually started using it. How
come Apple implements stuff, and say it's supported, even though it has been
implemented 1/3?

The rich text implementation is pretty much useless, even though Apple
actually knew what to implement, they just diden't!

If you look at this document (at the bottom), you can see that what they
actually implemented is a lot shorter list than what they should have
implemented.

http://www.opensource.apple.com/darw.../jsediting.cpp

Anyway - I will keep telling our users that Safari stinks, and they should
use a FireFox instead. Shame on Apple for the effort (or the lack of it).

I was joking about who could kill Apple, so that we would not have to be
limited this way, and I must agree with him when he said "There is no need
to, Apple is dooing a great job of killing themselves".

Regards,

Brian Binnerup

Brian Binnerup wrote:
> Hi all,
>
> I concluded it once again - Safari and Apple stinks! Now I have waited for a
<SNIP>


> Regards,
>
> Brian Binnerup
>
>

Erm, I use Firefox because thats what I used on my old Wintel machine. I
don't see anything wrong with safari, its just I prefer Firefox. But to
say that Apple stink because you don't like their browser is a bit
wierd. Its like saying you don't like ferrari's because the wheels have
the wrong type of tread!
Really, if you must troll, at least try to do a decent job of it.

Shard...