cacklebunny
asked on
Can't highlight or select text in Internet Explorer 6??!??!?
We just launched a new website that uses CSS to absolutely position DIVs throughout the page. We opted for the "tableless" structure per the suggestion of many articles and colleagues in an effort to stay "current" with the technology.
However, after we launched the site, we have started getting many complaints from users that they cannot select --or highlight-- text in the body of our online articles. Instead, when they try to select specific text, it will automatically highlight ALL the text on the page from the point they started on up.
This problem, we have found is centered around Internet Explorer 6 ONLY. If I try it in an earlier version of IE, I can select text with no problem. Netscape and Mozilla also do not have any problems.
Clearly this is an IE 6 bug, but are there any known fixes? In the interim, I've told my customers that they can "triple-click" over paragraphs and that will highlight those individual paragraphs for them to copy (except, they can't right-click and choose the "copy" option --they have to go to "EDIT" and "COPY" in order for it to work).
I would like to get a more user-friendly fix to this issue without having to totally throw our web design out and go back to the old table-design. Any help?
However, after we launched the site, we have started getting many complaints from users that they cannot select --or highlight-- text in the body of our online articles. Instead, when they try to select specific text, it will automatically highlight ALL the text on the page from the point they started on up.
This problem, we have found is centered around Internet Explorer 6 ONLY. If I try it in an earlier version of IE, I can select text with no problem. Netscape and Mozilla also do not have any problems.
Clearly this is an IE 6 bug, but are there any known fixes? In the interim, I've told my customers that they can "triple-click" over paragraphs and that will highlight those individual paragraphs for them to copy (except, they can't right-click and choose the "copy" option --they have to go to "EDIT" and "COPY" in order for it to work).
I would like to get a more user-friendly fix to this issue without having to totally throw our web design out and go back to the old table-design. Any help?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
we may be able to help more if we can see the site(or at least see the code...)
ASKER
Thanks, but I'm afraid I can't accept these as solutions. I don't want to go through the ordeal of redesigning the site to use floating DIVs instead of absolute positioning. I think you'll agree that I shouldn't have to do that all for the sake of IE 6. Absolute positioning, in and of itself, should not be regarded as a "no-no" just because Internet Explorer doesn't render it correctly. The standard was made so we could use absolute positioning and (theoretically) have complete control of our design.
I was aware the problem was focused on absolute positioning and IE 6 (based on my Google search), and I was reading on another site about overlapping DIVs (none of our DIVs overlap), but I was hoping for a fix akin to the "Tantek Hack" that would allow us to continue to use our initial design with a mininum of edits. Due to the sheer number of absolutely-positioned DIVs, I simply cannot revert to another means without throwing the site design away and starting over.
I appreciate your comments and suggestions --if anyone can come up with a fix, I'll be happy to award the points...otherwise I'll need to close this issue and move on.
I was aware the problem was focused on absolute positioning and IE 6 (based on my Google search), and I was reading on another site about overlapping DIVs (none of our DIVs overlap), but I was hoping for a fix akin to the "Tantek Hack" that would allow us to continue to use our initial design with a mininum of edits. Due to the sheer number of absolutely-positioned DIVs, I simply cannot revert to another means without throwing the site design away and starting over.
I appreciate your comments and suggestions --if anyone can come up with a fix, I'll be happy to award the points...otherwise I'll need to close this issue and move on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you post any code so that maybe just maybe some of the experts here may be able to get a better look?
Even a link will do.
>>> I think you'll agree that I shouldn't have to do that all for the sake of IE 6.
no you shouldn't, but you better check the browser stats and see whats the most popular browser that visits your site. I'll bet its IE6
Even a link will do.
>>> I think you'll agree that I shouldn't have to do that all for the sake of IE 6.
no you shouldn't, but you better check the browser stats and see whats the most popular browser that visits your site. I'll bet its IE6
ASKER
seanpowell:
My doctype is actually the following:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
I can't get rid of this, of course...if I do, I have more problems on my hands (IE goes into "quirks" mode).
My doctype is actually the following:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
I can't get rid of this, of course...if I do, I have more problems on my hands (IE goes into "quirks" mode).
I hear you cacklebunny - unfortunately, it's one or the other. No doctype, or no text selection.
Sorry.
Sorry.
Hi,
Since the user can eventually select the intended text (by reselecting and holding the left key down for a longer period), my theory is that the browser doesn't 'notice' the initial event. If this is so, you might be able to capture the initial mouse event, and force the selection with code.
Vinny
Since the user can eventually select the intended text (by reselecting and holding the left key down for a longer period), my theory is that the browser doesn't 'notice' the initial event. If this is so, you might be able to capture the initial mouse event, and force the selection with code.
Vinny
ASKER
Vinny:
Actually, it notices the initial event, because it's highlighting *something*...but it doesn't highlight the text you had intended to select.
Actually, it notices the initial event, because it's highlighting *something*...but it doesn't highlight the text you had intended to select.
Hi cacklebunny,
I realize that. (I've had the problem on these pages) It's been my experience, though, that after fiddling a bit, I am able to select & copy the section of text I want from the page -- which makes me believe that somehow or another, the browser is losing sight of where the cursor is initially.
Vinny
I realize that. (I've had the problem on these pages) It's been my experience, though, that after fiddling a bit, I am able to select & copy the section of text I want from the page -- which makes me believe that somehow or another, the browser is losing sight of where the cursor is initially.
Vinny
To All Experts,
A request has been made in Community Support to close this question:
https://www.experts-exchange.com/questions/20770035/20-Oct-Please-cancel-and-refund.html
If there are no objections, after 72 hrs, a moderator will finalize this question by:
- Deleting the Q and refunding points
YensidMod
Community Support Moderator @Experts Exchange
A request has been made in Community Support to close this question:
https://www.experts-exchange.com/questions/20770035/20-Oct-Please-cancel-and-refund.html
If there are no objections, after 72 hrs, a moderator will finalize this question by:
- Deleting the Q and refunding points
YensidMod
Community Support Moderator @Experts Exchange
I believe dorward should get some recognition since he first answered at least some of the question -- to wit:
"happens quite a bit with MSIE 6 and absolute positioning.", as well as his three workarounds
Simply because cacklebunny "can't accept these as solutions", does not mean they aren't viable options -- tedious, work-intensive -- perhaps -- but also doable.
But then again, what do I know :)
Vinny
"happens quite a bit with MSIE 6 and absolute positioning.", as well as his three workarounds
Simply because cacklebunny "can't accept these as solutions", does not mean they aren't viable options -- tedious, work-intensive -- perhaps -- but also doable.
But then again, what do I know :)
Vinny
>>unfortunately, it's one or the other. No doctype, or no text selection.
That's the correct answer. Doesn't matter where the points go, but you have to accept one of the responses...
It's not our fault - blame Microsoft.
That's the correct answer. Doesn't matter where the points go, but you have to accept one of the responses...
It's not our fault - blame Microsoft.
ASKER
These are *NOT* viable answers. In my original post, I clearly identified that I had already known this to be an IE 6 bug.
In addition, I also clearly stated in my original post that I needed a fix that did not require me to throw out my original design and start over....these two "fixes" would certainly require exactly that. The first one regarding absolute positioning would require a total redesign...the second answer basically disrupts all the elements for every other browser by throwing IE into "quirks" mode and making the pages not validate as XHTML in Netscape, IE, Mozilla, etc.
I don't think it's fair to expect me to accept two readily-known workarounds that basically would throw everything else out of wack through their implementation...that just doesn't make any sense.
If I have to give someone a certain amount of points to get this case closed due to some technicality, fine --I'm willing to negotiate that-- but I don't believe I should be shelling out 250 points for an answer that doesn't come close to meeting my initial request.
In addition, I also clearly stated in my original post that I needed a fix that did not require me to throw out my original design and start over....these two "fixes" would certainly require exactly that. The first one regarding absolute positioning would require a total redesign...the second answer basically disrupts all the elements for every other browser by throwing IE into "quirks" mode and making the pages not validate as XHTML in Netscape, IE, Mozilla, etc.
I don't think it's fair to expect me to accept two readily-known workarounds that basically would throw everything else out of wack through their implementation...that just doesn't make any sense.
If I have to give someone a certain amount of points to get this case closed due to some technicality, fine --I'm willing to negotiate that-- but I don't believe I should be shelling out 250 points for an answer that doesn't come close to meeting my initial request.
ASKER
Well after reading the FAQ..."there is no answer" can qualify as the only answer...so I owe people points. I have myself to blame for giving this kind of value to an unanswerable question. Live and learn, yes?
As some posters said, don't blame them --blame Microsoft. And you're right. I don't blame any of you and appreciate your help and patience. I know you probably share in my frustration.
Thanks for your help. Dorward and seanpowell --you got the credit.
As some posters said, don't blame them --blame Microsoft. And you're right. I don't blame any of you and appreciate your help and patience. I know you probably share in my frustration.
Thanks for your help. Dorward and seanpowell --you got the credit.
I know that this question was already answered here, but I thought that I should at least give a correct solution for future readers of this post. I was desperatly looking for a fix and I came across some javascript that fixes the problem. Here is the link. http://blog.tom.me.uk/2003/07/23/boie6selecta.php
Dorward is correct; it is a known bug but not well documented. The bug occurs with the use of absolutely positioned DIVs. You should not see it with other positioning. So, before you abandon your plans for a css layout in favor of tables, I'd suggest looking at your css. There maybe alternate ways to accomplish the same design. If you provide a link or some sample code, we maybe able to give some further suggestions. Other than that, I have not heard of any known fix.
-Xikilm