Re: [WSG] Help needed
On 11 May 2007, at 05:52:58, John Faulds wrote:
You really only need a dimension on the anchors to overcome an IE/
Windows bug when they're set to display: block so you can either
use * html #nav a { height: 1% } or conditional comments. You can
probably ignore my other comment about the hasLayout issue because
I assumed it was an IE problem, but it's not.
If you want to triger hasLayout and you don't have to worry about IE
5.x, you're better off using zoom: 1; rather than mucking about
setting dimensions that IE will just ignore and then having to use
hacks to hide them from other browsers (including IE 7).
Regards,
Nick.
--
Nick Fitzsimons
http://www.nickfitz.co.uk/
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
[WSG] Help needed
Hi there I¹ve got a problem with a page I¹m having to do in a hurry! Site has to go live and be demo¹d at a launch on Monday ... I only got the content, graphic layout etc. a couple of days ago. (And it¹s an official university sub-site so I¹m forced to use some of their code (tables?!!) and styles in part of it.) Anyway, my problem is well 3 things. 1. In the lefthand nav I would have liked to have some of the 2nd level link¹s not links. But my code is up the creek and I can¹t make them line up or be the same font size unless they¹re all links. Any clues on what I¹m doing wrong here? 2. And also, the bottom 2 2nd-level links jump when you roll over them. I can¹t see why! The top 2 are OK. 3. I also can¹t see why the foot2¹ style isn¹t applying to the footer. http://crunchie.tedi.uq.edu.au/Trials/TEDICDIP/index.html I know the stylesheet (styles2.css) is a mess. I based it on an old one for another site and probably shouldn¹t. But it¹s panic stations all round! I don¹t think anything from the imported UQ stylesheet is causing a problem, but ... Anyway, if anyone could see what is causing that problem, I¹d be very grateful!! (I¹m highly embarrassed to expose such a mess, but needs must!!) - susie *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Help needed
1. In the lefthand nav I would have liked to have some of the 2nd level Œlink¹s not links. But my code is up the creek and I can¹t make them line up or be the same font size unless they¹re all links. Any clues on what I¹m doing wrong here? Are these IE problems? If so, it's because the anchors are set to display block which causes a bug in IE which can be reset by also giving the anchors a dimension. 2. And also, the bottom 2 2nd-level links jump when you roll over them. I can¹t see why! The top 2 are OK. I'm not really seeing this but it's probably a hasLayout issue which may be solved by adding a dimension to the problem element or its parent. 3. I also can¹t see why the Œfoot2¹ style isn¹t applying to the footer. I don't see any footer2 styles in your CSS. -- Tyssen Design www.tyssendesign.com.au Ph: (07) 3300 3303 Mb: 0405 678 590 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Help needed
On 11/5/07 12:30 PM, John Faulds [EMAIL PROTECTED] wrote: 1. In the lefthand nav I would have liked to have some of the 2nd level Œlink¹s not links. But my code is up the creek and I can¹t make them line up or be the same font size unless they¹re all links. Any clues on what I¹m doing wrong here? Are these IE problems? If so, it's because the anchors are set to display block which causes a bug in IE which can be reset by also giving the anchors a dimension. No I'm looking at this in Firefox on a Mac. It doesn't happen in Safari ... 2. And also, the bottom 2 2nd-level links jump when you roll over them. I can¹t see why! The top 2 are OK. I'm not really seeing this but it's probably a hasLayout issue which may be solved by adding a dimension to the problem element or its parent. Ditto the above ... I don't know what this 'hasLayout' thing is ... 3. I also can¹t see why the Œfoot2¹ style isn¹t applying to the footer. I don't see any footer2 styles in your CSS. It's there - I've doublechecked. Near the bottom ... :) *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Help needed
Can't help you with your Mac problems, I can only tell you what I see in Windows (and the suggested fixes will still apply), but for the footer problem, remove */ from just above /* FOOTER STYLE */ - it's closing a comment that's not opened. On Fri, 11 May 2007 13:00:49 +1000, Susie Gardner-Brown [EMAIL PROTECTED] wrote: On 11/5/07 12:30 PM, John Faulds [EMAIL PROTECTED] wrote: snip Are these IE problems? If so, it's because the anchors are set to display block which causes a bug in IE which can be reset by also giving the anchors a dimension. No I'm looking at this in Firefox on a Mac. It doesn't happen in Safari ... snip I'm not really seeing this but it's probably a hasLayout issue which may be solved by adding a dimension to the problem element or its parent. Ditto the above ... I don't know what this 'hasLayout' thing is ... snip I don't see any footer2 styles in your CSS. It's there - I've doublechecked. Near the bottom ... :) *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** -- Tyssen Design www.tyssendesign.com.au Ph: (07) 3300 3303 Mb: 0405 678 590 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Help needed
Thanks John. I found the errant */ and the footer is working as it should, so thanks for that. I don't know where my brain is this afternoon - frozen up I think! Would you mind explaining what the fixes actually are? If I give the anchor (link) styles a width, I'm not clear how to do that and make it accurate. Whatever I've tried has taken the bg colour out further than the navbar, and hasn't made any difference to the jumping. And what would the code be for a hasLayout issue? I haven't come across that before ... - susie On 11/5/07 1:27 PM, John Faulds [EMAIL PROTECTED] wrote: Can't help you with your Mac problems, I can only tell you what I see in Windows (and the suggested fixes will still apply), but for the footer problem, remove */ from just above /* FOOTER STYLE */ - it's closing a comment that's not opened. On Fri, 11 May 2007 13:00:49 +1000, Susie Gardner-Brown [EMAIL PROTECTED] wrote: On 11/5/07 12:30 PM, John Faulds [EMAIL PROTECTED] wrote: snip Are these IE problems? If so, it's because the anchors are set to display block which causes a bug in IE which can be reset by also giving the anchors a dimension. No I'm looking at this in Firefox on a Mac. It doesn't happen in Safari ... snip I'm not really seeing this but it's probably a hasLayout issue which may be solved by adding a dimension to the problem element or its parent. Ditto the above ... I don't know what this 'hasLayout' thing is ... snip I don't see any footer2 styles in your CSS. It's there - I've doublechecked. Near the bottom ... :) *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Help needed
You really only need a dimension on the anchors to overcome an IE/Windows
bug when they're set to display: block so you can either use * html #nav a
{ height: 1% } or conditional comments. You can probably ignore my other
comment about the hasLayout issue because I assumed it was an IE problem,
but it's not.
On Fri, 11 May 2007 14:30:57 +1000, Susie Gardner-Brown
[EMAIL PROTECTED] wrote:
Thanks John.
I found the errant */ and the footer is working as it should, so thanks
for that. I don't know where my brain is this afternoon - frozen up I
think!
Would you mind explaining what the fixes actually are? If I give the
anchor
(link) styles a width, I'm not clear how to do that and make it accurate.
Whatever I've tried has taken the bg colour out further than the navbar,
and
hasn't made any difference to the jumping. And what would the code be
for a
hasLayout issue? I haven't come across that before ...
- susie
On 11/5/07 1:27 PM, John Faulds [EMAIL PROTECTED] wrote:
Can't help you with your Mac problems, I can only tell you what I see in
Windows (and the suggested fixes will still apply), but for the footer
problem, remove */ from just above /* FOOTER STYLE */ - it's
closing a
comment that's not opened.
On Fri, 11 May 2007 13:00:49 +1000, Susie Gardner-Brown
[EMAIL PROTECTED] wrote:
snip
snip
snip
snip
snip
snip
snip
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
--
Tyssen Design
www.tyssendesign.com.au
Ph: (07) 3300 3303
Mb: 0405 678 590
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
[WSG] Help needed with IE drama...
Hello fellow standardites, I'm losing hair over a very annoying IE anomaly... http://golfgods.dev.netconcepts.com/layout.html [check it in FireFox to see how it should be] the bit at the bottom (the section with the border switched on) isn't behaving as i expect it to. its simply an image in a p element...IE has no idea what to do with it and its driving me crazy! the main style sheet is here: http://golfgods.dev.netconcepts.com/css/style.css and the IE hacks are here: http://golfgods.dev.netconcepts.com/css/iehacks.css Any help would be greatly appreciated. Cheers Darren ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Help needed with IE drama...
We've worked out that the issue was caused by the comments in the HTML file. Has anyone had this sort of issue before? If there a solution other then removing the comments? Cheers D On 11/4/05, Darren Wood [EMAIL PROTECTED] wrote: Hello fellow standardites, I'm losing hair over a very annoying IE anomaly... http://golfgods.dev.netconcepts.com/layout.html [check it in FireFox to see how it should be] the bit at the bottom (the section with the border switched on) isn't behaving as i expect it to. its simply an image in a p element...IE has no idea what to do with it and its driving me crazy! the main style sheet is here: http://golfgods.dev.netconcepts.com/css/style.css and the IE hacks are here: http://golfgods.dev.netconcepts.com/css/iehacks.css Any help would be greatly appreciated. Cheers Darren ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
Re: [WSG] Help needed with IE drama...
Hi Darren, I haven't reviewed the bug, however if its anything like the issue we've come across with comments [1] then you could try an alternative method of commenting the code. (This goes somewhat to the concept of semantic markup also.) Rather than: !-- begin footer -- div id=footer ... /div !-- end footer -- try: div id=footer ... !-- end footer --/div Rationale: The id attribute identifies the nature of the div (as a result of taking a semantic approach to assigning the id value there is no need 'duplicate' this information in the comment). It is more problematic to keep track of the end of the div, and so a comment is useful. Placing the end comment inside the /div avoids the issue with floats and comments. Admittedly, it took me a while to get used to the new coding convention, but the judicious use of white space helps. [1] Bug caused by floats and comments: http://www.positioniseverything.net/explorer/dup-characters.html We've worked out that the issue was caused by the comments in the HTML file. Has anyone had this sort of issue before? If there a solution other then removing the comments? Best regards, -- Andy Kirkwood | Creative Director Motive | web.design.integrity http://www.motive.co.nz ph: (04) 3 800 800 fx: (04) 970 9693 mob: 021 369 693 93 Rintoul St, Newtown PO Box 7150, Wellington South, New Zealand ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] Help needed with IE drama...
On the topic of commenting styles, I use the following: !-- [header + logo -- div id=header ... /div !-- header] -- So the id of the element is right next to a opening or closing square bracket indicating if it's a start or end of the block. Works well for us. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Kirkwood|Motive Sent: Friday, 4 November 2005 3:53 p.m. To: wsg@webstandardsgroup.org Subject: Re: [WSG] Help needed with IE drama... Hi Darren, I haven't reviewed the bug, however if its anything like the issue we've come across with comments [1] then you could try an alternative method of commenting the code. (This goes somewhat to the concept of semantic markup also.) Rather than: !-- begin footer -- div id=footer ... /div !-- end footer -- try: div id=footer ... !-- end footer --/div Rationale: The id attribute identifies the nature of the div (as a result of taking a semantic approach to assigning the id value there is no need 'duplicate' this information in the comment). It is more problematic to keep track of the end of the div, and so a comment is useful. Placing the end comment inside the /div avoids the issue with floats and comments. Admittedly, it took me a while to get used to the new coding convention, but the judicious use of white space helps. [1] Bug caused by floats and comments: http://www.positioniseverything.net/explorer/dup-characters.html We've worked out that the issue was caused by the comments in the HTML file. Has anyone had this sort of issue before? If there a solution other then removing the comments? Best regards, -- Andy Kirkwood | Creative Director Motive | web.design.integrity http://www.motive.co.nz ph: (04) 3 800 800 fx: (04) 970 9693 mob: 021 369 693 93 Rintoul St, Newtown PO Box 7150, Wellington South, New Zealand ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
