I'm running my .NET application in Internet Explorer(Version 11) in compatibility mode. I'm using grid views to display content on my ASPX page. When I open the page and tried to select some cell or row from grid views, it is not selecting properly.
It is so difficult or impossible to select exactly the text you wanted to copy into an e-mail or a document. When you dragged the mouse to select text, you often selected adjacent paragraphs or columns also, even though you didn't want them.
Working fine with Earlier edition(IE 10) and Firefox and Chrome. I have to fix/find out why It is not working in IE 11.
Please let me know how to fix this one.
I think this is a "feature" in IE11 and there's no way to fix it in the code. IE11 text selection seems to struggle once it hits any HTML structures (spans, divs).
There is a work around for users but it's a bit painful. Press F7 to turn on caret mode, then you can select one item (double click) and then, holding down the shift key, use the cursor keys to highlight a selection.
If you have a lot of users, it would be better to implement an "Export to Excel" or "Copy to Clipboard" function than rely on text selections to get to the data.
IE also allows for entire field selection using CTRL+Click (Left Mouse Click).
Edge, nor Chrome allows for this superior selection technique.
Related
I am using OpenRefine to clean text from a CSV file. I've been working on the same project for several weeks, and it was working fine until this week.
I am trying to use the 'Cluster and Edit' function from the 'Edit cells' menu. When I use the 'fingerprint' and 'ngram fingerprint' keying function, the frame that opens up inside the browser window is sized appropriately, and I have access to all the buttons and selection menus. However, when I try to use the 'metaphone3' keying function, the frame that opens up is way wider than the browser window, the sliding selection boxes that usually appear in the right side of the frame are not visible, and the buttons across the bottom of the frame ('Select All', 'Unselect All', etc.) are not available. I'd really like to be able to use this keying function option again. Does anyone know what's going on, or how I might be able to fix it.
I am using the OpenRefine 3.3 beta, although a similar issue was happening earlier this week with all keying function options in 3.2 (all were working fine in 3.2 as recently as Friday, 10/25/2019). I am using Firefox, although the same issue happens in Internet Explorer. The system OS is Windows 10 Enterprise.
Thanks in advance!
In one of my PCs when I use inspect tool in chrome, I can't select some part of a property or a value, so I have to retype all the value again. As many times as I click on the selected text, the caret doesn't go to the place I need and the selected text doesn't deselect.
the following picture shows what I want and what happens.
There is no problem in another PC.
Both are windows 10 64bit and google chrome 62.
Try holding shift or control while clicking. Haven't tried it, but it may work. My guess is that it's simply a UX workflow that DevTools doesn't handle well.
I want to switch tabs with the Ctrl+Page Up/Down shortcuts on Chrome (using the latest version). It always works correctly when I use the left Ctrl button, but with the right Ctrl button, it only works properly on some days. When it doesn't, it becomes page up/down instead of correctly being next/previous tab. I usually browse tabs for the same few sites, so I don't think it's due to the websites. I'm not sure what causes this. Is this supposed to be happening? How can I make the shortcut always work when using right Ctrl?
Edit: Found that it's basically any "ctrl+" shortcuts and not just next/previous tab. Also, I changed my keyboard recently, but this problem has existed since my old keyboard which I've used for 4 or more years, over at least two different computers, and Chrome is the only browser I use so I don't know if this problem will still exist if I switch browsers.
Your right ctrl button is not working properly (hardware problem). Maybe it's damaged or somewhat.
Some pages maybe does not alove that shortcut's. I'm saying this because i found that on some pages, and my shortcut's doesn't work on them.
I don't see other posible solutions for that.
I'm working with a contenteditable iframe that is being using for basic WYSIWYG editing. I've noticed a strange difference in the way that a Tab keypress event is handled between Chrome and Firefox.
When the document of the iframe has been configured using designMode = 'On', a tab pressed inside the document will skip to the next control in Firefox (expected) but create the following pre white-spaced span in Chrome
<span class="Apple-tab-span" style="white-space:pre"> </span>
Here's an example.
Interestingly, when the body of the iframe is setup instead using body.setAttribute("contenteditable", "true"), which I assumed was the same approach done in a different way, both browsers work as i would expect; moving the focus to the next tab index.
Can anyone explain why?
I'm afraid that the only answer is "just because". Don't expect that there's a reason behind how something works in contenteditable. I experienced hundreds of times that no one really cared or had time to care about that. When you've got bugs like https://code.google.com/p/chromium/issues/detail?id=226941 which make contenteditable totally irritating for users on Chrome & Opera and which hasn't been even confirmed by developers throughout entire year, then a small difference in Tab's behaviour is a detail which you have to fix and forget ;).
Use:
document.designMode = 'on';
Insted of
body.setAttribute("contenteditable", "true")
this is insanely annoying problem:
AS3 full screen application based on ADOBE FLEX 4, text field. User types something in text field, and then starts clicking backspace many many times to remove what he just wrote, and for some reason, instead of removing characters from text field it tells browser to GO BACK and user navigates away. Why?! Please, please help, this is so terrible. My users are losing important unsaved this is data while using my application!
i am using safari browser
PLEASE HELP.
Wow, this is terrible, I am so irritated, it happens every single time
It is possible that the focus is lost from your text field when hitting the backspace multiple times (check if you are firing some events on the text field that may cause this), which causes the main window to take focus and trigger 'Back' on the browser.
The root of the problem is that the browser carries out keyboard shortcuts REGARDLESS of the flash app having the focus or not. From what I heard this problem does not exist on Safari's for Mac, only Safari for Windows.
I would check to see what browser you are in and then create a popup saying you this app does NOT work on Safari browser ON windows.
Scratching head*
Well maybe if HAD to solve this, I would use the ExternalInterface to interact with Safari or javascript to PREVENT the history back button from getting applied. So it won't go back to an old page. That is what I would look into.