On 4/12/07, Henri Sivonen <[EMAIL PROTECTED]> wrote:
On Apr 12, 2007, at 01:45, Michael A. Puls II wrote:
> On 4/11/07, Henri Sivonen <[EMAIL PROTECTED]> wrote:
>> I was thinking of
>> establishing an attribute such as "script-private" where authors
>> would be free to stick anything for retrieval by scripts.
>
> What would happen with <embed script-private="something">? Would the
> data be passed to the plug-in as a script-private param or would
> script-private be reserved; causing any plug-in using script-param not
> to get the data? (A prefix could possible avoid this.)
In old browsers at least, the script-private="something" would be
passed to the plug-in. Is it a problem?
Potentially. If the plug-in requires a script-private param for
something, that'd mean you might not be able to use script-private on
the embed element for what you want. In that case, you would use a
different attribute name that doesn't conflict, which is O.K. because
you can use use some odd attribute on embed and still validate.
It's not a big concern, but IF there's a way to avoid that potential
conflict, it'd be cool.
--
Michael
