From: Tyler Spivey <tspivey@pcdesk.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] href=javascript:
Date: Sun, 28 Aug 2016 13:44:58 -0700 [thread overview]
Message-ID: <38fb756a-5c2e-4cfa-a040-9b36979e113b@pcdesk.net> (raw)
In-Reply-To: <20160728163235.eklhad@comcast.net>
Oh, reply doesn't go to the list.
That's a perfectly valid URL.
<a href="javascript:alert('test%20test')">link</a>
works fine in firefox. I guess it gets decoded along the way.
On 8/28/2016 1:32 PM, Karl Dahlke wrote:
>> I'd think it should just leave it alone.
>
> It should. javascript: is the key.
> Perhaps other protocols should be left alone as well.
> Can you report this as a bug?
> Thing is I think it use to work. Oh well.
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
next prev parent reply other threads:[~2016-08-28 20:44 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 [this message]
2016-08-28 21:13 ` Karl Dahlke
2016-08-28 22:37 ` Chris Brannon
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=38fb756a-5c2e-4cfa-a040-9b36979e113b@pcdesk.net \
--to=tspivey@pcdesk.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).