* [Edbrowse-dev] href=javascript:
@ 2016-08-28 19:47 Karl Dahlke
2016-08-28 20:20 ` Chris Brannon
0 siblings, 1 reply; 6+ messages in thread
From: Karl Dahlke @ 2016-08-28 19:47 UTC (permalink / raw)
To: Edbrowse-dev
Didn't this use to work? Shouldn't it work?
Looks like tidy is mucking with the url.
<body>
<A href='javascript: alert("hello world")'>push</A>
</body>
Karl Dahlke
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [Edbrowse-dev] href=javascript:
2016-08-28 19:47 [Edbrowse-dev] href=javascript: Karl Dahlke
@ 2016-08-28 20:20 ` Chris Brannon
2016-08-28 20:32 ` Karl Dahlke
0 siblings, 1 reply; 6+ messages in thread
From: Chris Brannon @ 2016-08-28 20:20 UTC (permalink / raw)
To: Edbrowse-dev
Karl Dahlke <eklhad@comcast.net> writes:
> Didn't this use to work? Shouldn't it work?
> Looks like tidy is mucking with the url.
Yes, it's turning
<A href='javascript: alert("hello world");'>push</A>
into
<a href='javascript:%20alert("hello%20world");'>push</a>
I'd think it should just leave it alone.
-- Chris
^ permalink raw reply [flat|nested] 6+ messages in thread* [Edbrowse-dev] href=javascript:
2016-08-28 20:20 ` Chris Brannon
@ 2016-08-28 20:32 ` Karl Dahlke
2016-08-28 20:44 ` Tyler Spivey
0 siblings, 1 reply; 6+ messages in thread
From: Karl Dahlke @ 2016-08-28 20:32 UTC (permalink / raw)
To: Edbrowse-dev
> 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Edbrowse-dev] href=javascript:
2016-08-28 20:32 ` Karl Dahlke
@ 2016-08-28 20:44 ` Tyler Spivey
2016-08-28 21:13 ` Karl Dahlke
0 siblings, 1 reply; 6+ messages in thread
From: Tyler Spivey @ 2016-08-28 20:44 UTC (permalink / raw)
To: Edbrowse-dev
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
>
^ permalink raw reply [flat|nested] 6+ messages in thread* [Edbrowse-dev] href=javascript:
2016-08-28 20:44 ` Tyler Spivey
@ 2016-08-28 21:13 ` Karl Dahlke
2016-08-28 22:37 ` Chris Brannon
0 siblings, 1 reply; 6+ messages in thread
From: Karl Dahlke @ 2016-08-28 21:13 UTC (permalink / raw)
To: Edbrowse-dev
Yeah it's possible edbrowse isn't url decoding that string, %20 back to space,
because of the javascript:
Could be my bug.
Karl Dahlke
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Edbrowse-dev] href=javascript:
2016-08-28 21:13 ` Karl Dahlke
@ 2016-08-28 22:37 ` Chris Brannon
0 siblings, 0 replies; 6+ messages in thread
From: Chris Brannon @ 2016-08-28 22:37 UTC (permalink / raw)
To: Edbrowse-dev
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-08-28 22:37 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-28 19:47 [Edbrowse-dev] href=javascript: 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 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).