Hello DU and Lasse
When I say transfered I mean :
document.all[id].innerHTML = window.bufferFrame.document.body.innerHTML
being
id = my actual layer
bufferFrame = the Iframe
the body content of bufferFrame is being transfered to the layer, I'm not
sure if this is the most suitable term to use in this case.
Thank you very, very much for your time and recommendations, as a newbee I
had thought that my code was perfect and now I'm realizing that is not
(experience counts).
"DU" <drunclear@hotREMOVEmail.com> wrote in message
news:bh5dg0$6u7$1@news.eusc.inter.net...[color=blue]
> Javier wrote:
>[color=green]
> > Hello,
> > I'm very new in this forum and as I have the following problem,
> > the website is in
http://new.vanara.com[/color]
>
> --------------------------------------------------------------------------[/color]
--[color=blue][color=green]
> > --------------------------------------------
> > Here's how the site works:
> > You should press a button in the rollover area in order to load a source
> > file on an Iframe, this Iframe is actually hidden working as a Buffer.[/color][/color]
The[color=blue][color=green]
> > body of this loaded Iframe is transfered to a layer via the innerHTML[/color][/color]
method[color=blue][color=green]
> > ..
> >[/color]
>
> --------------------------------------------------------------------------[/color]
--[color=blue][color=green]
> > --------------------------------------------
> > Here's the problem:
> > The problem starts when you press the back button of the browser and the
> > text transfered to the layer changes as the Iframe does.[/color]
>
> "transfered" means what exactly? New nodes being appended and
> DOM-inserted into the DOM tree nodes? If so, then this can be verified
> with a test page. My hunch is that the dynamically altered document will
> replace the original document in the history and cache.
>[color=green]
> > It is supposed that the only text that will should change if you press[/color][/color]
the[color=blue][color=green]
> > back button, is the one loaded on the Iframe (that doesn't matter), but[/color][/color]
not[color=blue][color=green]
> > the one transfered to the layer.
> >[/color]
>
> Let me assure you that if you want to control a behavior properly and
> precisely in recent browsers, then your best chances are with using
> validated markup code, validated CSS code and W3C DOM 2 attributes and
> methods.
> Here, I don't know for sure if what you're looking for is possible. I
> have a demo page on a dynamically altered document in an iframe and
> using the forward buttons loads the dynamically altered 2nd document
> (not the original 2nd document) but that demo does not involve a 1st
> document being modified.
>[color=green]
> >
> >
> > Any help or suggestion would be very helpful.
> > Thanks,
> > Javier.
> >
> >[/color]
>
> Your frameset uses invalid attributes, has no doctype declaration. Your
> embedded stylesheet has several errors.
> Non-zero length property value must have an unit.
> 4.2 Rules for handling parsing errors
> "a unit must be specified for length values"
>
http://www.w3.org/TR/CSS2/syndata.html#parsing-errors
> 4.3.2 Lengths
> "The format of a length value (denoted by <length> in this
> specification) is an optional sign character ('+' or '-', with '+' being
> the default) immediately followed by a <number> (with or without a
> decimal point) immediately followed by a unit identifier (e.g., px, deg,
> etc.). After the '0' length, the unit identifier is optional."
>
http://www.w3.org/TR/CSS2/syndata.html#length-units
>
> You use "javascript
:" pseudo-protocol in your href values: this is bound
> to go wrong and cause problems.
>
http://jibbering.com/faq/#FAQ4_24
>
> Your page is based on table design: that's not recommendable unless you
> make use of tabular data... and here, it's not the case.
>
> You also have a frameset hierarchy: 4 frames within 2 nested framesets.
> Your
> <frame src="fill.htm" name="leftFrame" scrolling="NO" noresize>
> <frame src="fill.htm" name="rightFrame" scrolling="NO" noresize>
> are empty documents also... maybe you're still building your website..
> nevertheless..
> I recommend you do not use frames like that. You may still use an iframe
> for your webpage needs if it's the best solution for you.
>
> The document never gets loaded in NS 7.1 because, most likely, of this
> function:
> function loadSourceFinish(id){
> document.all[id].innerHTML = self.bufferFrame.document.body.innerHTML }
>
> Your code should avoid everywhere use of document.all (for cross-browser
> purposes) and innerHTML and eval() calls for many other reasons I won't
> explain here.
>
> One way to speed up rendering of your page is to minimize the number of
> .js files: here, I wonder why you can not combine these 5 external
> script files into 1 or 2 files.
>
> Your style sheet could be optimized in many ways:
>
> .content {
> font-family: Verdana, Arial, Helvetica, sans-serif;
> font-size: 9px;
> color: #666666;
> font-weight: normal;
> padding-left:0;
> line-height: 15px;
> }
>
> .content
> {
> font: normal 9px/15px Verdana,Arial,Helvetica,sans-serif;
> color:#666;
> }
>
> Note that color is an inheritable property while padding-left is not.
> So, depending on your markup code, it might not be even necessary to
> declare padding-left and color here.
>
> etc..
>
> I think you should first deal with the design of your page (many frames
> and frames should always be avoided if possible), define a tableless
> design, then validating the markup code and CSS stylesheets.
>
> DU
> --
> Javascript and Browser bugs:
>
http://www10.brinkster.com/doctorunclear/
> - Resources, help and tips for Netscape 7.x users and Composer
> - Interactive demos on Popup windows, music (audio/midi) in Netscape 7.x
>
http://www10.brinkster.com/doctorunc...e7Section.html
>[/color]
