Textbox in Firefox cannot CTRL + V (Paste) after some updates












1















Before some Firefox update, my app is working fine but after that I cannot CTRL + V (doing Right Click -> Paste is still working fine) anymore. Any idea for this problem?



This is aspx code on the page:



<td width="50%">
<input type="text" maxlength="10" id="RequestID" value="<% =RequestId %>" name="Request_ID"
onload="document.LBS.Request_ID.focus()" onkeypress="if (fnCheckKeyPress(event) == false) {event.returnValue = false; return false;}" />
</td>


The problem is on the "onkeypress" field. If I delete that then it works just fine, but it cannot filter text (it suppose to have only digits) anymore. The function is called from the js file:



function fnCheckKeyPress(event) {
// KeyCode Info: 13-ENTER ; 27-ESC ; 9-TAB ; 8-BACKSPACE ; 46-DELETE
var nKeyCode = event.keyCode ? event.keyCode : event.which ? event.which : event.charCode;
//alert(nKeyCode);
if (nKeyCode == 13) return false;
if (navigator.userAgent.indexOf("Firefox") != -1) {
if (event.keyCode >= 3 && event.keyCode <= 39) return true;
if (arguments.length > 0 && arguments[0].isChar == false && arguments[0].ctrlKey == true) return true;
}
if (nKeyCode < 46 || nKeyCode > 57) return false;
return true;


}










share|improve this question




















  • 1





    Uhhh .. use input event instead of that awful mess ... and onload is not triggered by an input element, it fires only when external resources are loaded.

    – Teemu
    Nov 22 '18 at 11:19













  • Sorry edited, the problem is on the "onkeypress" field.

    – Vu Tran
    Nov 22 '18 at 11:22











  • No, the problem is the use of keypress event, which is not suitable for your purposes at all. As said before, use input event instead.

    – Teemu
    Nov 22 '18 at 11:23













  • Hi, this problem is not happen on Chrome or IE, just on Firefox.... and I'm not editing anything on this page since 3 years ago. That's why I think the problem may comes from Firefox updates.

    – Vu Tran
    Nov 22 '18 at 11:27











  • It's time to edit it, see also keyCode and what else ... Your page is going to stop working in any browser on any upcoming update ... very soon, the warning has been there for a couple of years now.

    – Teemu
    Nov 22 '18 at 11:28


















1















Before some Firefox update, my app is working fine but after that I cannot CTRL + V (doing Right Click -> Paste is still working fine) anymore. Any idea for this problem?



This is aspx code on the page:



<td width="50%">
<input type="text" maxlength="10" id="RequestID" value="<% =RequestId %>" name="Request_ID"
onload="document.LBS.Request_ID.focus()" onkeypress="if (fnCheckKeyPress(event) == false) {event.returnValue = false; return false;}" />
</td>


The problem is on the "onkeypress" field. If I delete that then it works just fine, but it cannot filter text (it suppose to have only digits) anymore. The function is called from the js file:



function fnCheckKeyPress(event) {
// KeyCode Info: 13-ENTER ; 27-ESC ; 9-TAB ; 8-BACKSPACE ; 46-DELETE
var nKeyCode = event.keyCode ? event.keyCode : event.which ? event.which : event.charCode;
//alert(nKeyCode);
if (nKeyCode == 13) return false;
if (navigator.userAgent.indexOf("Firefox") != -1) {
if (event.keyCode >= 3 && event.keyCode <= 39) return true;
if (arguments.length > 0 && arguments[0].isChar == false && arguments[0].ctrlKey == true) return true;
}
if (nKeyCode < 46 || nKeyCode > 57) return false;
return true;


}










share|improve this question




















  • 1





    Uhhh .. use input event instead of that awful mess ... and onload is not triggered by an input element, it fires only when external resources are loaded.

    – Teemu
    Nov 22 '18 at 11:19













  • Sorry edited, the problem is on the "onkeypress" field.

    – Vu Tran
    Nov 22 '18 at 11:22











  • No, the problem is the use of keypress event, which is not suitable for your purposes at all. As said before, use input event instead.

    – Teemu
    Nov 22 '18 at 11:23













  • Hi, this problem is not happen on Chrome or IE, just on Firefox.... and I'm not editing anything on this page since 3 years ago. That's why I think the problem may comes from Firefox updates.

    – Vu Tran
    Nov 22 '18 at 11:27











  • It's time to edit it, see also keyCode and what else ... Your page is going to stop working in any browser on any upcoming update ... very soon, the warning has been there for a couple of years now.

    – Teemu
    Nov 22 '18 at 11:28
















1












1








1








Before some Firefox update, my app is working fine but after that I cannot CTRL + V (doing Right Click -> Paste is still working fine) anymore. Any idea for this problem?



This is aspx code on the page:



<td width="50%">
<input type="text" maxlength="10" id="RequestID" value="<% =RequestId %>" name="Request_ID"
onload="document.LBS.Request_ID.focus()" onkeypress="if (fnCheckKeyPress(event) == false) {event.returnValue = false; return false;}" />
</td>


The problem is on the "onkeypress" field. If I delete that then it works just fine, but it cannot filter text (it suppose to have only digits) anymore. The function is called from the js file:



function fnCheckKeyPress(event) {
// KeyCode Info: 13-ENTER ; 27-ESC ; 9-TAB ; 8-BACKSPACE ; 46-DELETE
var nKeyCode = event.keyCode ? event.keyCode : event.which ? event.which : event.charCode;
//alert(nKeyCode);
if (nKeyCode == 13) return false;
if (navigator.userAgent.indexOf("Firefox") != -1) {
if (event.keyCode >= 3 && event.keyCode <= 39) return true;
if (arguments.length > 0 && arguments[0].isChar == false && arguments[0].ctrlKey == true) return true;
}
if (nKeyCode < 46 || nKeyCode > 57) return false;
return true;


}










