Re: No IMG in FIG

Ka-Ping Yee ([email protected])
Wed, 2 Aug 1995 19:27:02 -0400


Ping wrote:
> To me the argument to allow <IMG> within <FIG> is overwhelmingly strong.
> I had the impression that this functionality was exactly one of the reasons
> why <FIG> allowed content: to ensure some degree of renderability by older
> browsers.
>
> For the sake of simplicity, consistency, and usefulness, i further
> agree that <FIG> should have the same content model as <P>.

On Wed, 2 Aug 1995, Michael Johnson replied:
> No, the content model of <P> is too restrictive to be used as the content
> model of <FIG>. The respective content models are more useful as they are,
> and I personally don't see any problem with simplicity or consistency either.

Please point out how you mean that the content model of <P> is "too
restrictive" to be used for <FIG>. I am asking primarily that we
remove the restriction that prevents <IMG> (and <FIG>) tags from being
used within a <FIG>. Every added restriction makes HTML less simple.

> Don't take this personally, Ping, but it seems to me that you have been
> making a large number of poorly thought out proposals lately. You seem to
> have a less than perfect understanding of the mission of HTML or else you
> just aren't taking the time to really consider the consequences of some of
> what you propose.

I can certainly accept this, but a general opinion on the quality of my
suggestions doesn't help us to work towards the goal of a better markup
language. I'd appreciate much more an explicit description of how my
understanding is flawed, specifically what parts of which proposals you
feel to be poorly thought-out, and what ill consequences may arise.

Ping (Ka-Ping Yee): 2B Computer Engineering, University of Waterloo, Canada
[email protected] | 62A Churchill St, Waterloo, N2L 2X2, 519 886-3947
CWSF 89, 90, 92; LIYSF 90, 91; Shad Valley 92; DOE 93; IMO 91, 93; ACMICPC 94
||| Hiyama Hikaru || Hayakawa Moemi || Skuld || Tendou Akane || Belldandy |||
draft Video Girl Ai manga full-translations posted on [email protected]