edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Jean-Philippe MENGUAL <mengualjeanphi@free.fr>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] [Fwd: Bug#647226: edbrowse: button press does not work anymore on	a page using a lot of javascript]
Date: Tue, 01 Nov 2011 00:12:06 +0100	[thread overview]
Message-ID: <1320102726.22211.4.camel@maison> (raw)

Hi,

Debian is reported the following problem (see below). Could you tell me
how I've to consider it please? Should I report it somewhere (a
bugtracker)? Should I answer something to the user? Note that you can
answer to the bug yourself freely if you want, with a mail on:
647226@bugs.debian.org

In Debian, we haven't changed anything in edbrowse. I can give you any
additional info if needed (e.g. build options, etc.). Maybe I can ask
for some debug info (gdb, valgrind, etc.)? But I need your help as I
don't know to use this tools.

Thanks for your help,

Regards,


Jean-Philippe MENGUAL


-------- Message transféré --------
De: pro.privacy@nurfuerspam.de
Répondre à: pro.privacy@nurfuerspam.de, 647226@bugs.debian.org
À: Debian Bug Tracking System <submit@bugs.debian.org>
Sujet: Bug#647226: edbrowse: button press does not work anymore on a
page using a lot of javascript
Date: Mon, 31 Oct 2011 21:26:00 +0100

Package: edbrowse
Version: 3.4.7-1
Severity: normal


Hello,

Surfing http://www.bibnet.de with a text oriented browsers is very
difficult.  The site makes heavy use of javascript and frames. The example
further down fails with edbrowse_3.4.7-1 (unstable). When pressing button
'i1*' (<Weiter> = continue) or 'i2*' (<Abbrechen> = abort) nothing
happens. The same example succeeds with edbrowse_3.4.1-1+b1 (stable).


Example with edbrowse_3.4.7-1:

---snip---
$ edbrowse
Sorry, language de_de.u is not implemented
no ssl certificate file specified; secure connections cannot be verified
edbrowse ready
e http://www.bibnet.de/wwwopac/woload.asp?DB=ALL
no trailing newline
591
e http://www.bibnet.de/wwwopac/login.asp?TYPE=K
2964
b
533
/Abbrechen/
<Weiter>|<Abbrechen>
i1?
submit B1
i2?
button B2
i2*
---snip---


Thank you for this helpful tool,
bye,

Christian

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'oldstable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages edbrowse depends on:
ii  libc6                         2.13-21    Embedded GNU C Library: Shared lib
ii  libcurl3                      7.21.0-2   Multi-protocol file transfer libra
ii  libmozjs7d                    7.0.1-4    Mozilla SpiderMonkey JavaScript li
ii  libpcre3                      8.12-4     Perl 5 Compatible Regular Expressi
ii  libreadline6                  6.1-3      GNU readline and history libraries
ii  libssl1.0.0                   1.0.0e-2   SSL shared libraries

Versions of packages edbrowse recommends:
ii  poppler-utils [xpdf-utils]    0.12.4-1.2 PDF utilitites (based on libpopple

edbrowse suggests no packages.

-- no debconf information





                 reply	other threads:[~2011-10-31 23:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1320102726.22211.4.camel@maison \
    --to=mengualjeanphi@free.fr \
    --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).