#12096 closed defect (worksforme)
dijit.form.ComboBox renders incorrectly in IE 7 mode of IE 8
Reported by: | saj14saj | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | tbd |
Component: | Dijit - Form | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
Attachments (1)
Change History (7)
Changed 10 years ago by
Attachment: | ComboBox comparison.png added |
---|
comment:1 Changed 10 years ago by
Seems to be a duplicate of mine http://trac.dojotoolkit.org/ticket/11992
Bill wasn't able to reproduce even though I can reproduce on 3 different machines, very same issue as you.
comment:2 Changed 10 years ago by
Additional information:
This rendering bug only happens in QUIRKS mode. When a doctype triggers standards mode, rendering is good.
Rendering problems in quirks mode can also be seen in the theme test page.
comment:3 Changed 10 years ago by
Description: | modified (diff) |
---|
comment:4 Changed 10 years ago by
Owner: | set to Douglas Hays |
---|
I tried loading themeTesterQuirk.html on IE8 with the IE7-compat mode button depressed, it loads fine for me. Maybe Doug can reproduce.
comment:5 Changed 10 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Please append a testcase. themeTester and the fs.html from #11992 work for me. This problem is easy to recreate with bad CSS. Starting in Dojo 1.5, the arrow icon is an INPUT as well. Note even in the attached Firefox screenshot that the arrow is cut-off. This means that the font-size or padding of that INPUT is different than that of the main INPUT. Most likely some custom user-defined CSS will need to be tweaked to either include all INPUT tags within the widget template or else the special dijit class dijitInputField, depending on the actual user-defined CSS.
comment:6 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
Screenshot comparing FF vs IE 7 mode rendering