ScriptManager with history support enabled emits an IFRAME which fails XHTML Strict validation - by steveberkovitz

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 371804 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/1/2008 3:38:22 PM
Access Restriction Public

Description

When history support is enabled on the ScriptManager an IFRAME is emitted, however IFRAMES are not valid when an in XHTML 1.0 Strict DOCTYPE is used.

The workaround is to use the XHTML 1.0 Transitional DOCTYPE instead.

Sign in to post a comment.
Posted by Microsoft on 11/12/2008 at 12:34 PM
XHTML strict is not supported by ASP.NET. Only transitional doctypes are supported, which enables iframes. Furthermore, the history feature can't be made compatible with IE 6 and 7 without using an iframe.
Posted by steveberkovitz on 10/13/2008 at 7:35 PM
Find attached.
Posted by Microsoft on 10/13/2008 at 7:12 PM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 10/2/2008 at 2:28 AM

Thanks for reporting the issue.

In order to fix the issue, we must first reproduce the issue in our labs. We would be appreciated that if you provide us with:

a) A demo zipped project file
b) A screenshot of this issue.

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Visual Studio Product Team