share|improve this question
















Before some Firefox update, my app is working fine but after that I cannot CTRL + V (doing Right Click -> Paste is still working fine) anymore. Any idea for this problem?



This is aspx code on the page:



<td width="50%">
<input type="text" maxlength="10" id="RequestID" value="<% =RequestId %>" name="Request_ID"
onload="document.LBS.Request_ID.focus()" onkeypress="if (fnCheckKeyPress(event) == false) {event.returnValue = false; return false;}" />
</td>


The problem is on the "onkeypress" field. If I delete that then it works just fine, but it cannot filter text (it suppose to have only digits) anymore. The function is called from the js file:



function fnCheckKeyPress(event) {
// KeyCode Info: 13-ENTER ; 27-ESC ; 9-TAB ; 8-BACKSPACE ; 46-DELETE
var nKeyCode = event.keyCode ? event.keyCode : event.which ? event.which : event.charCode;
//alert(nKeyCode);
if (nKeyCode == 13) return false;
if (navigator.userAgent.indexOf("Firefox") != -1) {
if (event.keyCode >= 3 && event.keyCode <= 39) return true;
if (arguments.length > 0 && arguments[0].isChar == false && arguments[0].ctrlKey == true) return true;
}
if (nKeyCode < 46 || nKeyCode > 57) return false;
return true;


}







javascript c# asp.net .net firefox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 11:22







Vu Tran

















asked Nov 22 '18 at 11:17









Vu TranVu Tran

62




62








  • 1





    Uhhh .. use input event instead of that awful mess ... and onload is not triggered by an input element, it fires only when external resources are loaded.

    – Teemu
    Nov 22 '18 at 11:19













  • Sorry edited, the problem is on the "onkeypress" field.

    – Vu Tran
    Nov 22 '18 at 11:22











  • No, the problem is the use of keypress event, which is not suitable for your purposes at all. As said before, use input event instead.

    – Teemu
    Nov 22 '18 at 11:23













  • Hi, this problem is not happen on Chrome or IE, just on Firefox.... and I'm not editing anything on this page since 3 years ago. That's why I think the problem may comes from Firefox updates.

    – Vu Tran
    Nov 22 '18 at 11:27











  • It's time to edit it, see also keyCode and what else ... Your page is going to stop working in any browser on any upcoming update ... very soon, the warning has been there for a couple of years now.

    – Teemu
    Nov 22 '18 at 11:28
















  • 1





    Uhhh .. use input event instead of that awful mess ... and onload is not triggered by an input element, it fires only when external resources are loaded.

    – Teemu
    Nov 22 '18 at 11:19













  • Sorry edited, the problem is on the "onkeypress" field.

    – Vu Tran
    Nov 22 '18 at 11:22











  • No, the problem is the use of keypress event, which is not suitable for your purposes at all. As said before, use input event instead.

    – Teemu
    Nov 22 '18 at 11:23













  • Hi, this problem is not happen on Chrome or IE, just on Firefox.... and I'm not editing anything on this page since 3 years ago. That's why I think the problem may comes from Firefox updates.

    – Vu Tran
    Nov 22 '18 at 11:27











  • It's time to edit it, see also keyCode and what else ... Your page is going to stop working in any browser on any upcoming update ... very soon, the warning has been there for a couple of years now.

    – Teemu
    Nov 22 '18 at 11:28










1




1





Uhhh .. use input event instead of that awful mess ... and onload is not triggered by an input element, it fires only when external resources are loaded.

– Teemu
Nov 22 '18 at 11:19







Uhhh .. use input event instead of that awful mess ... and onload is not triggered by an input element, it fires only when external resources are loaded.

– Teemu
Nov 22 '18 at 11:19















Sorry edited, the problem is on the "onkeypress" field.

– Vu Tran
Nov 22 '18 at 11:22





Sorry edited, the problem is on the "onkeypress" field.

– Vu Tran
Nov 22 '18 at 11:22













No, the problem is the use of keypress event, which is not suitable for your purposes at all. As said before, use input event instead.

– Teemu
Nov 22 '18 at 11:23







No, the problem is the use of keypress event, which is not suitable for your purposes at all. As said before, use input event instead.

– Teemu
Nov 22 '18 at 11:23















Hi, this problem is not happen on Chrome or IE, just on Firefox.... and I'm not editing anything on this page since 3 years ago. That's why I think the problem may comes from Firefox updates.

– Vu Tran
Nov 22 '18 at 11:27





Hi, this problem is not happen on Chrome or IE, just on Firefox.... and I'm not editing anything on this page since 3 years ago. That's why I think the problem may comes from Firefox updates.

– Vu Tran
Nov 22 '18 at 11:27













It's time to edit it, see also keyCode and what else ... Your page is going to stop working in any browser on any upcoming update ... very soon, the warning has been there for a couple of years now.

– Teemu
Nov 22 '18 at 11:28







It's time to edit it, see also keyCode and what else ... Your page is going to stop working in any browser on any upcoming update ... very soon, the warning has been there for a couple of years now.

– Teemu
Nov 22 '18 at 11:28














0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429791%2ftextbox-in-firefox-cannot-ctrl-v-paste-after-some-updates%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429791%2ftextbox-in-firefox-cannot-ctrl-v-paste-after-some-updates%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Create new schema in PostgreSQL using DBeaver

Deepest pit of an array with Javascript: test on Codility

Costa Masnaga