Daniel Laforest
Top achievements
Rank 1
Rank 1
Daniel Laforest
asked on 23 Oct 2008, 02:37 PM
Hi,
I'm using a radWindow in my site and it seems it is in an IFrame (which I did not create). I assume it is the radWindow that is rendered that way. I wanna know if it is possible to open the radWindow in something else since IFrame is not complient to the W3C standard.
Thanks,
Phil
I'm using a radWindow in my site and it seems it is in an IFrame (which I did not create). I assume it is the radWindow that is rendered that way. I wanna know if it is possible to open the radWindow in something else since IFrame is not complient to the W3C standard.
Thanks,
Phil
2 Answers, 1 is accepted
0
Accepted
Hello Daniel,
Version 1.0 of the XHTML standard provided a number of ways to write html that reflected the previous versions of HTML, for example - HTML4.01 - Strict, Transitional, Frameset and Loose. Towards a more semantic and better organized a la XML language, in version 1.1 of the XHTML these subsets were removed, i.e. XHTML1.1 is only strict (and it misses the Frameset subset respectively), as will be HTML5 and XHTML2, which are currently in blueprint.
Having in mind all of the above, <iframe> is not a standards compliant element, but the logic, semantics and nature of a "window" requires an element that opens an external document in the same page, and at present, there is no other way to load a page within a page.
However, RadWindow is created entirely on the client, i.e. its html code is not generated on the server and does not exist physically in the "View Source" option, although it is in the DOM of the page. This ensures that a page that validates without RadWindow, will certainly validate with RadWindow as well, as the W3C checker parses the physical, server-generated code of the pages, not the one that is dynamically created with JavaScript.
Please, be sure that you can use RadWindow without any concerns about the standards compliance of the pages.
Best wishes,
Martin Ivanov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Version 1.0 of the XHTML standard provided a number of ways to write html that reflected the previous versions of HTML, for example - HTML4.01 - Strict, Transitional, Frameset and Loose. Towards a more semantic and better organized a la XML language, in version 1.1 of the XHTML these subsets were removed, i.e. XHTML1.1 is only strict (and it misses the Frameset subset respectively), as will be HTML5 and XHTML2, which are currently in blueprint.
Having in mind all of the above, <iframe> is not a standards compliant element, but the logic, semantics and nature of a "window" requires an element that opens an external document in the same page, and at present, there is no other way to load a page within a page.
However, RadWindow is created entirely on the client, i.e. its html code is not generated on the server and does not exist physically in the "View Source" option, although it is in the DOM of the page. This ensures that a page that validates without RadWindow, will certainly validate with RadWindow as well, as the W3C checker parses the physical, server-generated code of the pages, not the one that is dynamically created with JavaScript.
Please, be sure that you can use RadWindow without any concerns about the standards compliance of the pages.
Best wishes,
Martin Ivanov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Daniel Laforest
Top achievements
Rank 1
Rank 1
answered on 23 Oct 2008, 03:39 PM
Thank you!