From: Karl Kleinpaste <karl@justresearch.com>
Subject: text/html clickable links fail in p0.63+w3-4.0pre31
Date: 04 Dec 1998 13:14:38 -0500 [thread overview]
Message-ID: <vxkvhjrbwq9.fsf@beaver.jprc.com> (raw)
A forwarded text/html article in a local newsgroup contains numerous
<a href>'s. Merely passing the mouse over these links induces this
stack trace:
Signaling: (args-out-of-range #<buffer "*Summary jprc.support.linux*"> #<marker at 1068 in *Article* 0x8947334> #<marker at 1080 in *Article* 0x88e6ec4>)
buffer-substring-no-properties(#<marker at 1068 in *Article* 0x8947334> #<marker at 1080 in *Article* 0x88e6ec4>)
w3-widget-echo((link :button-extent #<extent (1068, 1080) H keymap help-echo balloon-help button-or-field button 0x8fc3814 in buffer *Article*> :to #<marker at 1080 in *Article* 0x88e6ec4> :class (":link") :href "http://www.excite.com/" :emacspeak-help w3-widget-echo :help-echo w3-widget-echo :from #<marker at 1068 in *Article* 0x8947334> :visited-face #<face w3-style-face-00021 "An Emacs-W3 face... don't edit by hand."> :active-face #<face w3-style-face-00020 "An Emacs-W3 face... don't edit by hand."> :button-face (nil) :action w3-follow-hyperlink :tag "" :value "" :args nil :end 1083 :start 1071 :delete widget-leave-text))
widget-echo-this-extent(#<extent (1068, 1080) H keymap help-echo balloon-help button-or-field button 0x8fc3814 in buffer *Article*>)
default-mouse-motion-handler(#<motion-event 847, 533>)
(I'm experimenting with XEmacs 21.2-b4, so if that's part of the
problem, I suppose this should be ignored...)
next reply other threads:[~1998-12-04 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-04 18:14 Karl Kleinpaste [this message]
1998-12-05 16:06 ` Lars Magne Ingebrigtsen
1998-12-12 19:50 ` William M. Perry
1998-12-28 21:43 ` William M. Perry
1999-01-03 12:51 ` Lars Magne Ingebrigtsen
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=vxkvhjrbwq9.fsf@beaver.jprc.com \
--to=karl@justresearch.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).