By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,649 Members | 2,154 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,649 IT Pros & Developers. It's quick & easy.

Nesting object tags in ASP 3.0, ASP.NET & Internet Explorer

P: n/a
Hi,

I'm attempting to make use of nested object tags (in HTML) as per the
w3c standard here:

http://www.w3.org/TR/REC-html40/stru....html#h-13.3.1

This details the HTML 4.01 Specification with regard to object tags.
When I create a nested object in an ASP page, I get the following server
error:

Active Server Pages error 'ASP 0139'

Nested Object

/WebProject2/test.asp, line 5

An object tag cannot be placed inside another object tag.

If I create it in an html file, the outer object tag is rendered, as are
all of the child object tags too.

So...

ASP seems to totally disallow nested object tags.
Internet Explorer renders all of them regardless.
The w3c spec seems to say that each object tag will be rendered in turn
and once one is found which works, no more child object tags will be
rendered.

Guidence on whether or not this has been raised as an issue, or if it
even is would be greatly appreciated. This is hindering conversion of a
website at work to WAI compliance.

Thanks,

Ted Bradley

Nov 17 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi,

asp.xsd is the schema that ASP.NET use to vlidate HTML. check if that
schema enable nesting tags (you can always update the schema)

Natty Gur[MVP]
Phone Numbers:
Office: +972-(0)9-7740261
Fax: +972-(0)9-7740261
Mobile: +972-(0)58-888377
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 17 '05 #2

P: n/a
Hi,

Just checked through the asp.xsd in the Microsoft Visual Studio .NET and
can't find a reference to object.

(D:\Program Files\Microsoft Visual Studio .NET
2003\Common7\Packages\schemas\xml\asp.xsd)

Also worth noting that when I target the page for Internet Explorer 5.0,
Visual Studio does not complain, it's only IIS which produces the error.

Thanks,

Ted

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 17 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.