Another help with web page request

[PaulMy]

I have no html or any other code experience but have been able to modify/copy etc. to create a few pages for my website. Now I have encountered a difficulty that my trial and error method has been unable to resolve.

I have created a new page http://www.komokaweather.com/weather/cwop/CWOPpage.html that opens in a frame in my home page http://www.komokaweather.com from CWOP Komoka Pages link. This page has 7 links to my CWOP data and the first 3 links also open in a frame and I can then easily return (go back) to the home page.

However the last 4 links open in a new window and then cannot return (go back) or get out of that new window without X and that then terminates the browser session. I have tried these 4 links with and without target="FRAME1" but no change.

I use IE but Firefox and Opera all act the same. Chrome opens in a new window and after a couple of 'go back' clicks it does return to the previous page so don't loose the browsing session.

Any suggestion how I can overcome or what code should be changed or used?

Thanks,
Paul

[beteljuice]

Simples ........

The last four links go to aprs.fi which don't want you to embed their pages on your site.

They are using a "frame-busting" code.

Code: Select all

<script type='text/JavaScript'>
//<![CDATA[
if (parent.frames.length && location.href.toLowerCase().indexOf("http://translate.google") != 0)
	top.location.href = document.location;
//]]>
</script>

Which only allows google translator to 'contain' it.

[PaulMy]

Thanks beteljuice, appreciate the explanation.

Paul

[PaulMy]

As discussed in another thread, I have been experimenting with Dreamweaver and now encountered another problem and not sure if it is caused by DW. I have then reopened the file and resaved in Notepad++ but this has not fixed the problem.

In my earlier version of index.html my webpage displays fine in all browsers (except a table width problem in Firefox I think). However as I have made various changes to the home page it displays ok in IE but in all the other browser (Chrome, Netscape, Firefox and Opera) I get garbled or code text only displayed. The Browser Compatibility check in DW shows "No issues detected".

I have now reused my older version for the current index.html at http://www.komokaweather.com and this seems fine in all browsers. My revised index file is uploaded as http://www.komokaweather.com/index-Copy ... 17.09.html and this has the issues in all except IE. I have checked the code one line at the time to look at the differences and can't detect what changes between the two are causing the problem. I have also read a few sections of the W3Schools Online Web Tutorials but have not seen anything that helps me with this problem. Any suggestions to help me with this?

Thanks,
Paul

[GraemeT]

Hi Paul,

It looks like DW has somehow rewritten/encoded your html.

This might be caused by settings in DW.

Check Edit/Preferences/Code Rewriting

Make sure of the following settings:
Fix invalidly nested and unclosed tags - untick
Rename form items when pasting - tick
Remove extra closing tags - untick
Never rewrite code: in files with extensions .as .asr .asc .asp .ascx .asmx .aspx .cfc .cfm .cfml .config .cs .ihtml .js .jsp .php .php3 .vb .xml .xsl .xslt .xul
Special characters: tick Encode <, >, &, and " in attribute values using &
URL encoding: Do not encode special characters

Edit: This URL might also be helpful: http://help.adobe.com/en_US/Dreamweaver ... 3f21-7beea

[PaulMy]

Thanks Graeme,
I had a few that were set different. Not a lot of big changes to redo from the earlier version. Another lesson learned, but DW has been very good to help me understand the results of coding.

p.s. You can celebrate with us as our son's wife Kathryn delivered twins yesterday - two beautiful and healthy boys. Kathryn is from Parkes, NSW and her parents, also from Parkes, NSW, are here for a couple of months to help her along. For Canada: 2 hockey stars; for Australia: maybe 2 future AFL (Swans) or Rugby League recruits

p.s. we've wanted to show the parents some of our Canadian winter hospitality but it is and has been much more like summer weather here since they arrived a couple weeks ago.

And thanks for the link.

Paul

[beteljuice]

Shouldn't this be untick ?

Special characters: tick Encode <, >, &, and " in attribute values using &

[GraemeT]

Paul,

You can celebrate with us as our son's wife Kathryn delivered twins yesterday - two beautiful and healthy boys

My wife and I also have twin boys - aged 21 now.


Beteljuice,

Shouldn't this be untick ?

Maybe, but it's never caused me any grief (yet).
It doesn't generally affect to display of pages, just makes them hard to read in editors. (like &nbsp; etc.)
Having said that, I don't allow DW to reformat my pages.

[serowe]

Paul - in IE9 you have something else wrong with your main page as well - your physical page accounts for about 40% of the screen and the remaining 60% is just blank white scren (scrolling downwards).

I can't see anything obvious in the code that is causing it (ie transplanting the index.php code into php Designer V8, it doesn't show any obvious erros (missing tags etc) but something is adding white space/lines to the display somewhere.

Edit - actually think I found the problem - after every image you have the following code:

Code: Select all

<br /><br />

One issue with web browsers when displaying images (of any type) is they sometimes display all of the images and THEN display any intervening code. Try removing all of these breaks (it will drag the images together for now) and it shold remove the dead space at the end of the page.

[beteljuice]

I think

Code: Select all

<iframe name="frame1" src="/weather/index.htm" frameborder="0" height="17000" scrolling="no" width="1000">
</iframe>

Might have something to do with it (height attribute)

[serowe]

Interesting - viewing the source of the iFrame doesn't show the source of the main page - and vice versa...

[PaulMy]

Might have something to do with it (height attribute)

I really don't know what I am doing but with trial and error I get along
Yes, I have been gradually increasing the height as I have been adding images so that all the images can appear in the main frame. The longest is the daily images for the Sunrecorder monthly history pages and that is why I have it at 17000 now. Some day I'll learn how to do that different/better

I have it now working in six browsers, except that in Chrome and Safari the left menu frame has a very long top margin (coloured blank area) before the links show. I have just begun to search on what settings impact the different browsers so I can work on correcting that issue. I have been using Notepad++ to fix the index.html file that appeared to have been corrupted and will try again in DW later in the week to see how/why things may change with DW. Once I feel comfortable and safe with DW I'll try working on the colours again.

Any quick suggestion that will help me why/how different browsers are affected by the same code, like mentioned above?

Thanks for your comment,

Paul

[serowe]

Paul - I have to ask, though - why are you using an iFrame in the first place? Whilst it is (possibly) Ok to use in HTML, it is depracted in XHTML so really shouldn't be used.

Also, by stipulating such a horrendously long length you are more than doubling the total length of the display screen that you need.

http://www.w3schools.com/tags/tag_iframe.asp

[PaulMy]

Paul - I have to ask, though - why are you using an iFrame in the first place?

Becasue that was the template set up for me early in my site's startup, and I don't know yet how else to have the separate side menu. And by the looks of the length of the December and January Sunrecorder history files I can shorten it a bit, but not very much. Having said that, I will be using DW, or at least hope to, to present the history differently by using the Sunrecorder's saved daily image files instead of the screen capture I now do for each day. As I've said before, trial and error and one step at a time and that's been some of the fun

Paul

[serowe]

Try playing around without the iFrame in it then - as I said, it is old coding style/practice now and really shouldn;t be used.

I presume you are testing it on a home based server first (XAMPP or WAMP) which would make it a lot easier to test and try things out.

Even try it without the height=1700 code - it *should* dynamically size itself without it.