Search and Top Navigation
#9139 closed bug (notabug)
Opened March 07, 2013 01:45AM UTC
Closed March 07, 2013 01:49AM UTC
Last modified March 07, 2013 02:04AM UTC
Dialog demo html fails on Internet Explorer
Reported by: | cwu03d | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.dialog | Version: | 1.10.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Although the online demos for dialog samples work all all browsers, the standalone demo fails working on Internet explorer ( I used I.E. 10 on Windows 8). All sample html files under Web\\jquery-ui-1.10.1.custom\\development-bundle\\demos\\dialog will not properly show UI effect.
Cause: All demo html files for dialog has this sentence:
<meta charset="utf-8" >
The missing close tag will cause I.E. 10 behave improperly.
Fix: Add the closing tag for meta fixed problem:
<meta charset="utf-8" />
Other:
Please check all the demo html for the same case, apply fix if that is the case.
Attachments (0)
Change History (3)
Changed March 07, 2013 01:49AM UTC by comment:1
resolution: | → notabug |
---|---|
status: | new → closed |
Changed March 07, 2013 02:00AM UTC by comment:2
scott.gonzalez is somehow arrogant and irresponsible. Why don't download the zip file, extract to some location, then open any of the html files with I.E, see what happens?
Please also compare the demo html source and the online version, you will see the online version meta tag is closed, as <meta charset="utf-8" />
but the ones from downloaded zip file doesn't.
As a software engineer, I have handled a of bugs. But never to rush to close any bug without investigation. Sorry for you guys.
Changed March 07, 2013 02:04AM UTC by comment:3
Arrogance and irresponsibility (and a quick trigger finger) are important qualities. We'll pretend for a while that I've never opened any of our demo files in IE 10, and that none of our millions of users have either. Does http://view.jqueryui.com/1.10.1/demos/dialog/default.html fail for you?
This is perfectly valid and works everywhere, as you've noted. Perhaps you're changing something in your local settings, like forcing XHTML.