| Issue 368: | Problems with iframes | |
| 3 people starred this issue and may be notified of changes. | Back to list |
|
What steps will reproduce the problem? See attached example What version of the product are you using? On what operating system? 1.5.2 on firefox 3.5 Please provide any additional information below. I needed to create a mechanism to create nyromodals dynamically, and chose to use metadata.js. In some cases these nyromodal windows needed to be in iframes, so I went through a couple of different methods to accomplish that. Issue 1: No matter which method I use when the nyromodal is created in an iframe, the browser advances one page. Avoiding this is part of the reason for using nyromodal - so the back button doesn't suffer from unexpected behavior. Issue 2 : Apparently the main way to create an iframe is to use target="_blank". Unfortunately, this is deprecated behavior and won't validate against the strict dtd. Can some other way be found to force the iframe? Issue 3 : I want to examine the calling element (the anchor) to determine whether to force an iframe. I try to do this in processHandler(), but apparently the forceType property is processed before the processHandler() is called. I've attached a file showing the various options and the various problems. You'll have to fix up the script paths to make it work.
Nov 3, 2009
#1
cbguth...@gmail.com
Nov 4, 2009
Issue 1 occurs since I fixed Issue 246 to avoid the double loading page. Basically it's occuring when the new iframe:src is set. I don't knwo how to fix it at this time... Issue 2 : What do you think about a new setting where you'll set your attribute selector. So basically the default one would be [target=_blank]. Then, in the nyroModal code, I'll wimply test it using the is() function. Issue 3 : forceType was added to force the type of the modal before processHandler. Once processhandler is called, the type is already set. So, if you want to update the type in the processHandler callback, change the type setting and it will works.
Nov 10, 2009
I've gone with solution three as the most compact. Thanks. While I can live with Issue 1, it's pretty annoying so we probably need to keep it open as an issue. Time permitting, I may be able to take a poke at it.
Nov 10, 2009
Do you really need to use iframe? Why can't you use simple Ajax load? which so much less-memory consuming and better.
Nov 10, 2009
I wish I could and I do in many cases, but in this case I really had to go to an iframe. I'm using nyromodal to display the results of clicking on footers on many pages. In most cases (such as terms and conditions) using the ajax call is great. But for things like order status where a form is involved, a lot more javascript files are included. Rather than include those in every page, I simply include them in a separate page and use an iframe to display that page. So, basically it's an issue of not wanting to bloat all of the pages to support a seldom used command. Thanks again for the nice addon.
Nov 10, 2009
nyroModal could load your javascript when loaded through Ajax if you're adding the rel="forceLoad" if these scripts has to be executed once the modal is shown, you could add rev="shown" in your scripts tag.
Apr 16, 2010
(No comment was entered for this change.)
Status:
WontFix
|
||||||||