[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lynx-dev] title attribute, audio/video tags

From: Thorsten Glaser
Subject: [Lynx-dev] title attribute, audio/video tags
Date: Wed, 26 Jan 2011 17:12:41 +0100 (CET)
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)


I’ve been wondering to make the attached example file more useful.

I think the first paragraph should be rendered like this:

    Foo Baz [bar] Blubb.

Where "[bar]" is in the same colour as the img alt attribute
from the line below (i.e. yellow=brightbrown, not-bold).

The audio/video things should be converted into links, maybe
like this:

    [AUDIO] Your browser does not support the audio element.

Internal representation:

<p>[<a href="horse.ogg">AUDIO</a>] Your browser does not
support the audio element.</p>

Same for the video. As for the middle example:

<p>[AUDIO] [<a href="song.ogg">SOURCE</a>] [<a
href="song.mp3">SOURCE</a>] Your browser does not support
the audio element with sources.</p>

The last paragraph is easy from the first:


    Baz [bar]


Now my questions:

How is the title attribute currently handled, I see that
it’s parsed and copied into a struct member?

How would I best go about these tags? I think the easiest
is to do a transformation before Lynx actually displays
them, as shown above (ignoring all other attributes), but
is that possible / the sensible thing to do? (I’d imagine
the source view wouldn’t like that much.) Where would I go
hook my patch?

I think I can actually do part of this as part of my dayjob
(work on FusionForge; we add some title="…" there recently)
so chances are I can present a patch someday.

15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]