Re: [WSG] Show overflow in overflow:hidden
s1ntez wrote: Hi, Is it possible to show div with position:relative in container with overflow:hidden property applied. In my case the div with overflow:hidden is cutting the content of relatively positioned block, but i need to show it. No is the answer. The original purpose of overflow:hidden is to hide any content/element that spills over. I think you need to re-consider why you applied overflow:hidden to the container. If it serves no purpose then I'd recommend removing it. Alternatively reduce the width of the relatively positioned block so it doesn't extend beyond its containers boundaries. Ca Phun Ung Web: http://yelotofu.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] transitional vs. strict
To throw water into hot oil. Choosing transitional or strict will, in Gecko browser, determine whether your browser activates almost-standards-mode or standards-mode respectively [1]. [1] http://hsivonen.iki.fi/doctype/ -- Ca Phun Ung Web: http://yelotofu.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] h1 heading followed by h2 or introductory text?
kevin_erickson wrote: Hello, I have a page where the content starts with an h1 heading, followed by introductory information and this information is followed by h2 headings and their content. Is this compliant with web standards to have and h1 and an h2 seperated by text or should the introductory text be prefaced with an h2? I am thinking of accessibility and do not want to cause problems for screen readers by breaking the outline of the page. Yes. h1 followed by some introductory paragraph text then h2 is totally compliant, accessible and won't cause any problems. -- Ca Phun Ung Web: http://yelotofu.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] PNG file sizes
Mike Brown wrote: Rachel May wrote: I created the PNGs in Photoshop (CS3) and just wondering if there are any better tools or ways of saving the PNGs for smaller file size, while still retaining their high quality?? http://www.ignite-it.co.uk/ Best. Graphics. Optimiser. PlugIn. I use PNGGauntlet as an after process to optimize those PNGs. http://brh.numbera.com/software/pnggauntlet/ Unfortunately it only supports Windows. -- Ca Phun Ung Web: http://yelotofu.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Force landscape on a print style sheet?
wsg wrote:
I'm doing a print style sheet for a reporting system, and I'm trying
to figure out if it's possible to force a printer to print in
landscape orientation using CSS
Yes, there is something like that in CSS. The W3C have something called
Paged Media, see [1]. You could print in landscape just by adding the
following clause to the print style sheet:
@page {size: landscape;}
However, sadly browser support is still lacking. The above does not work
in Firefox, IE or Safari. Only Opera seems to like it.
[1] http://www.w3.org/TR/REC-CSS2/page.html
Ca Phun Ung
http://yelotofu.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] semantic list with explanations
Tim MacKay wrote: Hello all, Just looking for a little help. I'm creating a sort of 'point form' list that goes a bit like this: 1. Pursuit of customer satisfaction We promise to pursue customer satisfaction as our main point of customer focus...blah blah blah 2. Pursuit of customer loyalty We promise to pursue customer loyalty as our secondary point of customer focus...blah blah blah The critical detail here is point-form. If we were to take away the bullet points what's left are standard headings and paragraphs. Hence, a definition list is not appropriate. The way to mark this up would be: ol li h2Pursuit of customer satisfaction/h2 pWe promise to pursue customer satisfaction as our main point of customer focus.../p /li li h2Pursuit of customer loyalty/h2 pWe promise to pursue customer loyalty as our secondary point of customer focus.../p /li /ol Note: The h2 here is totally arbitrary, but do use the appropriate heading in your own code. --- Ca Phun Ung http://yelotofu.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] strong v's b , em v's i
Hi Robby, As far as I'm aware strong is here to stay. HTML and XHTML both support it. Also the page you're referring to doesn't look credible as it advocates using HTML 4.0 as a rule of thumb. Try this: http://www.w3schools.com/tags/default.asp Or if you want the definitive answer take a look at the relevant W3C guidelines. Regards, Ca Phun Robby Jennings wrote: I'm currentlycollating a coding standards document, and havearrived at thestrong v's b puzzle.I've been preaching the use of strong tags as it provides contextual mark-up of content.The b provides inlinepresentational mark-up which I'm trying to phase out. I've found this list ofdepreciated tags http://www.html-reference.com/depreciated.htmwhich lists strong and em as depreciated. I thought the b tag wouldbe depreciated. So which is correct? What should I be using?I know I can just use span tags, and apply css, it's a little clunky to me though. Any thoughts on this would be welcome. Cheers, Robby Jennings UID Developer SEEK Limited Level 2, 3 Wellington St. St Kilda, Victoria, 3182 PH : +61 3 8417 4105 FAX : +61 3 9510 7244 URL : www.seek.com.au Please consider the environment before printing emails. *** 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.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: [EMAIL PROTECTED]***
Re: [WSG] strong v's b , em v's i
Nice one Patrick, that made me laugh too... lol But on a serious note what could we do about resources like these that publicize incorrect information and advocate bad practice? Patrick Lauke wrote: Robby Jennings wrote: I've found this list of depreciated tags http://www.html-reference.com/depreciated.htm which lists strong and em as depreciated. I thought the b tag would be depreciated. The fact that they confused (based on the filename) depreciate with *deprecate* made me chuckle... depreciate: to reduce the purchasing value of (money) Them tags are getting cheaper every day... P Patrick H. Lauke Web Editor / University of Salford http://www.salford.ac.uk Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ *** 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] Minimum Height Delimma in IE
Hi Cole,
Had a look at your page and I think the problem is the overflow:hidden
applied to #container (skin.css line 18). You should see the rest of the
content if you remove that line. If overflow:hidden is absolutely
necessary then you could just remove the height values. IE will expand
the height of the box until it fills the content and FF will just use
min-height. Also the CSS child selector is perfect for overcoming the
lack of min-height support in IE6. Assuming #content is contained within
a DIV tag you could do the following (stripped out unnecessary CSS for
clarity):
#content {
min-height:500px;
height:500px;
}
div#content {
height:auto;
}
IE6 does not support the child selector so it will ignore the second
clause. FF will see min-height and height=auto. The good thing about
this is it's perfectly valid code.
Hope this helps!
Regards,
Ca-Phun
Cole Kuryakin wrote:
Hello All --
Yes the age-old minimum height delimma has come to haunt me.
I usually stay away from anything that cannot be done in IE 6 without
a hack, but I've got a client who loves a design I did before I
realized that the main container would need to be held open
vertically under certain circumstances.
So, now I'm kinda stuck -- can anyone help?
#content {
width: 510px;
min-height:500px;
height:auto;
margin: 0 0 0 30px;
color: #000;
padding-bottom: 30px;
position: relative;
z-index: 1;
}
I'm trying out Stu Nicholls solution for ie:
/*\*/
* html #content {
height: 500px;
}
/**/
But, it appears to be LIMITING the height of #content to 500px rather
than letting it expand if there's more than 500px of content.
BTW -- the reason I'm using position and a z-index on this element is
because there's a element I that that needs to show behind it. I don't
know if that has any effect on this issue or now.
Any help GREATLY appreciated and I PROMISE not to design anything else
that may cause these IE problems. God, what a headache!
If anyone would like to see the problem live, go here: in FF and then
IE 6.
Thanks to all in advance,
Cole
***
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]
***
