OWF + WIN7/IE11 Black Screen -

[Brandon C]

-----------------------------------------------------------------------------------------------------------------------------
      <!-- modernizr-->
        <script src="./js-lib/modernizr/modernizr-2.6.2.js"></script>
        <!-- turn off Modernizr-based animations if needed -->
        <script>
            // limit the scope
            ;(function(Ozone, Modernizr) {
                // no animations?
                if (!Ozone.config.showAnimations) {
                    // turn off Modernizr-based animations
                    Modernizr.csstransitions = false;
                    Modernizr.cssanimations = false;
                }
            })(Ozone, Modernizr);
        </script>


Users having problems with Windows 7 / Internet Explorer 11.

F12 shows multiple instances of
"'Modernizr' is undefined" owf-server v7.17.0-1515202181.gz.js (line= shown above)


-----------------------------------------------------------------------------------------------------------------------------

One instance of
'Ozone.version.owfversion' is null or not an object' marketplaceAPI v7.17.0-1515202181.gz.js (line = shown below)

(minified);Ozone.marketplace.util.owfversion=Ozone.version.owfversion;(minified)

-----------------------------------------------------------------------------------------------------------------------------


The OWF works with Chrome and Mozilla Firefox browsers.

On Windows 10 / IE11 it works as well.

This is only affecting Windows 7/IE11 with the latest .Net Framework update.

-----------------------------------------------------------------------------------------------------------------------------

something with Windows 10 with IE11 renders OWF with the defaulted scripts work while the Windows 7 with IE11 returns a black screen and statements being undefined is there something I would need to assist with the library for definitions and statement assumptions?

Thank you.

super perplexed.

[Ross Pokorny]

Brandon

What version of OWF are you using?

Ross Pokorny

On Thursday, September 29, 2016 10:39:44 AM EDT Brandon C wrote:
> ----------------------------------------------------------------------------

[charles...@sage.northcom.mil]

We are seeing the same issue using OWF 7.17.

[charles...@sage.northcom.mil]

It looks like the version of modernizir (2.6.2) bundled w/ OWF 7.17 is quite old, they are now on 3.3.1 ...

[Ross Pokorny]

We have just done some testing and are unable to reproduce this issue.
Additionally, I know that this was not happening earlier this year because
during that time I fixed minor UI issues in OWF that were specific to IE11.
Is this issue something that has just appeared recently or have you always
seen it with OWF 7.17.0?

Would either of you be interested in building OWF from master and seeing if
that version also displays the issue? There are some committed-but-unreleased
patches to OWF that may affect this issue.

Ross Pokorny
Ozone Developer

On Tuesday, October 4, 2016 7:14:40 AM EDT charles...@sage.northcom.mil
wrote:

[Brandon C]

Enter code here...

We are on OWF 7.17.0. 

Last known OWF functionality is September 07, 2016.

Can you give me the unreleased versions to test?

Also we are looking into the Client side to see if somehow Microsoft has pushed something specific to have caused this. 

Thank you for your response. 

___________________________________________________________________________________________________ 

[Ross Pokorny]

When I say unreleased, I simply mean that the new commits haven't been named
as a new "7.17.1" yet. The commits are publicly available on the master
branch of OWF's github repository at https://github.com/ozoneplatform/owf-framework . If you build OWF from source (on the master branch) you will get
the commits I was referring to.

If you don't have a way to build OWF for whatever reason (security
restrictions in your environment for instance) I can build it and we can try
to find a way to send it to you.

Ross Pokorny
Ozone Developer

> > <javascript:>

[Brandon C]

Understood. I do have some restrictions building in my current environment your assumptions are correct. 

If you are able assist in your last message your offer would be of great value in our current situation. 

[mellowT]

Ross,

Thank you for the many fixes to the OWF 7.17.0 baseline in late June, especially the IE11 fixes.  I was unaware of them until today after reading this thread.

As I was looking through the closed issue list I noticed this comment from you in Issue 75 from June 29:

"Those commits will be included in an upcoming 7.17.1 release."

When might this release be scheduled?

Tom

[Brandon C]

Update: We were able to display the OWF application through WIN7/IE11 but only through the IP and not the DNS name. 

Received these errors during debugging:

if ( deep && copy && ( jQuery.isPlainObject(copy) || (copyIsArray = jQuery.isArray(copy)) ) ) {

Object doesn't support this property or method jquery.js, line 218 character 5

// Recurse if we're merging plain objects or arrays

if ( deep && copy && ( jQuery.isPlainObject(copy) || (copyIsArray = jQuery.isArray(copy)) ) ) {

if ( copyIsArray ) {

copyIsArray = false;

clone = src && jQuery.isArray(src) ? src : [];

} else {

clone = src && jQuery.isPlainObject(src) ? src : {};

}

On Wednesday, October 5, 2016 at 4:19:20 AM UTC-7, Ross Pokorny wrote:

When I say unreleased, I simply mean that the new commits haven't been named

as a new "7.17.1" yet.  The comm its are publicly available on the master

[Brandon C]

Update:

Problem was the cache settings. works if clearing cache. modernizr has a  chance to return.

OWF we are finding issues during the debug.  

DOM7011: The code on this page disabled back and forward caching.

[Ross Pokorny]

Brandon

Are you saying that after clearing your browser cache the problems are gone
entirely, aside from that back/forward caching warning?

Ross Pokorny
Ozone Developer

[brandon....@sage.northcom.mil]

Sorry for the 2 years later: 

Server side cache clearing and increased cache threshold assisted with client IE browser sided issues. 

After 2 years this issue has not occurred.