From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] <object>
Date: Fri, 15 Jan 2016 18:06:37 -0500 [thread overview]
Message-ID: <20160015180637.eklhad@comcast.net> (raw)
Speaking of object tags, should I try to slide a minimal understanding
of object into 3.6.1?
Right now it completely disappears.
<body><object>hello world</object></body>
I would treat <object> just like <div>,
it looks like the tidy tree is doing same,
and then we would at least see what is inside.
That is the alternate text, and it's not ideal,
ideal would be parsing the attributes and launching plugins etc,
but as a quick and easy start it's better than nothing.
So you would at least see something like
Your browser does not have shockwave player installed,
click here to download the {swf file}.
So Chris should I slide this in or wait til after 3.6.1?
I don't have strong feelings either way,
but it would be nice if <object> was not completely lost,
as it is now.
Karl Dahlke
next reply other threads:[~2016-01-15 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 23:06 Karl Dahlke [this message]
2016-01-16 14:39 ` Adam Thompson
2016-01-17 7:00 ` Karl Dahlke
2016-01-17 7:17 ` 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=20160015180637.eklhad@comcast.net \
--to=eklhad@comcast.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).