Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#18888 closed defect (fixed)

BackgroundIframe not enabled for IE11/Win10

Reported by: Earl Hood Owned by: Michael Van Sickle <mvansickle@…>
Priority: undecided Milestone: 1.12
Component: Dijit Version: 1.11.2
Keywords: Cc:
Blocked By: Blocking:

Description

The BackgroundIframe? is not enabled for IE11 under Windows 10 environments. Because of this, popups, et.al. do not show when popped up over an ActiveX control.

Examining dijit/BackgroundIframe.js, the Windows OS version check needs to be updated to check for "Windows 10.0". For example:

    has.add("config-bgIframe",
        (has("ie") && !/IEMobile\/10\.0/.test(navigator.userAgent)) || // No iframe on WP8, to match 1.9 behavior
        (has("trident") && /Windows NT (?:6\.[01]|10\.0)/.test(navigator.userAgent)));

Workaround for existing (1.11.2) and previous releases of the toolkit can has.add("config-bgIframe") before dijit/BackgroundIframe is loaded to supercede the test for those that need to support IE11/ActiveX/Win10 environments.

Change History (6)

comment:1 Changed 3 years ago by Earl Hood

Windows 8(.1) should also be supported. That would update the has.add() to the following:

    has.add("config-bgIframe",
        (has("ie") && !/IEMobile\/10\.0/.test(navigator.userAgent)) || // No iframe on WP8, to match 1.9 behavior
        (has("trident") && /Windows NT (?:6\.[0-3]|10\.0)/.test(navigator.userAgent)));

comment:2 Changed 3 years ago by dylan

Milestone: tbd1.12

comment:3 Changed 3 years ago by bill

My testing showed that the BackgroundIFrame was only needed for IE11 on Win7. That's why I wrote the code to limit to that case. Apparently you are seeing cases where it's needed on IE11 on Win10?

comment:4 Changed 3 years ago by Michael Van Sickle <mvansickle@…>

Owner: set to Michael Van Sickle <mvansickle@…>
Resolution: fixed
Status: newclosed

In c07a4cd/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:5 Changed 3 years ago by Michael Van Sickle <mvansickle@…>

In 68a5c50/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 

comment:6 Changed 3 years ago by Michael Van Sickle <mvansickle@…>

In 9dcc39aa/dijit:

Error: Processor CommitTicketReference failed
Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? 
Note: See TracTickets for help on using tickets.