Re: [whatwg] Object data Attribute

2006-11-16 Thread Shadow2531

On 11/7/06, Shadow2531 <[EMAIL PROTECTED]> wrote:

On 11/6/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote:
> Hi,
>Should the data attribute be required for ?

No.

Reason 1:
 is used for Java. (
Although I'd love to have  work, but ...)

Reason 2:
You might want to load a plugin like this:  and later use scripting to
tell the plugin to get the resource. If the data attribute is
required, you'd be forced to load a resource that you didn't want to.

Reason 3:
The tcl plugin  suports inline
scripts via a script param and things like the following need to work
with the data attribute.






Note that the embed element should not require the src attribute for
the same reasons.

For example, this needs to be be allowed:



--
burnout426


Re: [whatwg] Object data Attribute

2006-11-07 Thread Shadow2531

On 11/6/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote:

Hi,
   Should the data attribute be required for ?  There is at


No.

Reason 1:
 is used for Java. (
Although I'd love to have  work, but ...)

Reason 2:
You might want to load a plugin like this:  and later use scripting to
tell the plugin to get the resource. If the data attribute is
required, you'd be forced to load a resource that you didn't want to.

Reason 3:
The tcl plugin  suports inline
scripts via a script param and things like the following need to work
with the data attribute.


  


--
burnout426


Re: [whatwg] Object data Attribute

2006-11-07 Thread Shadow2531

Me:

Reason 3:
The tcl plugin  suports inline
scripts via a script param and things like the following need to work
with the data attribute.


Sorry. Correction.  That's WITHOUT the data attribute.

--
burnout426


[whatwg] Object data Attribute

2006-11-06 Thread Lachlan Hunt

Hi,
  Should the data attribute be required for ?  There is at 
least one plugin that doesn't need it.  XStandard embeds itself without 
using it, like this:


height="400">

  


I'm not sure whether that's a correct use of the object element or not, 
and I do think it would make more sense for XStandard to replace a 
textarea, but there must be implementation issues with that or something.


http://xstandard.com/page.asp?p=A4372B00-8D7F-4166-977C-64E5C4E3708E&ss=C2B75B64-1544-429D-ACDA-07D17E35FB56

--
Lachlan Hunt
http://lachy.id.au/