OBJECT and IFRAME

MegaZone (megazone@livingston.com)
Mon, 22 Sep 1997 03:16:14 -0700 (PDT)


Message-Id: <199709221016.DAA23941@server.livingston.com>
To: www-html@w3.org
Date: Mon, 22 Sep 1997 03:16:14 -0700 (PDT)
From: MegaZone <megazone@livingston.com>
Subject: OBJECT and IFRAME

This is OBJECT:

<!ELEMENT OBJECT - - (PARAM | %inline; | %blocklevel;)* -- generic embedded object -->
<!ATTLIST OBJECT
  %attrs;                          -- %coreattrs, %i18n, %events --
  declare     (declare)  #IMPLIED  -- declare but don't instantiate flag --
  classid     %URL;      #IMPLIED  -- identifies an implementation --
  codebase    %URL;      #IMPLIED  -- some systems need an additional URL --
  data        %URL;      #IMPLIED  -- reference to object's data --
  type     %ContentType; #IMPLIED  -- Internet content type for data --
  codetype %ContentType; #IMPLIED  -- Internet content type for code --
  archive     %URL;      #IMPLIED  -- space separated archive list --
  standby     CDATA      #IMPLIED  -- message to show while loading --
  align       %IAlign;   #IMPLIED  -- vertical or horizontal alignment --
  height      %Length;   #IMPLIED  -- suggested height --
  width       %Length;   #IMPLIED  -- suggested width --
  border      %Length;   #IMPLIED  -- suggested link border width --
  hspace      %Length;   #IMPLIED  -- suggested horizontal gutter --
  vspace      %Length;   #IMPLIED  -- suggested vertical gutter --
  usemap      %URL;      #IMPLIED  -- reference to image map --
  shapes      (shapes)   #IMPLIED  -- object has shaped hypertext links --
  name        CDATA      #IMPLIED  -- submit as part of form --
  tabindex    NUMBER     #IMPLIED  -- position in tabbing order --
  %reserved;                       -- reserved for possible future use --
  >

This is IFRAME:
<!ELEMENT IFRAME - - (%block;)+ -- inline subwindow -->
<!ATTLIST IFRAME
  id          ID         #IMPLIED  -- document-wide unique id --
  title       CDATA      #IMPLIED  -- advisory title as for anchors --
  name        CDATA      #IMPLIED  -- name of frame for targetting --
  src         %URL;      #IMPLIED  -- source of frame content --
  frameborder (1|0)      1         -- request frame borders? --
  marginwidth %Pixels;   #IMPLIED  -- margin widths in pixels --
  marginheight %Pixels;  #IMPLIED  -- margin height in pixels --
  scrolling (yes|no|auto) auto     -- scrollbar or none --
  align       %IAlign;   #IMPLIED  -- vertical or horizontal alignment --
  height      %Length;   #IMPLIED  -- suggested height --
  width       %Length;   #IMPLIED  -- suggested width --
  >

IFRAME has 'src' and OBJECT has 'data' - equivalent.
IFRAME has 'frameborder' and OBJECT has 'border' - can server the same 
purpose - and is even more flexible.

That leaves:
  marginwidth %Pixels;   #IMPLIED  -- margin widths in pixels --
  marginheight %Pixels;  #IMPLIED  -- margin height in pixels --
  scrolling (yes|no|auto) auto     -- scrollbar or none --

hspace and vspace *might* suffice for marginheight and marginwidth.

That would leave only scrolling as missing.  Even if it does not, three
attributes is all.

Is there any *real* reason we can't deprecate IFRAME and give OBJECT all
of its abilities?  I mean *really*?  They are practically the same thing,
and it seems, from reading the spec, that the only difference is that
OBJECT doesn't have scrolling controls (which might be nice anyway) and
it can't be a target for content - and I don't see why not.

Wouldn't surprise me to find most of the code is reused to support both.

-MZ
--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588