(3) is still not a bug. You're misunderstanding how the log viewer works. Again, you have to compare this behaviour to:

Code:
//window -dk0 @logviewer | loadbuf @logviewer FILE.LOG


put the two colored lines in FILE.log and load it:

Code:
[00:00] <^K>4* One of those ways is like this,<ctrl+o> where the first color code which exists is NOT at the very start of the string
<^K>4[00:00] * And the other way is like this,<ctrl+o> where the first color code which exists IS at the very start of the string


You will see that it stops coloring both lines. This is the behaviour you should be expecting.

Again, the window is simply reloading lines of plain text. There is no difference between a control code at column 1 or column N, because they are just colour codes being applied to text. The log viewer has no understanding of the column difference because it has no understanding of a "log format"-- it's just loading plain text that happens to have control codes. In this case, the files it loads happen to be log files, but there's no such requirement. I'm not sure how I can make this any more clear.

(5) I looked at this behaviour again. It's popping up over your mouse (horizontally)-- it's not remembering a specific position. The only reason you're reproducing this is because you aren't moving your mouse. The popping up over your mouse thing is definitely intentional.

Regarding your gripe about expectations: mIRC had no log viewer until ~7.11 (in 6.35 and earlier it was notepad.exe). Most users don't really have any specific expectations about the behaviour of a log viewer in mIRC, since it previously had no such functionality, so it really shouldn't throw anybody off. Regardless, the behaviour of a log viewer should not be compared to the regular channel buffer anyway, which is what you're doing. a "LOG VIEWER" is something that views text (go download any "log viewer" application and you'll see the same thing)-- it is not meant to accurately recreate your buffer. Colours, timestamps, etc., are simply displayed as logged in the file, and have no more special meaning as they did in your session. The log viewer is simply showing you the text that was written to the log-- exactly as it was written to the log. This is what anybody should expect a log viewer to display. I don't see any of this as "broken" even without the custom window script functionality. My expectation of a log viewer is just what Khaled implemented it as: notepad with control code parsing. I would expect this from a log viewer in mIRC just as I would expect this from a log viewer in MSN, or a log viewer in any other program that logs my interactions.