edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] tag attributes in edbrowse DOM
Date: Thu, 24 Jul 2014 14:55:48 +0100	[thread overview]
Message-ID: <20140724135548.GE18899@toaster.adamthompson.me.uk> (raw)

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

Hi all,

Whilst browsing various documentation stored in Atlassian's Confluence wiki
system [1], I noticed that most of the code examples weren't showing up.
Closer investigation shows they use something which looks like a version of the Syntax Highlighter script
[2] when generating code examples.

This script uses the <script> tag in a strange way,
essentially to store code without html escaping it.
I think it then accesses the DOM to look for the special "syntaxhighlighter"
type attribute of script tags then renders this content.
It also requires a special brush attribute for these tags.
Obviously, since we don't currently support the type attribute for script tags
(that I can see) and certainly don't support arbitrary attributes,
this doesn't work.

I was wondering how difficult it would be to load all attributes for tags into
the DOM, not just the ones which have direct effect on the browser.
I've no idea if this would fix the non-functioning syntax highlighter script (I
suspect probably not), but it would give us a more standard DOM representation.

Cheers,
Adam.
[1] https://www.atlassian.com/software/confluence
[2] http://alexgorbatchev.com/SyntaxHighlighter/

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

             reply	other threads:[~2014-07-24 13:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 13:55 Adam Thompson [this message]
2014-07-30 14:33 ` Chris Brannon
2014-07-24 15:43 Karl Dahlke
2014-07-24 20:29 ` Adam Thompson
2014-07-31  7:27 Karl Dahlke
2014-07-31 11:19 ` Adam Thompson

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=20140724135548.GE18899@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.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).