testing needed!

[domtheknight]

I need a couple of specific things tested:

1. If any of you ported a style from LJ (etc) prior to core2's release, and have not since upgraded your style to core2 (so you're still on a customized core1 style), we need to do some specific testing in that circumstance to try to reproduce a reported bug.

2. If any of you also have openIDs, we need to look at something with comments and comment notifications.

3. I need people to look at the menus in multiple browsers to see if anyone can reproduce this issue: picture of problem (what looks like tiny chunks of menu missing). That specific photo is from Safari 4.

If you can do any or all of those things, please comment here or PM or email me and I'll give you more details.

ETA: all of these tests should be done now, thanks!

[cross-posted to beta-testing listserv]

Comments

[delight]

Sorry for the slow response, I have family visiting and will be off and on computer all night; pseudelight@gmail.com will also get to me when I'm at work, so that would be lovely, thanks. :)

[domtheknight]

Email sent! It's from domtheknight at gmail, in case you were wondering.

[delight]

My email's being extremely strange to me at the moment, so I hope it's okay if I reply here: so far I am unable to reproduce preview issues with core2 while being on a core1 style (gosh, I feel boring -- I'm not getting any problems!); I'm happy to change core1 styles and try again, if it would help! Camino 1.6 and Firefox 3 on OS X Leopard as well as Chrome and Firefox 2 on WinXP are having no issues.

Now I am off to -- well, okay, to class, and then to wrangle my email to fight with openID.

[domtheknight]

Hm, you can change core1 and try again if you would like. It certainly wouldn't hurt, and if you've got time, maybe that will tell us something.

It's always possible that the original reported problem was a blip in the database, or was accidentally fixed by another bug.