From: Marcin Borkowski <mbork@mbork.pl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: PDF viewer poll
Date: Tue, 15 Oct 2019 08:17:06 +0200 [thread overview]
Message-ID: <87eezettwd.fsf@mbork.pl> (raw)
In-Reply-To: <397B5450-539A-4E64-A251-190E5AA96CB4@fiee.net>
On 2019-10-15, at 06:42, Henning Hraban Ramm <texml@fiee.net> wrote:
>> Basically javascript can be limited to (1) setting annotation properties, like toggling layers or button renditions, and (2) some simple calculations (for forms). Constructing pdf runtime using javascript is pretty braindead (use html instead then).
>
> D’accord.
Of course you are aware that limiting a powerful language is not an easy
task?
>> It is one of the puzzling areas to me: no problem in browsers and elsewhere but not in open source pdf viewers. It's not the most complex stuff so it probably indicates that no one cares much about these features.
>
> I wouldn’t say "no problem", because JS causes security problems everywhere.
It's not JS that causes problems. Any other (powerful enough) language
not specifically designed with browser environment in mind could be
problematic here. I guess that having Perl, Python or Ruby instead of
JS would create a similar set of problems. (Lua might be an exception
due to its design and a possibility to whitelist functions for eval,
AFAIR.)
Just 2 cents from a JS programmer who actually thinks that JS is not the
worst Lisp dialect out there.
Best,
--
Marcin Borkowski
http://mbork.pl
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-10-15 6:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 10:43 Henning Hraban Ramm
2019-10-13 10:47 ` denis.maier
2019-10-13 14:50 ` Rudolf Bahr
2019-10-13 15:26 ` Henning Hraban Ramm
2019-10-13 15:50 ` Pablo Rodriguez
2019-10-14 17:09 ` Greedwolf DSS
2019-10-13 16:49 ` Pablo Rodriguez
2019-10-13 18:02 ` kaddour kardio
2019-10-13 18:28 ` Hans Åberg
2019-10-14 7:58 ` Taco Hoekwater
2019-10-14 9:17 ` Hans Hagen
2019-10-15 4:42 ` Henning Hraban Ramm
2019-10-15 6:17 ` Marcin Borkowski [this message]
2019-10-19 10:21 ` Henning Hraban Ramm
2019-10-19 10:51 ` Hans Hagen
2019-10-19 11:06 ` Henning Hraban Ramm
2019-10-20 20:15 ` Marcin Borkowski
2019-10-21 8:21 ` Hans Hagen
2019-10-15 8:11 ` Hans Hagen
2019-10-15 8:12 ` Taco Hoekwater
2019-10-15 8:21 ` Hans Hagen
2019-10-15 8:25 ` luigi scarso
2019-10-16 8:02 ` luigi scarso
2019-10-14 16:55 ` Marcin Borkowski
2019-10-15 15:40 ` Benct Philip Jonsson
2019-10-15 4:26 ` Alan Braslau
2019-10-15 4:58 ` Hamid,Idris
2019-10-19 19:27 ` Henning Hraban Ramm
2019-10-15 5:00 ` Otared Kavian
2019-10-15 11:58 ` luigi scarso
2019-10-16 9:30 ` context
2019-10-13 18:21 Damien Thiriet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eezettwd.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).