edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] tag attributes in edbrowse DOM
Date: Thu, 31 Jul 2014 12:19:02 +0100	[thread overview]
Message-ID: <20140731111902.GB27064@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140631032718.eklhad@comcast.net>

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

On Thu, Jul 31, 2014 at 03:27:18AM -0400, Karl Dahlke wrote:
> > So they are overloading the <script> tag?
> 
> I think they have done so almost from the begining.

Yeah probably. The developper of the syntax highlighter software even says not
to use this method in environments (like blog posts which may be converted to rss etc)
where the script tags may be stripped out.
The reason they're doing it is due to the fact that whatever's in the script
tag doesn't require html escaping.

> > Is edbrowse also trying to execute things that it should not
> 
> I don't believe so.
> If the language attribute is given I require it to say javascript.
> 	<script language=javascript>
> If no language attribute is given I assume javascript,
> which is what the documentation says to do.
> It's possible that I should also be checking the type attribute.

Yes we should if it exists.
However, even though edbrowse is registering these tags as containing javascript, when using the syntax highlighter in this mode one uses a CDATA
section to surround the data, and thus I think edbrowse isn't parsing the contents of these tags.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-07-31 11:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31  7:27 Karl Dahlke
2014-07-31 11:19 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-24 15:43 Karl Dahlke
2014-07-24 20:29 ` Adam Thompson
2014-07-24 13:55 Adam Thompson
2014-07-30 14:33 ` 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=20140731111902.GB27064@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).