RE: [WSG] working with line-height

2009-07-01 Thread Ant Tears
Hi Ben,
It seems that the short answer to your question is a base line-height of 0.8 
(yup, unitless).
My guess would have been the value 1 but I don't know enough about browser 
default styles to say why 0.8 seems to work.
I've only checked this using IE8 and Firefox 3.5 using the developer tool bar, 
so there's a fair chance I'm talking crap, but it's probably an avenue worth 
investigating.

As with so many things CSS my knowledge comes directly from Eric Meyer, so I'll 
link his site.
http://meyerweb.com/eric/thoughts/2006/02/08/unitless-line-heights/

Cheers,
Ant

From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On 
Behalf Of Ben Lau
Sent: 01 July 2009 16:20
To: wsg@webstandardsgroup.org
Subject: [WSG] working with line-height

Hi list,

I frequently have to work with pixel-perfect design, and I'm always having 
trouble with line-height in particular. Please take a look at this example: 
http://www.hellobenlau.net/wsg/index.html

I'm wondering if there was a way to top align the text to its line-height. So 
say, with text size 20px, could the top of the 'T' be aligned to the top of the 
pink box?
How does the 'gap' above and below the text gets calculated?

Thanks
Ben

[]
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


IMPORTANT NOTICE:
This email contains proprietary information, some or all of which may be 
legally privileged. It is for the intended recipient only. If an addressing or 
transmission error has misdirected this email, please notify the author by 
replying to this email. If you are not the intended recipient you must not use, 
disclose, distribute, copy, print or rely on this email. In addition you must 
erase all information contained in this email immediately after notifying the 
author. No liability is accepted for viruses and it is your responsibility to 
scan attachments (if any). Unless related to the business of the firm, the 
opinions expressed within this email are the opinions of the sender and do not 
necessarily constitute those of Conscia Enterprise Systems Ltd, whose 
registered address is 280 St Vincent Street, Glasgow, G2 5RL, United Kingdom.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


RE: [WSG] a target= blank not part of xhtml

2008-03-27 Thread Ant Tears
Hi Michael,
If I recall / understood correctly, the opening of a new browser window
was seen by the W3C as functionality and therefore consigned to
scripting.

As for web standards prohibiting opening of new windows, this AA
requirement is a little ambiguous for my taste:
10.1 Until user agents allow users to turn off spawned windows, do not
cause pop-ups or other windows to appear and do not change the current
window without informing the user.

The WCAG Samuari Errata states:

Do not cause pop-ups or other windows to appear and do not change the
current window without informing the user.

* Plain text is the strongly preferred method of informing the user.
Use of any other method must be reserved for cases where plain text is
unreasonably difficult or impossible.
* The title attribute on a hyperlink a element can suffice in the
unique case of legacy pages that are unreasonably difficult to update.
It is not sufficient in newly-created pages or other circumstances.

This shows more clearly shows that opening new windows is not deemed
illegal. However, it gives little indication as to when it is acceptable
to open a new window.
Jackob Neilsen rates it in his top 10 design mistakes
http://www.useit.com/alertbox/9605.html

This one talks about opening non html docs in a new window:
http://www.useit.com/alertbox/open_new_windows.html

Ant








-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Michael Horowitz
Sent: 27 March 2008 16:36
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] a target= blank not part of xhtml

Has the same problem. Target is not xhtml.

Are people arguing web standards prohibit opening a new page in a new 
browser or tab?

Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079



Rob Kirton wrote:
 Michael

 I would recommend that you use target=_new and then use XHTML 
 transitional DTD

 -- 
 Regards

 - Rob

 Raising web standards  : http://ele.vation.co.uk
 Linking in with others: http://linkedin.com/in/robkirton


 On 27/03/2008, *Michael Horowitz* [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:

 I just read how a target=_blank is not part of xhtml

 Why not.  I can't imagine its better practice to replace it with
 javascript.

http://weblogtoolscollection.com/archives/2004/01/02/targetblank-xhtml-1
0-strict-conversion/

 --
 Michael Horowitz
 Your Computer Consultant
 http://yourcomputerconsultant.com
 561-394-9079




***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]

***


 ***
 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]
***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



RE: [WSG] Best way to clear a float

2007-11-12 Thread Ant Tears
Hi Jamie,

Easy clear is my current method of clearing also.

The only problem is that your css does not then validate (as
inline-block is from the css2.1 spec)

 This is a W3C Candidate Recommendation, which means the specification
has been widely reviewed and W3C recommends that it be implemented. It
will remain Candidate Recommendation at least until 20 December 2007.
http://www.w3.org/TR/CSS21/#crec  A test suite and a report on
implementations will be provided before the document becomes a Proposed
Recommendation. Badger

 

