I have been encountering this error around textFields for a while now, and I'm trying to make sense of what this error means.
This failure happens sometimes when typing into a text field that contains an "x" button that will clear text. If you start typing into a clear field with no button, the "x" button will appear, and then clicking the "x" causes the field to become blank again and that button disappears as well.
Note that this is a failure that only happens to bots, testing locally works just fine every time.
Typing into fields that don't have a "x" button will always work, this failure is only happening in this specific case. I have already disconnected the hardware keyboard, since the app has no problem typing into other types of text fields without a clear button.
Clicking on the "x" button always passes, but subsequently typing into the cleared field results in the above "Timed out waiting for key event to complete" failure.
Is anyone else experiencing this failure? Is the button appearing in the text field causing Xcode bots to get confused with the page hierarchy? Does anyone have a workaround for this?
Related
I am facing this issue specifically when the user makes following set of actions:
If a user taps on an Input field the keyboard pops up (expected and
fine behavior). However, if a user taps directly to another input
field, without tapping anywhere else keyboard gets hidden (unexpected
and buggy behavior). For me to be able to make keyboard pop again, I
have to tap outside on any non-input field and tap on input field
again.
Not sure if it is related but from looking at other issues, this issue is being faced on Google Chrome (Surface 7). It works fine for Edge browser but I want something that works for Chrome.
I have a form in Access 2013 that uses a button to jump to another form.
However when the button is clicked certain requirements have to be met in order for the jump process to actually be executed. If the requirements are not met the user is forced to stay on the current form (with the button).
When this happens the button stays in the clicked (i.e. pressed down) state on the form, making it look like it's being constantly pressed.
(Note: If the button is clicked again and the requirements again aren't met it pops back out...)
Is there any way to change the appearance of the button back to the unclicked appearance after every click when the user is forced to stay on the current form?
Many thanks in advance for any kind of help!
A regular button can stay depressed for a short while, while its _Click() event procedure is running.
But once that finishes, it always returns to its normal state.
So the assumption was, that a toggle button was used instead, which turned out to be correct.
I have a weird issue regarding a text box within a subform that is within the form i am working on. Usually, I do not get this error when I would normally close out of the form via the Close button that was created on it. If I was to close the form via the tab when I'm doing edits, it causes the error and using the Close button stops it when I reopen it. I have no idea how to fix this so closing it through the tab would also not cause this issue.
If the close button works properly and closing the tab does not, then the close button does more than just close the form. Look at the OnClick code for the close button and transfer the appropriate part of it to the OnClose event of your form.
Most likely it is just something like Me.Dirty = False that writes any unsaved edits to the record but there may be more to it.
(a) TIMTOWTDI =. there is more than one way to do it
(b) TIOOWTDI =. there is only one way to do it
i do not know if the case for this issue is (a) or (b), above.
The follow links may apply to this discussion:
https://developer.mozilla.org/en-US/docs/DOM/window.onbeforeunload
MSDN beforeunload | onbeforeunload event
http://dev.w3.org/html5/spec-LC/history.html#unloading-documents
http://dev.w3.org/html5/spec-LC/history.html#beforeunloadevent
... Note: There are no BeforeUnloadEvent-specific initialization methods.
please note: i am not discussing SO article 276660 "How can I override the OnBeforeUnload dialog and replace it with my own? which is about the text that the end-user sees in the dialog box; i found SO article 276660 via the first reply to this discussion: suggestion: change default for are you sure that you want to navigate away from this page? from OK to Cancel
My issue with how various browsers behave is the need to prevent the end user from losing her/his typed data because she/he accidentally clicked away from a page; such a disaster can easily occur if she/he happens to press the space bar shortly after the dialog box has been displayed; "disaster" may seem like a very strong word unless you are the end user who has just lost an hour or two of typing.
i. is JavaScript the only way to prevent this?
ii. is there some way to tell the end users' browsers to make Cancel the default?
Clarification (i hope): in a Windows O/S dialog box, it is possible to tell the Windows O/S which button to highlight as the default; for example, if the message were something like "delete all of my files", a default of "OK" is a bad idea.
SO frequently saves my text as i'm composing a question; other forums do not do the same.
i'm guessing that if my laptop were to crash as i'm writing this message then SO would give me some way to recover close to the point where i am at this moment.
Will someone please tell me whether there are one or more ways with regards to browsers, and, if there are, where to find more information?
imho, setting the default dialog box button to "OK" is far too dangerous because accidentally hitting the space bar could cause a lot of grief.
Thank you.
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.