IMHO Bernie's comments make sense... I think the ways people can put
spurious "non-printing" chars into a file are pretty much knowable, and that
browsers *should* deal more gracefully with simple error conditions than
they do now... doing things like dying when one rsads a spurious char after
the end of the outermost scope of a file seems kinda extreme.
Jeff Sonstein, Networks Administrator
New College of California
50 Fell Street
San Francisco CA 94102
[415] 241-1302 ext. 490
-----------------------
The opinions expressed here do not
esslect anything about my employer,
New College of California
--------- Opinions R Us ---------