Am I correct in thinking that once it becomes a Proposed Recommendation
the validator will be altered and the css will then validate?

It would be nice to have validating css again :-)

 

Ant



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jamie Stewart
Sent: 12 November 2007 16:15
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Best way to clear a float

 

My preference would be to clear floats through the CSS and not through
adding in any additional markup.  The code for this is below, so any two
elements being floated to sit side by side should be put in a container
with the class .clearfix. 

I use this approach purely because I view this as a presentation issue
and not a reason to add a new element to your HTML structure.  I hope
this helps and here is a link explaining the below example
http://www.positioniseverything.net/easyclearing.html

Cheers
Jamie Stewart

.clearfix:after {

content: .; 

display: block; 

height: 0; 

clear: both; 

visibility: hidden;


}



.clearfix {display: inline-block;}



/* Hides from IE-mac \*/

* html .clearfix {height: 1%;}

.clearfix {display: block;}

/* End hide from IE-mac */
 

 

On 12/11/2007, Likely, James A. [EMAIL PROTECTED] wrote:

Hello, 

I am curious to see how others clear floats. 

Here is the problem. Div one and two float left and take 50% of the
screen. Content is to go below the two floats. 

div style=float: leftone/div 
div style=float: lefttwo/div 
divContent/div 

In the past I would use: 

div style=float: leftone/div 
div style=float: lefttwo/div 
br style=clear: both; / 
divContent/div 

As this seemed to be the only method to make the clear work in IE. I am
curious to see how others do this and if you are doing it with out using
the br style=clear:both / 

What method are you using to make this work in IE? 

Thanks 

Jamie 


***
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]
***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***


[WSG] Two columns, one fluid one fixed?

2005-08-18 Thread Ant Tears
Title: Two columns, one fluid one fixed?



I'm 
not so good with floats, but this might be a different 
approach:

#container{ text-align: left; margin: 0; 
margin-right:185px;} #centrecontent { border: 1px solid 
red;} #right { width:182px; 
position:absolute;right:5px;border: 1px solid blue; 
}

  -Original Message-From: Bennie, Jack 
  [mailto:[EMAIL PROTECTED]Sent: 18 August 2005 
  09:55To: wsg@webstandardsgroup.orgSubject: [WSG] Two 
  columns, one fluid one fixed?
  Hey Guys Got 
  a simple one, but can't seem to get my head round it I'm after a 2 column setup, one fixed width and the other 
  fluid. I can get the following code to work in IE 5, 5.5 and 6, but not in 
  Safari, Mac IE 5.2 and Firefox...
  !DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 
  Transitional//EN" html 
  head titleUntitled/title style #container{ 
  text-align: left; margin: 0; width: 100%; 
  } #centrecontent { float: 
  left; border: 1px solid red; 
  } #right 
  { width:182px; float:right; border: 
  1px solid blue; } /style /head body 
  div id="container" div id="right" Eant et fugiant a te inquieti iniqui. et tu vides eos et distinguis 
  umbras, et ecce pulchra sunt cum eis omnia, et ipsi turpes sunt. et quid 
  nocuerunt tibi? aut in quo imperium tuum dehonestaverunt, a caelis usque in 
  novissima iustum et integrum? quo enim fugerunt, cum fugerent a facie tua? aut 
  ubi tu non invenis eos? sed fugerunt, ut non viderent te videntem se, atque 
  excaecati in te offenderent
  /div div id="centrecontent" Eant et fugiant a te inquieti iniqui. et tu vides eos et distinguis 
  umbras, et ecce pulchra sunt cum eis omnia, et ipsi turpes sunt. et quid 
  nocuerunt tibi? aut in quo imperium tuum dehonestaverunt, a caelis usque in 
  novissima iustum et integrum? quo enim fugerunt, cum fugerent a facie tua? aut 
  ubi tu non invenis eos? sed fugerunt, ut non viderent te videntem se, atque 
  excaecati in te offenderent
  /div /div /body 
  /html 
  I'm pretty sure it's something simple, but it's 
  the end of the day and I can't spot it! Any ideas? I need to keep the the 
  :float: left;" in the "#centrecontent"
  Thanks in advance... 
  Regards Jack Bennie Web Developer - Web Services 
  This 
  message, including any attached files, is intended solely for the addressee 
  named and may contain confidential information. If you are not the 
  intended recipient, please delete it and notify the sender. Any views 
  expressed in this message are those of the individual sender and are not 
  necessarily the views of WorkCover 
  NSW.