1347114 - sap products have dependencies on focusin/focusout *not* being implemented in Gecko

Status: RESOLVED WONTFIX

(Web Compatibility :: Site Reports, defect, P5)

Description

[Andreas]

Attachment: DropDown.gif

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170302120751

Steps to reproduce:

Since Firefox Version 52 i can't select items in a drop down list on different internal SAP sites in our company. Version 51 works fine.


Actual results:

see attachment

Comment 1

[YF (Yang)]

Can you make this to a publicly available testcase?


Did you test with a fresh profile?
https://support.mozilla.org/t5/Install-and-Update/Use-the-Profile-Manager-to-create-and-remove-Firefox-profiles/ta-p/2914

Did you test with e10s disabled?
https://wiki.mozilla.org/Electrolysis#Firefox_Release

Comment 2

[Andreas]

How can i make it publicly? is my first report.


I have tested the following:

- new profil = dosn't work, same result, can't select entries 
- e10s disabled (about:support = 0/1) = dosn't work, same result, can't select entries 
- tested on another PC, upgrade from FF 51.0.1 to FF 52 = same result, can't select entries from dropdown

- downgrade FF 52 to 51.0.2 = i can select the entries again

Comment 3

[YF (Yang)]

Can you provide a publicly available page for reproduce?

Comment 4

[Mats Palmgren (inactive)]

Note that we don't need the entire page, just the <select> that isn't working +
any surrounding HTML/CSS/JS needed to reproduce the problem.
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Reducing_testcases

Comment 5

[Andreas]

Attachment: Page.zip

I have added the downloaded page. But the dropdown box dosen't work with this copy.
I this enough?

Comment 6

[YF (Yang)]

