Re: Modernizing IBM i - The User Interface (Part 11) -- WEB400

Subject: Re: Modernizing IBM i - The User Interface (Part 11)
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: Tue, 22 Nov 2016 11:59:22 -0600
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

What little I could find suggests that Microsoft was trying to adopt their own solution for changes over time with something called document modes. It appears they abandoned that path and starting with IE 11 defaulted to IE 7 mode. I followed the instructions and things worked fine for two days, then - wham - back to old behavior.

As of last night both IE 11 and Firefox worked on my local PC and they both worked on my remotely hosted ventures.martinvt.com . Both IE 11 and Firefox failed on an iSeries Apache server connected through a vpn.

On 11/22/2016 4:54 AM, Kevin Turner wrote:

I have never had to do that to be honest, and we don't get cross-domain access errors for xmlHTTPRequests to the same domain as the original.

I wonder what version of IE is causing this error?

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.