My cursor is right where it needs to be in my text editor - visually. When I continue typing from the keyboard - nothing is shown. The cursor is in the browser (when I press up-down arrow keys from the keyboard - the browser page is moved up/down). I need to click on the text editor so that I can continue typing. Even though the cursor is visible and blinking in the text editor. I use tinymce and ie9. (I use ie9 just for testing purposes, I'm not crazy).
When I execute:
document.activeElement
it returns that an iframe element has focus, and not the text area.
Related
I'm using ReactJS and I have a lot of <button> in my code. I notice that I can use the Tab key to move over the button and there will be an outline on focused button like this:
But on this website which I'm trying to replicate, the buttons they use do not get Tab-focused on normal but just when we turn on the VoiceOver accessibility mode.
And the border of the Tab focus is also different.
I wonder how can we implement this in React?
Changing tabIndex to 0 or -1 doesn't work.
Thanks everyone!
Update
I ask because this leads to a problem:
If I use the UI Keyboard (UIKB) first and then try to type with the real keyboard keydown event. The tab focus would just stuck on the UIKB letter and return it twice.
This doesn't happen on the Wordle game because they just allow using tab focus when in accessibility mode.
tabIndex = -1 doesn't work because I want to allow the user use the tab focus just in a11y mode like Wordle, I don't want to totally disable it.
I'm using Firefox to get information of a HTML website in order to do some automation with Python and Selenium. So far, stuff was great and worked as expected.
Now I have the following situation:
An element appears only when moving the mouse over an item, activated by JavaScript.
Once I move the mouse away, the element disappears, again by JavaScript.
How do I stop JavaScript immediately after I have identified the element?
I have tried:
deactivating JavaScript completely. But then the element does not even appear.
deactivating JavaScript after I used the inspector . However, pressing F8 does not work, because I'm not on the debugger tab, but in the inspector tab. I can't move my mouse since the element disappears.
Use keyboard shortcuts to switch to the debugger tab. I.e.
Use to identify the element
Do not move the mouse once you hover over the element
Press Ctrl+Shift+Z to activate the debugger tab
Press F8 to pause execution
Use the mouse or press Ctrl+Shift+C to go back to the inspector tab and analyze the element
I have a simple form containing rich text box. When trying to navigate using the cursor keys from it beeps if the caret can't be moved - for example, pressing Home key when the caret is already on start of line, or trying to move line up when the caret is already on top line. Is there a way to disable those beeps?
If you want to disable the ding (beeps) noise from being triggered each time when you press cursor keys or home key, then unfortunately it doesn't seems to be possible. But yeah, you can do it in some specific ways (i.e. using AcceptButton, CancelButton form property described in this SO thread.
I've got a WPF form inside a window and a short series of events like this:
1) 1st form has series of selection buttons
2) Clicking a button brings up a progress bar window over the existing window
3) Progress window closes and 1st form switches to a new 2nd form using page navigation
The problem is that the 2nd form (and the entire window) no longer has any focus and what's really killing me is that the window is no longer getting OnKeyDown() calls (it's still the top winow). If I hit the tab key the first menu option is highlighted and the following key stroke will fire a OnKeyDown(). Also, if I alt-tab to another app and then alt-tab back to my window it will begin receiving OnKeyDown() again.
How do I figure out where the focus is after the dialog?
If you are using navigation then the focus will have switched to the Page that you have navigated to, assuming that it is Focusable.
You can check that by setting up a breakpoint in a Focused event handle for the Page.
Alternatively you can use an explicit control.SetFocus() in the page.Navigated handler.
After clicking, for example, on a button with no handler (that is no any reation axcept button clicking animation) I have this ugly effect on my eyes:
Blurring of the text on the button goes off in a second (from the first picture to the second and so on to the sharpness), then the text gets sharpness. I have this effect at any combinations of "TextOptions" options in XAML including TextOptions.TextFormattingMode="Display".
If I click on a button which raises, for example, select file dialog window, everything seems well.
How to escape this blur? Have you ever seen this effect?
In addition. This effect appears only with TextSize=11 and Aero is disabled. With TextSize equals any another value all goes well. But 11 is a default value so everybody can see this bug!
I don't know if you've fixed this yet or not, but the solution is to use the flag UseLayoutRounding="True". Throw that on the button style and it will be fixed.