Intersoft Solutions - Community - WebCombo - Javascript errors on web grid with page embedded in iframe

Create New

New Discussion
New Question
New Product Feedback

Post Reply

Vincenzo AngeloniMember

Posted: February 20, 2013 11:23 AM

Hi,

I have an html pages configuration so that an outer page contains an inner page through an iframe, and the inner page contasin a WebGrid. If I open in the browser the inner page all works as expected, instead if I open the outer page a lot of javascript errors arise. To show you I created a simple project with 2 pages: Inner.aspx and Outer.aspx, if you browse the first all is ok, if you browse the second you will see the errors. You can find this project in attachment InnerFrame.zip.

While debugging the code I see that the following instructions are executed:

var v46839 =ISGetObject(v79345.childNodes[0].gridId);
var ve0e96 =v46839.Tables[v79345.childNodes[0].tblName];

but v79345.childNodes[0].gridId is undefined, so ISGetObject returns null and the next instruction arise the error.

Could you please help?

Regards,

Vince

1 attachment

InnerFrame.zip

Quick Reply

Quote

All Replies

Hans KristianMember

Posted: February 20, 2013 10:56 PM in response to Vincenzo Angeloni

Hello,

I am sorry for the inconvenience.

Thank you for the sample and I can reproduce your issue on my end as well.

First of all, if you want to use WebGrid in HTML5 doctype, you should set RenderingMode property to “HTML5”.

So all features should work exactly as in other doctype.

You can set the rendering mode in a WebGrid instance individually by setting the RenderingMode property to HTML5 value, such as shown in the example below:


<ISWebGrid:WebGrid ID="WebGrid1" runat="server" RenderingMode="HTML5">

</ISWebGrid:WebGrid>

Alternatively, you can also apply the rendering mode globally through the application-wide configuration, see the following example.

<add key="ISNet.WebUI.WebGrid.v8_0_7200.RenderingMode" value="HTML5"/>

Your issue appears due to, in Inner.aspx, you put a comment tag before doctype declaration. So put the comment tag to another place.

This is HTML5’s default behavior, if there is comment tag before doctype declaration, it will make HTML5 doctype doesn’t work properly.

In order to fix the issue, I make some changes in your Inner.aspx file.

First, I set the RenderingMode property to “HTML5”. Second, I put the comment tag after doctype declaration.

Please kindly have review on the modified sample and let me know whether the issue still persists or not.

Thank you.

Regards,

Hans.

1 attachment

Inner.zip

Quick Reply

Quote

Vincenzo AngeloniMember

Posted: February 21, 2013 10:12 AM in response to Hans Kristian

Hi Hans,

I know about the comment, I put the comment before doctype on purpose, the question is: why Inner.aspx works with the before doctype if browsed alone, but it does not work when embedded in Outer.aspx?

Moreover, I do not find differences using RenderingMode="HTML5, anyway I will put it.

Thanks in advance,

Vince

Quick Reply

Quote

Hans KristianMember

Posted: February 21, 2013 10:14 PM in response to Vincenzo Angeloni

Hello,

Like I said before you shouldn’t put the comment tag before doctype tag.

It will interfere with the system of HTML5, so it makes all version of IE set the Document Mode to “Quirks” Mode, not in “IE9 Standards” Mode.This is default behaviour of HTML5 doctype
If this happens, it will interfere with the system of WebGrid as well.

You can run the Inner.aspx page indeed. However, in page doesn’t run in HTML5 mode (QuirksMode.jpg).

To fix this issue, you should put the comment tag after doctype tag. Alternatively, you should modify the content of your comment into:

<!--[if anybrowser]> do not remove <![endif]-->
<!DOCTYPE html>

The Inner.aspx page will run in HTML5 mode, after I modify the comment (IE9Standart.jpg).

There is also thread in another website that discuss about this Comment tag issue. You could find it by following this link .

Hope this helps.

Regards,
Hans.

2 attachments

Vincenzo AngeloniMember

