Le 2011/09/26 04:44, Invisible a écrit :
>>> Was it you that said something about "committing to backwards
>>> compatibility way too early"?
>>
>> Yep. That was the fundamental failure, caused by the whole "write once"
>> marketing campaign.
>
> I wouldn't mind, but it didn't even /work/.
>
> Like I said, I wrote an applet. It worked fine in IE. When I tried it
> with Netscape, it crashed with a null pointer exception. And, since it's
> an applet, I have no idea /where/ it crashed. You don't get a stack trace.
>
> I suspect this is probably related to the vagueness of the
> documentation. That means that others don't really know how to implement
> it correctly. Or, hell, maybe the documentation just doesn't actually
> match what Sun implemented...

It may be that some bug in the implementation under IE is effectively 
hiding another bug...
It may be that you get the crash on the correct implementation and you 
did something wrong that made it work on a faulty implementation.

Remember the imfamous "it's not a bug, it's a feature" that Microsoft 
spun to cover actual IE bugs instead of correcting them.

>
>>> I notice Office no longer comes with any documentation at all, just a
>>> link to an online forum.
>>
>> It has documentation. It just mixes it in with the online forum. I think
>> you have to chose to install it locally, tho, which is what you might be
>> seeing.
>
> Oh well. Almost never non-trivial Office task usually involves finding
> an Office MVP anyway...
>
>> I've lost track of closing braces....
>
> ...which is why every open bracket should always start a new indentation
> level...
>

Post a reply to this message