(In reply to Andreas from comment #5)
> Created attachment 8848406 [details]
> Page.zip
> 
> I have added the downloaded page. But the dropdown box dosen't work with
> this copy.
> I this enough?

I don't see the drop down list / don't works.

Comment 7

[Mats Palmgren (inactive)]

(In reply to Andreas from comment #5)
> I this enough?

No, I need to see the dropdown box and the context around it to determine
what the problem is.

You should report this problem to SAP too, to make them aware of it.

Comment 8

[Andreas]

Attachment: Page2.zip

I have found another page with the same problem. 
I've also downloaded the site and the local copy works with the dropdown problem.
See page2.zip

I will make also a ticket on monday at SAP.

Comment 9

[Andreas]

In the field "Sprache", can't select the english entry.

Comment 10

[YF (Yang)]

Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=01927ad414ea0925f976b191c2db41a0d0152ae9&tochange=aa39c1a962ffa63c1c5017b8c824663dea930771

aa39c1a962ff	Kevin Wern — Bug 687787: support focusin/focusout based on webkit/blink r=smaug

Comment 11

[Mats Palmgren (inactive)]

Fwiw, I suspect the SAP application code depends on focusin/focusout *not* being implemented
in Gecko, rather than a bug in our implementation.

The reporter said he would file a ticket with SAP on monday, but we could also contact them
separately I guess...  It might speed up a fix.
Karl, do we have contacts at SAP?

Comment 12

[Karl Dubost💡 :karlcow]

So we do not have a specific contact with SAP from the top of my head. And I don't see any specific contacts in my mail archive. Let's see.

There are a couple of people listed there that we could attend to contact.
https://github.com/orgs/SAP/people
but it would be good to know which type of sites/app was used for this dropdown before contacting. So we can help them locate the issue.

Andreas could you tell us which product?
Thanks.

Comment 13

[Andreas]

Affected applications in our company:

- SAP Identity Management
- SAP Solution Manager (only dropdown box on login page)
- SAP Human Capital Management

Comment 14

[Mike Taylor [:miketaylr]]

Dees, do you happen to have any contacts at SAP?

Comment 15

[Desigan Chinniah [:cyberdees] [:dees] [London - GMT]]

(In reply to Mike Taylor [:miketaylr] from comment #14)
> Dees, do you happen to have any contacts at SAP?

A few (but not super strong). Let me see if anyone has a route into anyone working within either of the products mentioned in Comment 13.

Comment 16

[Alexander Wickmann]

We have the same problem with our SAP Application, based on EHP6 FOR SAP ERP 6.0

Comment 17

[Desigan Chinniah [:cyberdees] [:dees] [London - GMT]]

Initial feedback from internal SAP contacts (after they made some inquiries) was:

===
"they told me that it would be best if you go to this site: 

Please guide Chinniah to the SAP Support Portal: https://support.sap.com/home.html
 
Here customers can create incidents which are then handled accordingly by the appropriate teams. This should normally work as the other colleagues will take care of all questions etc. and they are very responsive."
===

Mike/Karl — worth trying...

Comment 18

[Mike Taylor [:miketaylr]]

Thanks Dees. It looks like a SAP customer will need to do that then, from what I can tell glancing at the site.

Comment 19

[Andreas]

Maybe this is the solution.
https://launchpad.support.sap.com/#/notes/2452731

But currently not implemented in our SAP systems.

Comment 20

[Karl Dubost💡 :karlcow]

Andreas the content of this page is only accessible to registered users.
Can you summarize the answer here? Thanks.

Comment 21

[Andreas]

Attachment: Problem describtion from SAP

Comment 22

[Andreas]

Attachment: Problem Solution from SAP - Note: 2428821

Comment 23

[Andreas]

I have added the two relevant notes from SAP.

Comment 24

[Nathan Froyd [:froydnj]]

If I'm reading attachment 8857815 [details] correctly, it sounds like SAP has already fixed this problem, and any customers who are affected need to download the appropriate fix from SAP and apply it to their systems.  Is that correct?

Comment 25

[Liz Henry (:lizzard) (relman/hg->git project)]

So far, it sounds like the issue may be in SAP. 
Even if it isn't, too late to fix in 53.

Comment 26

[Nathan Froyd [:froydnj]]

Not going to fix this for 55 at this point.

Karl, is there anything left to do here?  We haven't heard from the original reporter in five months, can we just close this as RESOLVED INCOMPLETE?

Comment 27

[Andreas]

Hello Nathan,

Sorry for the late response.

We have not yet installed SAP's patch because it's a kernel patch.
And the Firefox is not officially supported in our company, so the patch does not have the highest priority.
That's why I can't tell if it works.

Perhaps Alexander Wickmann (comment 16) can give a positive report?

Best regards
Andreas

Comment 28

[Alexander Wickmann]

Hello Nathan,

we have the same Problem like Andreas. Firefox is not officially supported in our company and for our service provider the SAP Patch have not the highest priority. 

Regards
Alex

Comment 29

[Oana Arbuzov [:oanaarbuzov]]

Unfortunately I don't have access to SAP, does the issue still occurs Andreas on your side?

Comment 30

[Andreas]

(In reply to Oana Arbuzov [:oanaarbuzov] from comment #29)

Unfortunately I don't have access to SAP, does the issue still occurs Andreas on your side?

Yes, the problem is still present (75.5.0esr)

Comment 31

[Dennis Schubert [:denschub]]

Am I understanding this correctly that there is a patch from SAP, that fixes the issue, but that the installations in question have not updated/applied that?

Comment 32

[Andreas]

(In reply to Dennis Schubert [:denschub] from comment #31)

Am I understanding this correctly that there is a patch from SAP, that fixes the issue, but that the installations in question have not updated/applied that?

Yes, that's right.
Our SAP Basis Team says that the patch is a kernel update and requires a lot of preparation.
And Firefox is still not officially supported in our company, this problem is not a high priority for our SAP Basis. rolleys

But from my side, the ticket can be closed. Since I am now working with Edge Chromium in the company.

Comment 33

[Dennis Schubert [:denschub]]

I understand that's annoying, yeah. But realistically, there's nothing we can do on our side, as any change to DOM events always break a ton of other sites... Given a patch exists from SAP for more than three years now, I'll close this. This isn't really in our control.

Thanks for your feedback, I really appreciate that.