From: Kevin Carhart <email@example.com>
Subject: Re: [Edbrowse-dev] version
Date: Sun, 18 Feb 2018 00:30:10 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.firstname.lastname@example.org> (raw)
> I don't know, it may be more complicated than that.
> These are usually more than just browse.
True. It does not solve the complex scenarios where you want to use a
website to do things, but I think it could be "necessary but not
sufficient" some of the time, since a JS crash can inhibit dynamic
behavior from working right. Doing real ecommerce, or online banking, a
lot of the time is going to be related to document.forms, submitting and
maintaining state, right? I've tried some of this. It works some of the
time and doesn't work some of the time. And, although this could have
many causes, I think one major problem is when a submission button isn't
recognized, so you can't i*.
Anyway, I wanted to scratch an itch.. an interesting couple hours'
research. It is definitely not the whole story when we want to use the
applications on sites and use them for what they're for.
next prev parent reply other threads:[~2018-02-18 8:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 11:56 Karl Dahlke
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04 ` Karl Dahlke
2018-02-16 19:11 ` Adam Thompson
2018-02-18 2:19 ` Karl Dahlke
2018-02-18 2:42 ` Kevin Carhart
2018-02-18 3:03 ` Karl Dahlke
2018-02-18 3:39 ` Kevin Carhart
2018-02-18 7:43 ` Karl Dahlke
2018-02-18 8:17 ` Dominique Martinet
2018-02-18 8:47 ` Dominique Martinet
2018-02-18 8:30 ` Kevin Carhart [this message]
2018-02-18 7:45 ` Kevin Carhart
2018-02-18 8:55 ` Karl Dahlke
2018-02-18 11:29 ` Karl Dahlke
2018-02-18 14:08 ` Karl Dahlke
2018-02-19 1:07 ` [Edbrowse-dev] version / dyndns Kevin Carhart
2018-02-19 3:58 ` [Edbrowse-dev] update on dyndns Kevin Carhart
2018-03-24 16:07 [Edbrowse-dev] version Karl Dahlke
2018-03-25 8:11 ` Kevin Carhart
2018-06-11 15:45 [edbrowse-dev] version Karl Dahlke
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).