-
1. Re: HTML5 - maybe a matter of inheritance?
John Waller Oct 12, 2011 6:56 PM (in response to claudioparoli)Is this the link to the page you're having trouble with?
It's only the page link we need.
From there we can access every support (CSS, JS etc) file needed to diagnose the issues.
-
2. Re: HTML5 - maybe a matter of inheritance?
Ben Pleysier Oct 12, 2011 7:13 PM (in response to claudioparoli)1. phone.css and tablet.css cannot be found. Therefore it may be better to replace
<link href="../css/tbmc_mq.css" rel="stylesheet" type="text/css">
with
<link href="http://balmainmassage.com.au/css/desktop.css" rel="stylesheet" type="text/css">
2. The above will fix this as well
3. Ditto
4. Ditto
5. Ditto
Please send some of your weather down to Melbourne.
Gramps
PS. This might help http://html5boilerplate.com/
Message was edited by: altruistic gramps
-
3. Re: HTML5 - maybe a matter of inheritance?
claudioparoli Oct 12, 2011 7:12 PM (in response to John Waller)Sorry John I guess the link is not very visible. The page I'm taking about is http://balmainmassage.com.au/testing/index3.html.
I've since discovered that it's the float:left; property in the .pod class that causes the trouble - if I comment it out all the links work - but of course the page collapses. And I'm still confused as to why floating those divs should case the links to disappear.
thanks for any suggestion or advice you may come up with
-
4. Re: HTML5 - maybe a matter of inheritance?
claudioparoli Oct 12, 2011 7:19 PM (in response to Ben Pleysier)Thanks Gramps I'll see what I can do about the weather. I've FTP'd the missing files onto the site but the page only refers to desktop.css. Sort this one down and I'll come to Melbourne personally with the weather
-
5. Re: HTML5 - maybe a matter of inheritance?
Ben Pleysier Oct 12, 2011 7:32 PM (in response to claudioparoli)As I said, replace the line of code and all is hunky dory.
Gramps
-
6. Re: HTML5 - maybe a matter of inheritance?
claudioparoli Oct 12, 2011 9:02 PM (in response to Ben Pleysier)Gramps I've done as you suggest just to be on the safe side and it makes no difference. tbmc_mq.css calls up desktop.css anyway. But I'm going through the htlml5boilerplate site you suggested and it looks as if there's quite a number of useful tips. thanks again.
-
7. Re: HTML5 - maybe a matter of inheritance?
claudioparoli Oct 13, 2011 3:06 AM (in response to claudioparoli)well well well... the problem was fixed by assigning a height value (90px) to the tag header. I'm happy as Larry - at least until the next problem - but can anyone explain why this fix worked????
-
8. Re: HTML5 - maybe a matter of inheritance?
Ben Pleysier Oct 13, 2011 3:30 AM (in response to claudioparoli)Sorry, just got home.
I tested in IE (senior moment) and all was well. Now I see the problem which is caused by a relative position of the footer. Change the footer style rule to
footer {
clear: both;
}
or similar and all is well.
Weather was perfect today, got up to 23 degrees, thank you.
Gramps
-
9. Re: HTML5 - maybe a matter of inheritance?
osgood_ Oct 13, 2011 3:39 AM (in response to claudioparoli)None of your top navigation links work at the url provided in Firefox on the Mac but I assume that's without the height being added to the 'header'.
Instead of assigning a height to the 'header' (which is not good) you should asign overflow: hidden; The reason in the first instance your links were not working is because the use of 'float' in the 'nav ul li' css selector had not been cleared. When you float elements you have to clear them to allow any following element to be forced into its correct position. Because you had not cleared the floats the 'container' <div> was sitting above the links and therefore they were not accessible. overflow: hidden; will correct this and can be used because you do not have any drop menus associated with the top level links.
Now why don't the 'READ MORE','click here' links in your boxes work.
To answer your question why adding the height to the 'header' resolved the issue it's because it pushed the 'container' down making the links accessible. But height is not good to assign to any container where you have html text in my opinion although less dangerous now as the most modern browsers zoom the whole page unless you select just the text zoom.
-
10. Re: HTML5 - maybe a matter of inheritance?
Ben Pleysier Oct 13, 2011 3:38 AM (in response to claudioparoli) -
11. Re: HTML5 - maybe a matter of inheritance?
osgood_ Oct 13, 2011 3:41 AM (in response to Ben Pleysier)Your way works too Gramps
-
12. Re: HTML5 - maybe a matter of inheritance?
claudioparoli Oct 13, 2011 5:19 PM (in response to claudioparoli)Many thanks to you both, Gramps and osgood. I've updated the testing files. My page now seems to be stable, displays OK on all modern browsers and the links all work (lots of issues to sort out still, to ensure an acceptable result on previous IE versions. But that's par for the course, and I'll have to delve more into the issue of clearing the floats).
Cheers
PS Grumps cold & rainy here today. Send us a slice of Melbourne sun please...