Posted: February 28, 2013 5:50 AM in response to Hans Kristian

Hi Hans

I made a deeper investigation of the problem I have in the productive environment. In attachment InnerFrame.zip you can find the example that reproduce the problem, I added the doctype <!DOCTYPE html> to InnerFrame.aspx without any comment before. Now the problem I have is that this page is shown in Outlook, and Outlook it works like IE7, so to simulate this behaviour it needs to set the browser mode to "IE7" and the document mode to "IE9 standards" like shown in attachment image1.png.

In this situation at first I have the error reported in the first message of this thread:

While debugging the code I see that the following instructions are executed:
var v46839 =ISGetObject(v79345.childNodes[0].gridId);
var ve0e96 =v46839.Tables[v79345.childNodes[0].tblName]
but v79345.childNodes[0].gridId is undefined, so ISGetObject returns null and the next instruction arise the error.

I made some search in WebGrid javascript code (based on version 8.0.7200.250) and I found that the function named wg82a90.m18140 is executed only if "IS.w3cs || IS.ie9s || !IS.ie": here the code:

m60528:function(v94961) {
  if (IS.w3cs ||IS.ie9s ||!IS.ie) wg82a90.m18140(v94961);
}

To make a test I changed it the function in this way (you can find that in the file WebGrid_Core.fix.js in the zip file):

wg82a90.m60528 = function (table) {
    if (IS.w3cs || IS.ie9s || !IS.ie || (IS.ie && IS.IsHTML5DocType())) {
        wg82a90.m18140(table);
    }
};

and this make the error disappear, but there are still layout problems with the height of the grid and with the header and footer width.

Please tell me what do you think about that and if you can help me to overcome this situation.

Regards,

Vince

2 attachments

Hans KristianMember

Posted: February 28, 2013 11:17 PM in response to Vincenzo Angeloni

Hello,

Thank you for your valuable feedback.

I try to set the browser mode to "IE7" and the document mode to "IE9 standards" and the result is I can replicate your issue on my end as well.
This issue occurs due to Internet Explorer 7 doesn’t support HTML5 doctype indeed.
You shouldn’t use HTML5 doctype in Internet Explorer 7.
The layout problem occurs due to we can’t use HTML5 doctype in Internet Explorer 7 as well.

Regards,

Hans.

Quick Reply

Quote

Vincenzo AngeloniMember

Posted: March 6, 2013 3:29 AM in response to Hans Kristian

Hi Hans,

Microsoft Dynamics CRM is a web based product from Microsoft, html pages of this product have html5 doctype and it is desinged to work inside Outlook so it works correclty with Outlook and IE7. Maybe IE7 does not recognize the new html5 tags, but for sure is able to render html5 pages with the right layout if the pages are correclty generated. In my opinion, as I show you with the fix proposed in the previous comment, the grid operations and the grid layout is not correclty handled by Intersoft in case of html5 doctype and userAgent MSIE 7.0.

Regards,

Vince

Quick Reply

Quote

Hans KristianMember

Posted: March 6, 2013 9:32 PM in response to Vincenzo Angeloni

Hello,

I am not sure if we can just enhance the HTML5 in IE7. Some processes and renders might be depending on the browser itself that support HTML5. This became issue because IE7 itself does not support it.
Even though the CRM is used by Microsoft, we could not follow it. It is not well standard. The correct standard is following the W3School standard. I would like need to discuss with our developer to see the possibility first.

Regards,
Hans.

Quick Reply

Quote

Services

Support

Community / WebCombo

Javascript errors on web grid with page embedded in iframe

Answers

All Replies

Business Platform

Development Tools

Community / WebCombo

Javascript errors on web grid with page embedded in iframe

Answers

All Replies

Sign in to Intersoft Account

Sign in to Intersoft Account

Link Existing Account

Create New Account

Link Existing Account

Sign in to Intersoft Account

Sign in to Intersoft Account

Create New Intersoft Account

Forgot Password

Your new password has been sent to your email.