I is not codr

[ysobel]

...but, er. I found a problem (a page that was missing a </a>), so I created the bug, submitted an attachment, decided I'm doomed, and am speculatively eyeing the other bugs on my list.

mainly for my own reference:

http://bugs.dwscoalition.org/show_bug.cgi?id=432
http://bugs.dwscoalition.org/show_bug.cgi?id=158
http://bugs.dwscoalition.org/show_bug.cgi?id=490

http://bugs.dwscoalition.org/show_bug.cgi?id=11 + http://bugs.dwscoalition.org/show_bug.cgi?id=12 + http://bugs.dwscoalition.org/show_bug.cgi?id=14

Comments

[denise]

*votes for 432* :)

[ysobel]

432 is an awesome number the straightforwardest to code, I think, because it's mainly "make X act like the rest of the things on the page", rather than adding new behaviour.

[ETA: yeeeeahhhh, straightforward, sure. *facepalm*]

(For 490, I want to see a) if the behaviour of private messaging from an unvalidated account has been decided on [not sure if it's "don't let them send" or just "warn that the person won't be able to reply"], and b) take care of both in one swell foop.)

(...and 11/12/14, which are kind of the same class of thing in my head, will NOT LEAVE ME ALONE. even though I've not entirely figured out how to implement it [interface-wise, though I have ideas, and also checking-permissions-wise].)

[denise]

I'd say just warn that they won't be able to reply.