History of "Problems"

6. October 14, 2003 at 10:06am by 217.18.252.30

Line 4:

test

5. September 17, 2003 at 3:08am by John Kugelman

Title:
Problems
Lines 1-14:
Lines 17-20:

I haven't been able to reproduce the problem. Can you tell me what browser you're using?

4. June 27, 2003 at 2:06pm by 80.225.220.22

Lines 9-10:

I changed these to — and –. Do those work better?

Yes. Netscape Navigator 4 resolves those. Netscape Navigator 3 doesn't, but I guess one can't have everything.

Line 13:

In fact, I've just found that the characters "t." at the end of "result." below get lost on saving if no new-line follows them. Adding the newline gave the appearance you now see (view in editing mode). Hmm - that's funny - that particular quirk didn't occur when I tried to reproduce it. Doubtless, you can track down the problem though.

Line 16:
  • I tried giving a url in square brackets, but omitting to specify text as well. I got an unexpected result

3. June 20, 2003 at 11:34am by John Kugelman

Lines 3-4:

If you mean Netscape 4... Well, I haven't bothered to target it. Maybe I'll just disable to stylesheets for Netscape 4 if it's really a problem.

If you don't mean Netscape 4, then let me know and I'll try to fix it right away. The site looks fine in Mozilla, so I assumed it would look fine in Netscape 6+.

Line 7:

I changed these to — and &x2013;. Do those work better?

Line 9:

Fixed:

  • I tried giving a url in square brackets, but omitting to specify text as well. I got an unexpected result.

2. June 20, 2003 at 11:00am by 62.64.215.184

Lines 5-6:

Also, some browsers (yeah, Netscape Communicator again) do not resolve &mdash or &ndash.

1. June 20, 2003 at 10:48am by 62.64.230.246

Title:
Wiki Problems
Line 1:

I disabled stylesheet support in Netscape Communicator, as it doesn't display some of your pages correctly. What an improvement! Possibly, Netscape 7 would do better. Simpler stylesheets might avoid such problems.

I tried giving a url in square brackets, but omitting to specify text as well. I got an unexpected result.

Also, some browsers (yeah, Netscape Communictor again) do not resolve &mdash or &ndash.

I'll add details of any other quirks I come across.