[FIXED] [#299] [#300] More Layout run failed messages when I run my website in IE7 or IE8 modes.

[michaeld]

These errors do not appear in IE9 or IE10 but seems to only affect rendering of an ImageButton that appears with a linkbutton within a FieldContainer with HBoxLayout. This does not mean necessarily that the issue has anything to do with any of the controls I've referenced.

[Daniil]

Hi @michaeld,

Could you, please, provide us with a test case?

[michaeld]

Attachment as before...

The visual issue is FBLog Imagebutton

IE8 and lower does not display and produces the layout render error whereas IE9 and above does not.

[Daniil]

Ok, thanks. I will investigate.

For the future, it would be nice if you could simplify it. I understand it is going to be a problematic to simplify the Ext.NET part (though, it is also possible), but we would appreciate if you could remove, at least, irrelevant to Ext.NET or ExtJS things like:

<script type="text/javascript"><!--
    var _gaq = _gaq || [];
    _gaq.push(['_setAccount', 'UA-25254525-1']);
    _gaq.push(['_trackPageview']);
    (function () {
        var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
        ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
        var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
    })();//-->
</script>

<script type="text/javascript" src="//pagead2.googlesyndication.com/pagead/show_ads.js"></script>

Hmm, wait a bit, I see that the Ext.onReady script is not so big as it was in the previous pages. You probably simplified it a lot. Nice.

Are you not able to post a standalone ASPX page to reproduce? Well, it is not so comfortable for us to deal with the raw page sources. It takes some time to get it runnable. Commonly, we very seldom request the page sources and, commonly, in quite exceptional occasions. Thank you for understanding.

[michaeld]

Hmm, wait a bit, I see that the Ext.onReady script is not so big as it was in the previous pages. You probably simplified it a lot. Nice.

The root page is significantly less complicated than the ones I sent you before that were having a different render problem, especially without content. I've also gone through and removed a lot of panels substituting containers where possible so that may help as well.

Well, it is not so comfortable for us to deal with the raw page sources. It takes some time to get it runnable. Commonly, we very seldom request the page sources and, commonly, in quite exceptional occasions. Thank you for understanding.

It's the raw page source I delivered in the past that I thought you were able to discover the layout render issues in the past with page-analyzer. If you think the issue can be detected in page-analyzer, feel free to try directly at the root domain of the website I posted to your email. We're still not live so I can't post that link on a public google indexed page, as yet.

Are you not able to post a standalone ASPX page to reproduce?

Ok, thanks. I will investigate.

I'll try if you still cannot after investigation.

Thanks.

[michaeld]

I'm wondering if this is a clue related to the issue. Can you tell me what this message means?

[W] targetCls is missing. This may mean that getTargetEl() is being overridden but not applyTargetCls(). fieldcontainer-1010

[Daniil]