Why not use an IFRAME hack in ModalDialogV2 ?
If you've read my Modal Dialog enhanced article; you may wonder the reason why I obsinately insist on not using an IFRAME to stop the bleed through when a layer moves over a HTML Select element and I use SPANs instead.
I have received several e-mails asking the reason behind it. And since the method I propose in the article is much complicated than simply using and IFRAME, you are right in wondering the reason why.
May the source be with you!
bu yaziyi sevdin mi?
hemen
una ekle!
I have received several e-mails asking the reason behind it. And since the method I propose in the article is much complicated than simply using and IFRAME, you are right in wondering the reason why.
The legitimate usage of the IFRAME is to provide external data; such as a disclaimer or a web service.- Introducing a non-semantic element (with or without JavaScript) does not eliminate the fact that it is used in a semantically incorrect fashion.
- May be in the future IFRAMEs wil behave differenly and allow bleed-through, who knows.
However spans will always behave as intended because I use them in a semantically correct way: They are used to wrap text around. And this usage is a supplementary method to enhance user experience; not an ugly hack that utilizes the user agent's render characteristics. - Yet another reason; people may tend to browse frame support disabled. Or their user agents may not have frame support at all (and old browser, or a PDA for instance).
I know, that's equally true for JavaScript, but who really turns JavaScript off anyway? - From my testings, IFRAME hack only works in IE5.5 and above (it may be a concern for some people; but I don't think it's a big deal).
- Activex, Java, Flash etc.. is another story. If you would like to implement the third method; you can replace them with a static alternative (an image or text may be). But I admit that's a bit overkill.
May the source be with you!
Labels: ajax, bestpractice, javascript, modaldialog
bu yaziyi sevdin mi?
hemen
una ekle!
- permalink: 11:16 PM


0 Coments
Post a Comment
Links to this post:
Create a Link
<< Home