New issue
Advanced search Search tips

Issue 839335 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Hi All, I'm a frontend developer and I've been using Chrome for ever to test local aspx files. These are typically simple HTML files saved with the .aspx extension. Since the update to 66.0.3359.139 was installed, the browsers some text-boxes are not allowing to type or change. Has anyone else seen this issue or found a resolution?

Reported by atul.ba...@thinkinno.com, May 3 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Textboxes in page
2. 
3. 

What is the expected behavior?
It should allow typing numbers of characters in it. in previous versions, it is allowing.

What went wrong?
No idea.

Did this work before? N/A 

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 

Comment 1 by woxxom@gmail.com, May 3 2018

Searching for "local aspx" on this bug tracker doesn't reveal anything related:
https://bugs.chromium.org/p/chromium/issues/list?can=1&q=local+aspx&sort=-modified

Apparently you're the first one.
It means you or someone else has to provide a file or set of files that reproduces the problem.

I have a key down event on textbox and checks window.event, but there it shows 'Load' event instead of 'KeyDown' event and my condition is working on KeyDown event, so it gets false. but this is working in previous versions.

Comment 3 by woxxom@gmail.com, May 3 2018

Well, without a demo file there's nothing to work on.
Maybe you can do the bisect yourself then:
https://www.chromium.org/developers/bisect-builds-py
Labels: Needs-Triage-M66
Labels: Needs-Feedback Triaged-ET
Thanks for filing the issue!

@Reporter: Could you please provide sample test file/URL that reproduces the issue which helps us in further triaging it.

Thanks!
I have resolved this in following way

Previous code
 var g_nameOnly = function()
{
        var curKeyCd;
        curKeyCd   = window.event ? event.keyCode : event.which;
        
}

 Changed to 
 var g_nameOnly = function(e)
{
        var curKeyCd;
        curKeyCd   = e ? e.keyCode  : event.which;
        
}

   this window.event gives 'Load' event on keyboard click but the previous Google chrome version was working fine. When I passed e in parameter then it gives me proper keyboard event. 
 
   
Project Member

Comment 7 by sheriffbot@chromium.org, May 7 2018

Cc: viswa.karala@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: susan.boorgula@chromium.org
Labels: Needs-Feedback
atul.barot@ Thanks for the update.

As per comment #6, can you please confirm if this issue can be closed?

Thanks..
Status: WontFix (was: Unconfirmed)
Closing due to lack of feedback.

Sign in to add a comment