On Fri Apr 20 2018 22:14:04 GMT-0400 (Eastern Standard Time), John R.
Sweet wrote:
> This conflict between "modern javascript" and legacy extensions --
> or whatever the heck is going on -- is a really bad situation. We
> need a couple of extensions that won't work past v 52esr and the
> later > v
erprise-boun...@mozilla.org] On Behalf Of
> >> Perry Wagle
> >> Sent: April 18, 2018 12:49 PM
> >> To: Enterprise@mozilla.org
> >> Subject: [Mozilla Enterprise] ESR52 vs "modern" javascript
> >>
> >> ESR52 produces blank pages when more a
>
> >> -Original Message-
> >> From: Enterprise [mailto:enterprise-boun...@mozilla.org] On Behalf
> >> Of Perry Wagle
> >> Sent: April 18, 2018 12:49 PM
> >> To: Enterprise@mozilla.org
> >> Subject: [Mozilla Enterprise] ESR52 vs "
o be a *serious* issue of functionality. JRS
On 04/20/2018 08:00, enterprise-requ...@mozilla.org wrote:
Message: 1
Date: Thu, 19 Apr 2018 20:16:52 +
From: Jason Jackson
To: Perry Wagle , "Enterprise@mozilla.org"
Subject: Re: [Mozilla Enterprise] ESR52 vs "modern" java
ozilla.org] On Behalf Of
>> Perry Wagle
>> Sent: April 18, 2018 12:49 PM
>> To: Enterprise@mozilla.org
>> Subject: [Mozilla Enterprise] ESR52 vs "modern" javascript
>>
>> ESR52 produces blank pages when more and more sites apparently try to
>>
ackson
Computer Systems Technician
North Vancouver School District
> -Original Message-
> From: Enterprise [mailto:enterprise-boun...@mozilla.org] On Behalf Of
> Perry Wagle
> Sent: April 18, 2018 12:49 PM
> To: Enterprise@mozilla.org
> Subject: [Mozilla Enterprise] ESR52
ESR52 produces blank pages when more and more sites apparently try to render
things with what must be “modern” javascript.
Is there any hope of a workaround? My legacy extension that I critically
require runs only on ESR52, and porting it is still quite a trick.
Thanks!
— Perry
_
7 matches
Mail list logo
