I just upgraded the forum to vBulletin 4.1.12, which fixes a variety of bugs and also includes integration with Forum Runner (which I haven't set up yet--are folks interested in this?).
You can read more about the release here: https://www.vbulletin.com/forum/entr...ulletin-4-1-12
As usual, please let me know if you run into bugs or unusual behavior.
Forum Runner does not support Blackberry yet, so no interest in that from me for now.
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
Manage attachments window is not working for me. It pops up and is completely blank - IE9. Edit control also not fixed based on issues I had with backspacing and moving between lines in this post.
Manage attachments also not working in Chrome but edit control seems to work fine in Chrome.
Oh the joys of the different browsers.
Last edited by VirtualAce; 04-12-2012 at 10:31 PM.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Ah yes I did not see that thread. I have tested it in IE9 and Chrome on Win7 64-bit as well as IE9 and Chrome in Vista 32-bit and it does not work on either of them.
So this was an issue for me before the upgrade, but it still seems to be an issue, so here it is:
Win7 64-bit, Chrome 18
When I use keystrokes (ctrl-i or ctrl-b) to enable bold or italics the backspace and enter keys don't work right. I get two behaviors:
1. If I backspace/enter while bold/italics is still on, it moves the cursor to just before the bold/italic area, and backspaces/enters there.
2. If I backspace/enter some time after disabling the bold/italics, it moves the cursor to just after the bold/italic area and backspaces/enters there.
The backspace thing has been bugging me since I started using the keystrokes some weeks ago, but I just discovered that enter does the same thing today. I'm not sure what other keys may behave this way too.
I also tested this with FF10 and IE9, which seem to work fine.
