edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] data-* attributes / new work on RC
Date: Sun, 26 Nov 2017 17:43:41 -0500	[thread overview]
Message-ID: <20171026174341.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1711241728020.5490@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 795 bytes --]

I'm still in a bit of a quandary regarding an onclick function that doesn't complete because of an edbrowse error or shortcoming.
99% of the time you still want to go to the link, if you're a casual user, though there may be that 1% wherein you should have stopped.

1. return true and folllow the link. Developers like me can always set db3 and I'll see the error along the way.

2. Return false and don't follow the link. This would frustrate users as various links just wouldn't work, they would just sit there silently.

3. Some kind of debug toggle flag to do one or the other.

4. Return true and proceed unless debug is 3 or higher, whence we return false and stop, because after all we're trying to debug.
I kind of lean towards this one.

What do you think?

Karl Dahlke

  parent reply	other threads:[~2017-11-26 22:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 12:29 [Edbrowse-dev] Tidy error reporting Karl Dahlke
2017-11-22  8:43 ` [Edbrowse-dev] data-* attributes Kevin Carhart
2017-11-22  9:33   ` Kevin Carhart
2017-11-22 15:48   ` Karl Dahlke
2017-11-22 21:36     ` Kevin Carhart
2017-11-23  1:23       ` Kevin Carhart
2017-11-24 21:19   ` Karl Dahlke
2017-11-25  0:20     ` [Edbrowse-dev] data-* attributes / new work on RC Kevin Carhart
2017-11-25  0:56       ` Karl Dahlke
2017-11-25  1:15         ` Kevin Carhart
2017-11-25  1:22           ` Karl Dahlke
2017-11-25  1:44             ` Kevin Carhart
2017-11-25  2:28               ` Karl Dahlke
2017-11-25  3:10                 ` Kevin Carhart
2017-11-25  5:02                   ` Karl Dahlke
2017-11-25  5:35                     ` Kevin Carhart
2017-11-26 13:14               ` Karl Dahlke
2017-11-27  1:03                 ` Kevin Carhart
2017-11-27  1:48                 ` Kevin Carhart
2017-11-27  2:58                   ` Karl Dahlke
2017-11-27  3:37                     ` Kevin Carhart
2017-11-26 22:43               ` Karl Dahlke [this message]
2017-11-27  3:19                 ` Kevin Carhart
2017-11-27  4:23                   ` Karl Dahlke
2017-11-27  4:51                     ` 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=20171026174341.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --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).