1278154 - iframe link will not auto-focus in ScienceLogic EM7

Status: RESOLVED WONTFIX

(Web Compatibility :: Site Reports, defect)

Description

[Knowguy]

Attachment: tickets_simple.7z

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160605030215

Steps to reproduce:

Spent a few hourse tracking down exact issue why certain fields were not auto-focusing. This same issue is present in all but Chrome. (Developer of web app that utilizes this will likely never address.  Most people in my organization settle for Chrome because of this, I refuse).

Open attached zip file
Inside tickets_simple main directory
Open test.htm
Click Thickbox example link text.
Opened iframe should have auto-focused under description search field.
Open test.htm with Chrome(Chromium, or Chrome clone).
iframe will have auto-focus in correct search field.





Actual results:

Search field does not auto-focus.  Only works under Chrome (does NOT work under, IE, Edge, or Firefox). 




Expected results:

Field should have auto-focus. This small detail allows work to be done without use of mouse and shaves time off of processes.

Comment 1

[Emil Pasca [:emilpasca]]

User Agent:  Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0

I have tested this issue on Windows 10 x64 with the latest Firefox release (47.0) and the latest Nightly (50.0a1-20160608030219) and managed to reproduce it.
After following the provided steps in the description, when opening test.htm the search field under the description in the iframe, it does not have auto-focus.
I have also tested the same steps on Chrome and the search field has auto-focus.

Comment 2

[Andrew Overholt [:overholt]]

Neil, do you know what's up here? (It was almost a toss of the coin between you and Olli :)

Comment 3

[Neil Deakin]

The page is trying to focus an element inside an iframe with visibility:hidden.

Comment 4

[Andrew Overholt [:overholt]]

I had hoped to dig into this but I am evidently not getting to it soon ...

Is the page in question just wrong (see comment 3)? (TIA for the help, Mike)

Comment 5

[Mike Taylor [:miketaylr]]

I think this is probably just invalid... I'm not sure why or how Chrome gets it to work, but ideally the author should be waiting to focus the input element on the iframes load event (assuming its visible at that point).

Comment 6

[Hsin-Yi Tsai (she/her)[:hsinyi]]

Close as Invalid as comment 5 suggests. Thanks!

Comment 7

[Knowguy]

This is disappointing. Will have to switch to Chrome for network monitoring at work now.

Comment 8

[Knowguy]

I would love to sit down with someone and provide my login information to you show you the exact issue and how vital it is.

Comment 9

[Mike Taylor [:miketaylr]]

Hey Jesse -- sorry that it's disappointing. IMO, this isn't a bug in Firefox, but a bug in the assumptions that thickbox plus the app makes. It should be possible to fix, as long as you're waiting until the iframe is visible and loaded before calling .focus() on the input element.

Comment 10

[Neil Deakin]

Yes, it looks even for a simple testcase where the frame is already loaded, Chrome and Safari allow script to focus content inside a iframe with visibility: hidden, but don't allow tabbing to it. Firefox and IE11 do not have this issue. So this looks code that is relying on a Chrome bug.

Comment 11

[Mike Conley (:mconley) (:⚙️)]

Hey Jesse,

So it sounds like the best course of action would be to get the web site you're referring to to not rely on this strange Chrome behaviour, and be more cross-browser friendly.

Can you provide us with more information about where this site / application is hosted, so that perhaps someone from our Web Compatibility team can reach out to the developers?

Thanks!

Comment 12

[Knowguy]

The product is EM7, a network monitoring suite developed by ScienceLogic [ https://www.sciencelogic.com/ ]. Hopefully someone can get their attention from Mozilla. I know a lot of NOC people would rather use Firefox with this suite it is just so bad that you cannot help but seek out an alternative, performance wise.  Which I also have a performance bug opened for this same suite: [ https://bugzilla.mozilla.org/show_bug.cgi?id=1277206 ]

Comment 13

[Mike Taylor [:miketaylr]]

(whoops, I had assumed you were the site owner Jesse)

Let's go ahead and re-open/move this to a tech evangelism bug then -- see comment #9 for the recommended fix.

Comment 14

[Karl Dubost💡 :karlcow]

1st attempt  at contacting the CTO. Antonio Piraino
http://twitter.com/MozWebCompat/status/780563163112628224


Probably at https://github.com/apiraino/ too.

Comment 15

[Knowguy]

Registered with EM7 support and was able to file a ticket there: Ticket ID: 112185

Comment 16

[Karl Dubost💡 :karlcow]

> @MozWebCompat can you get the end customer to please open a ticket with us if there is an issue?  many thanks.
http://twitter.com/antoniopiraino/status/780810414846316544

per Comment #15 I guess it has been done.
Thanks Jesse.

Comment 17

[Knowguy]

As expected ScienceLogic will not address this issue since they themselves said that using Chrome was an effective work around.  So far every bug or issue I have had with Firefox I have yet to get fixed. IE: https://bugzilla.mozilla.org/show_bug.cgi?id=1277206

Comment 18

[Mike Taylor [:miketaylr]]

Sorry to hear that Jesse -- in this instance it's not really something we can fix for ScienceLogic. :/