RE: The MQ (or not) issue; what we are seeking

When it is suggested that there are ebook readers that don't support JavaScript, what is meant is that they don't support JS embedded in the ebook content itself. Am I correct? AFAIK, virtually all ebook readers are browser engine-based and use JS code in their implementation. They just don't want content to contain JS as it is a potential security risk. I only point this out in case it makes a difference in this MQ discussion.

Paul

> -----Original Message-----
> From: George Kerscher [mailto:kerscher@montana.com]
> Sent: Wednesday, October 05, 2016 6:44 PM
> To: 'Liam R. E. Quin' <liam@w3.org>; 'Bill Kasdorf'
> <bkasdorf@apexcovantage.com>; 'Alan Stearns' <stearns@adobe.com>;
> 'Siegman, Tzviya - Hoboken' <tsiegman@wiley.com>; Peter Krautzberger
> <peter.krautzberger@mathjax.org>; public-digipub-ig@w3.org
> Subject: RE: The MQ (or not) issue; what we are seeking
> 
> You ask: "Does this have to work in ebook readers (which might or might not
> support JavaScript) as well as in Web browsers?"
> 
> George responds: Yes, the publishers want to distribute their content into all
> markets. The visual presentation is essential, and people using access
> technology need to get at the semantically rich information.
> 
> Best
> George
> 
> 
> 
> -----Original Message-----
> From: Liam R. E. Quin [mailto:liam@w3.org]
> Sent: Wednesday, October 05, 2016 5:52 PM
> To: Bill Kasdorf; Alan Stearns; Siegman, Tzviya - Hoboken; Peter Krautzberger;
> public-digipub-ig@w3.org
> Subject: Re: The MQ (or not) issue; what we are seeking
> 
> On Wed, 2016-10-05 at 15:17 +0000, Bill Kasdorf wrote:
> > What we need is an interim solution that will make it safe for
> > publishers to deliver the MathML along with the image that they want
> > displayed visually. For now.
> support JavaScript) as well as in Web browsers?
> 
> Liam
> 
> >
> 
> 
>

Received on Thursday, 6 October 2016 05:08:46 UTC