Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <1350245.WGnKmheAe9@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Wed, 28 Dec 2011 14:50:28 +0100 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 8Bit Subject: Re: cross-scripting issue: use javascript/DOM on iframe loaded from different domain, how? Newsgroups: comp.lang.javascript References: <4ef07168$0$6637$9b4e6d93@newsspool2.arcor-online.net> <5302802.FDOyZ681go@PointedEars.de> Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 43 NNTP-Posting-Date: 28 Dec 2011 14:50:29 CET NNTP-Posting-Host: 86c0fff6.newsspool3.arcor-online.net X-Trace: DXC=AQQkn=nAF0L[6=1B@oB@@@McF=Q^Z^V3H4Fo<]lROoRA8kF Thanks very much to everyone who posted, I will ask the people who host > the page I'm loading into the Iframe to implement the code Bart > recommended. However, the proper code for that approach would be … It would be even better if they did not use client-side scripting, but server-side scripting to generate the form, and if they generated the `selected' attribute specification on a different `option' element if the parameter was detected in the document's URL. PointedEars -- Danny Goodman's books are out of date and teach practices that are positively harmful for cross-browser scripting. -- Richard Cornford, cljs, (2004)