From: Sebastian Humenda <shumenda@gmx.de>
To: edbrowse-dev <edbrowse-dev@lists.the-brannons.com>
Subject: [Edbrowse-dev] JS interpreter crashes on Google books
Date: Thu, 21 Jan 2016 13:49:08 +0100 [thread overview]
Message-ID: <20160121124908.GC1722@Kraftkrust> (raw)
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
Hi there,
presumably that has been reported before / is known already, but I have a
reproducible crash at the Google Docs site:
https://docs.google.com/document/d/1jTnjQ6WRFyUE7iKgkMiJMxDmJ-UDzgtpT40i-xm-JoQ/edit?pref=2&pli=1
It seems that Edbrowse is asking for something, it prints [y|n], but no matter
what I type, it repeats the same message over and over again. C-c will make the
js interpreter crash.
Cheers
Sebastian
--
Web: http://www.crustulus.de (English|Deutsch) | Blog: http://www.crustulus.de/blog
FreeDict: Free multilingual dictionaries - http://www.freedict.org
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-01-21 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 12:49 Sebastian Humenda [this message]
2016-01-22 8:14 ` Karl Dahlke
2016-01-22 12:41 ` Karl Dahlke
2016-01-22 13:05 ` Sebastian Humenda
2016-01-23 1:41 ` Kevin Carhart
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=20160121124908.GC1722@Kraftkrust \
--to=shumenda@gmx.de \
--cc=edbrowse-dev@lists.the-brannons.com \
/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).