ToothyWikiInternals/FixedErrorReports

Clock glitches

(None currently observed, all servers syncing via NTP. Post here if this is not the case).

Cyrillic issues

(see also ToothyWikiInternals/NonEnglishLanguages)

Just to let Moonshadow know, my browser at work (IE6) refused to let me see the site until I installed a Cyrillic font.

When I looked at 'View Source', the page was there (looking at RecentChanges and one other I can't recall), but the actual browser window showed just a blank white screen.

It worked fine once I had found my Win2K CD and installed the font it requested.

-- Kazuhiko

: Cyrillic now disabled - it was causing more trouble than it was worth. If we ever get any Russian speakers wanting to post in Russian, I'll add it to the user preferences panel as an option. - MoonShadow

Linewrapping

Broken handling of line-wrapping appears to happen in cases like this:

 some preformatted text
 some more preformatted text, FOLLOWED BY A BLANK LINE

This long line of text is separated from the preceding preformatted stuff by a blank line, and yet Wiki doesn't appear to line-wrap it for some reason... abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde

By contrast, line wrapping happens properly with a paragraph like this. abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde abcde

: OK, scratch that. Looking at the HTML source, it looks correct, and Netscape and IE 5.0 display it correctly. It's just IE 5.5 throwing a wobbly at the most bizarre and unnecessary provocation, in typical fashion. And there's not much MoonShadow can do about that... *sigh* --AlexChurchill

Not-A-Real-Bug

ElectronicBovineSquatters, despite being created today, doesn't show in RecentChanges.

 - Hm. It does from here.. ^^; - MoonShadow

: Here too. The only RecentChanges glitch I've seen was the ChronoTrigger timestamp one. Maybe PT was just afflicted by an NTL cache or something? --AlexChurchill

- Looks like caching issues to MoonShadow

(PeterTaylor) I don't feel that's a satisfactory explanation, given that AlanRoberts _was_ showing, and was created at pretty much the same time.

AlexChurchill: Well come on Peter, you're a coder - you know what's needed for bug reports. It's behaviour that's not reproducible from MoonShadow's home, my work or MikeJeggo's home. Is it still happening now for you? If so, give us a report of your features which might vary from where me and MS tried to reproduce it: what browser, OS, etc. Copypaste a chunk of the RecentChanges which you're seeing. If you can't reproduce it now, then what's MS supposed to do about it?

: I know it's not reproducible by intent, but by continuing to assert its existence I increase the probability that it's taken seriously next time someone reports it. See: my knowledge of bug reports goes beyond the theory they teach in lectures.