From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] href=javascript:
Date: Sun, 28 Aug 2016 15:37:48 -0700 [thread overview]
Message-ID: <8760qk34g3.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160728171357.eklhad@comcast.net> (Karl Dahlke's message of "Sun, 28 Aug 2016 17:13:57 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> Yeah it's possible edbrowse isn't url decoding that string, %20 back to space,
> because of the javascript:
> Could be my bug.
This makes sense. The href is supposed to be a URL, so it seems
that we should always URL decode it. Thinking about it,
javascript:whatever() is still a URL, but the scheme happens to be
javascript, rather than http or whatever.
-- Chris
prev parent reply other threads:[~2016-08-28 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 19:47 Karl Dahlke
2016-08-28 20:20 ` Chris Brannon
2016-08-28 20:32 ` Karl Dahlke
2016-08-28 20:44 ` Tyler Spivey
2016-08-28 21:13 ` Karl Dahlke
2016-08-28 22:37 ` Chris Brannon [this message]
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=8760qk34g3.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--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).