PDA

View Full Version : [CLOSED] TextField is not found in IE9.



kyleSencha
21 Feb 2012, 5:02 PM
I used TextField in FormPanel as items in a page, then I put the page in a tabpanel as a tab page.

I open this tab page(called page1), then I open another tab page. I click the tab of page1 to active it, then the TextField in page1 cann't be found.

I used this tag '<meta http-equiv="X-UA-Compatible" content="IE=8" />' in my main page, and the problem was found in IE9.

WesleyMoy
21 Feb 2012, 5:25 PM
Have you tried running your app without the X-UA-Compatible header?

Because GWT compiles a different permutation for each browser, it shouldn't be necessary or desirable to run IE9 in IE8 mode. Is there any particular reason why you would need this?

kyleSencha
22 Feb 2012, 5:43 PM
Yes, I have try it. When I remove the X-UA-Compatible header, IE8 and IE9 will run the page in IE7 mode. But our portal do not perfect support for IE7.

WesleyMoy
23 Feb 2012, 3:16 PM
Usually, a document with a valid DOCTYPE declaration and no X-UA-Compatible header will be rendered using the most up-to-date renderer available. Because both GWT and Ext GWT layouts depend on your document being in standards mode, you should already have a valid DOCTYPE for your host page. See http://blogs.msdn.com/b/ie/archive/2010/03/02/how-ie8-determines-document-mode.aspx and http://ieblog.members.winisp.net/misc/How%20IE9%20Determines%20Document%20Mode.svg for a more detailed description of how a document mode is chosen in IE8 and IE9.

If this is not an option, consider using <meta http-equiv="X-UA-Compatible" content="IE=9" />. This will force both IE8 and IE9 to render their pages with their highest-versioned engines, which are IE8 and IE9 respectively.

kyleSencha
24 Feb 2012, 7:08 PM
Thanks for your help. The problem is solved by using <meta http-equiv="X-UA-Compatible" content="IE=9" />.