RCU Forums - View Single Post - highlighting problem
View Single Post
Old 08-13-2007 | 07:48 PM
  #31  
tippy
Senior Member
 
Joined: Oct 2002
Posts: 1,415
Likes: 0
Received 0 Likes on 0 Posts
From: Town Creek, AL
Default RE: highlighting problem


ORIGINAL: Pushrod02

I just highlighted your "error message" from the debug tool by click, drag and delete. Upgrade your browser Tippy. IE 7.0 is available from MS and like always, it's free. (hint, here's your solution) I had another issue with some software and low and behold it FIXED the problem with highlighting a quote here on RCU too.
Click, shift+arrow key, delete does that too.

Let me get this straight.

IE 6 worked great on RCU ... no lack of highlight problems.

RCU installs some code that makes IE 6 glitch ...

I have to upgrade to fix the problem they installed ?

What other features besides being able to do what I use to be able to do several months ago do I gain by going to IE 7????
Upgrading to regain a feature I use to have in a previous version is NOT an upgrade. That's called a patch.

So ... your saying I should install the IE7 patch to fix the bug that RCU can't fix??

If RCU has abandoned the efforts to resolve this issue for IE 6 users (dead horse scenario) ... then RCU needs to make a public statement to the users concerning this. They need to advise all users and future users that RCU no longer works correctly with IE6 and recommends users install the IE7 patch for things to work correctly.

I don't want to go through the up-patch process and then have RCU post the next day "... we fixed it ...".

I want to know that RCU has completely given up all efforts to fix this before I change my software to accomodate their bug.

Otherwise ... the next user with IE 6 will simply start another thread stating they have a problem.

If RCU announced they can't fix the bug and suggests we all install the IE7 patch, then I might be more receptive to the patch.

The last word from RCU concerning this issue was:
RCadmin:: 6/8/2007 10:10:40 PM
... delete files is correct. I am having our developer look at this bug ...
Everything else has been " ... clear your cache and post your browser version ..."

All I want to know is ... what did the developer come up with after two months of debugging???
If the developer says it's hopeless and we all should up-patch, then post it here.