New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 789953 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Latest Chrome versions not rendering the content properly on a click/action

Reported by krishnak...@gmail.com, Nov 30 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Example URL:
http://testchromedefectserver.mybluemix.net/analytics/console

Steps to reproduce the problem:
Following scenarios were working fine with Chrome until V54. After version 54 all the three scenarios not working fine only on chrome browser (other browsers like Mozilla FF, Safari, ... it works well)

Login Credentials :

UserId: admin
Password: admin

Note: Initial Loading of the entire page takes nearly 2 min first attempt. That is not the problem here. Please ignore that page response time.

Scenario-1: 

1. Go to the following URL -
 http://testchromedefectserver.mybluemix.net/analytics/console/clientLogs
2. Click on the Search Button (Magnifier Icon)
3. You can see the Request is placed with the loading gif icon on the result view
4. Now Click on the Date Filter (Change from Today to some other day)
5. Click on the Search Button Again, you can see the request doesn't get triggered. Click of search button does not invoke any action.

Scenario-2:

1. Go to the following URL -
 http://testchromedefectserver.mybluemix.net/analytics/console/serverSearch
2. Click on the Search Button (Magnifier Icon)
3. You can see the Request is placed with the loading gif icon on the result view
4. Now Click on the Date Filter (Change from Today to some other day)
5. Click on the Search Button Again, you can see the request doesn't get triggered. Click of search button does not invoke any action.

Scenario-3:

1. Go to the following URL -
 http://testchromedefectserver.mybluemix.net/analytics/console/exportData
2. Select any "Event Type" from the dropdown
3. Click on the "EXPORT" button. You can see the file getting exported with a prompt seen to save the file.
4. Now Uncheck the "Default" checkbox and Click on the Date Filter (Change from Today to some other day)
5. Now onwards you wont be able to select the Default Checkbox again, also export button doesnt search button does not invoke any action.

Find the screenshots for all the three scenarios for reference (with markers to highlight the fields)

What is the expected behavior?
Explained in the above Steps itself.

What went wrong?
Certain functionalities especially action invoke doesn't happen on our web app. One deployment is setup for recreating or viewing the explained issue.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes v54

Does this work in other browsers? Yes

Chrome version: 62.0.3202.94  Channel: stable
OS Version: OS X 10.10.5
Flash Version:
 
Scenario-I.png
74.7 KB View Download
Scenario-II.png
56.7 KB View Download
Scenario-III.png
99 KB View Download
Exact Last version of Chrome Browser the app worked well was in v54.0.2840.71
Labels: Needs-Bisect
Cc: divya.pa...@techmahindra.com
Labels: Triaged-ET Needs-Triage-M62 Needs-Feedback
Tried testing this issue, as there is no option to register on the given link, If shareable could you please provide test credentials that would help us in triaging the issue from TE-end. 
I have added the credentials in the description itself. Sharing it again


Login Credentials :

UserId: admin
Password: admin


Project Member

Comment 5 by sheriffbot@chromium.org, Dec 1 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
I believe this code is wrong:

            if (a.dispatchEvent && document.createEvent) {
                var d = a.ownerDocument || document
                  , e = d.createEvent("HTMLEvents");
                e.initEvent(b, !!c.bubbles, !!c.cancelable);
                for (var f in c)
                    f in e || (e[f] = c[f]);
                return a.dispatchEvent(e) && e
            }

Try adjusting this to something like this:

e = d.createElement(b == "click" ? "MouseEvents" : "HTMLEvents")

The event you are creating and dispatching is the wrong type.
One question, in that case could you clarify why was it working till chromed v54.x versions and before.

Also Other than chrome every other browser handles the events correctly.

Thank you

Sign in to add a comment