RE: [WSG] How to detect bottom of a page?
In your screen stylesheet you should have:
display: block;
font-weight: bold;
font-size: 150%;
bottom: 45px;
position: absolute;
This will align the div to the bottom of the screen (what you originally
had) when viewed on a screen.
In your print stylesheet you should have
display: block;
font-weight: bold;
font-size: 150%;
bottom: auto;
position: static;
This will position the div after any content when you print it.
In both cases the footer divs should appear after your content in the HTML.
Also look at changing the fonts from %'s to pt's in the print stylesheet,
this will suit printing better.
-Original Message-
From: listdad@webstandardsgroup.org [mailto:[EMAIL PROTECTED]
On Behalf Of Bojana Lalic
Sent: Wednesday, 7 June 2006 3:09 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] How to detect bottom of a page?
I do have a print stylesheet and this is what's in it:
.framework_url {
display: block;
font-weight: bold;
font-size: 150%;
bottom: auto;
position: static;
}
I've also got another stylesheet which has the following:
.framework_url {
display: none;
}
What's missing?
-Original Message-
From: listdad@webstandardsgroup.org
[mailto:[EMAIL PROTECTED] On Behalf Of Samuel Richardson
Sent: Wednesday, June 07, 2006 1:31 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] How to detect bottom of a page?
Like I said in my original email serve those rules below only when you
print
the page, serve your original rules when the page is viewed on the
screen.
Google CSS Media to find out how to serve different CSS files based on
what device is being used to access the page.
S
-Original Message-
From: listdad@webstandardsgroup.org
[mailto:[EMAIL PROTECTED]
On Behalf Of Bojana Lalic
Sent: Wednesday, 7 June 2006 1:29 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] How to detect bottom of a page?
The div is now appearing after the content in HTML and is appearing at
the end of the content on the last page but not appearing at the bottom.
This is the css:
display: block;
font-weight: bold;
font-size: 150%;
bottom: auto;
position: static;
How do I force the div to display at the bottom of the page, regardless
of how much content there is on the page?
-Original Message-
From: listdad@webstandardsgroup.org
[mailto:[EMAIL PROTECTED] On Behalf Of Samuel Richardson
Sent: Tuesday, June 06, 2006 4:20 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] How to detect bottom of a page?
B,
Make sure the div that is appearing at the bottom of the page appears
after
your content in the HTML. Then in a print only style sheet format that
block
to be position : static;
This will cause the footer to be pushed down from the content on the
page
again. IE may still use the bottom CSS rule even though it should (due
to
the position : static;) if this is the cause then add bottom : auto; to
make
it behave.
- Samuel
Read my blog if you're coming to Melbourne :
http://www.seasonstravel.com.au
-Original Message-
From: listdad@webstandardsgroup.org
[mailto:[EMAIL PROTECTED]
On Behalf Of Bojana Lalic
Sent: Tuesday, 6 June 2006 4:33 PM
To: Paul Novitski; wsg@webstandardsgroup.org
Subject: RE: [WSG] How to detect bottom of a page?
Hi all
This is the css I used to display the url at the bottom of the page:
display: block;
font-weight: bold;
font-size: 150%;
bottom: 45px;
position: absolute;
However, I've got a slight problem now. When printing out the article
that is three pages long (when printed out) the url appears on the first
page. How do I force it to display only on the last page?
Cheers
Bojana
-Original Message-
From: Paul Novitski [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 20, 2006 6:46 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] How to detect bottom of a page?
At 06:57 PM 4/19/2006, Bojana Lalic wrote:
I am working on a print stylesheet. What I need to do is display a
url at the bottom of the last page.
I understand that this can be done with CSS3 float: bottom; but is
there another way of doing this?
I wonder if you can simply mark up the URL at the bottom of your HTML
page, then suppress it from screen display if desired.
Paul
Global Summit 2006: Technology Connected Futures -- 17-19 October,
Sydney,
Australia.
Visit our website http://www.educationau.edu.au/globalsummit2006 for
further
details.
_
IMPORTANT: This e-mail, including any attachments, may contain private
or
confidential information.
If you think you may not be the intended recipient, or if you have
received
this e-mail in error,
please contact the sender immediately and delete all copies of this
e-mail.
If you are not the intended
recipient,
[WSG] Alignment Issues in IE6 on XP only?
I seem to be having an alignment issue that only appears in IE6 on XP. It is fine in all other browsers tested including IE6 on W2k, both Win + Mac FF, Safari Opera.The alignment issues are seen on the vertical lines running at the edges and in the left blue column. An example page can be viewed via:http://wsg.dnsalias.com/about/And an XP screenshot at: http://wsg.dnsalias.com/xp.JPGAny help appreciated,CheersMartin **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] XHTML Strict
Patrick H. Lauke wrote: Thierry Koblentz wrote: The issue is not about the attributes but their value; and in the example I wrote, the validator would choke on the ID's *value*. Because 1st_Section is a valid value for the name attribute but it is *not* for the id attribute. To expand: because the name attribute can contain any CDATA, while id *must* begin with a letter. Which, of course, I should know. I must've hit my head or something. It's a fairly marginal advantage, though, if you ask me. I agree. // Kalle Räisänen. -- We have become so accustomed to our illusions that we mistake them for reality. We demand them. And we demand that there always be more of them, bigger and better and more vivid. -- Daniel Boorstin, The Image. ** 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] XHTML Strict
[EMAIL PROTECTED] Surely any conforming user agent should ignore any markup that it does not understand, so is there really any need to stop using name, where it is being used for 'belt and braces' compatibility? For XHTML 1.0 (even strict), using name is still fine. Deprecated, yes, but not invalid. For XHTML 1.1, though, it would be silly to aim for compatibility, as then the question would arise: if you're after compatibility, why move to 1.1? Patrick Patrick H. Lauke Web Editor / University of Salford http://www.salford.ac.uk Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Dave shea enhancement
Hi folks I was wondering if anyone can help me. I am using the Dave Shea enhancement to allow for valid H2 text to be visible to the screenreader whilst maintaining the graphic for the client. One of the things the client wants now is the heading to be a link. I have styled this and all seems to be working but now this does not validate the page on the W3C validator. Does anyone have some sample code using this method and a link surrounding the image that validates? Cheers Ben --- Sent via BlackBerry Ben Logan Director Spotless Design http://www.spotlessdesign.com Tel: +44 (0) 207 168 7526 Fax: +44 (0) 207 681 4375 Mob: +44 (0) 7971 002292 MSN ID: [EMAIL PROTECTED] Skype: spotlessdesign AOL IM: DJBenLogan ** 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] XHTML Strict
On Wed, 7 Jun 2006 06:48 pm, [EMAIL PROTECTED] wrote: Surely any conforming user agent should ignore any markup that it does No, user agents don't ignore markup that is not specified in the DOCTYPE. It generates (or should) a parse error. Most web sites don't serve XHTML correctly as application/xhtml+xml because one browser by a very large US software manufacturer doesn't parse this MIME type. If you want to see examples try: http://www.bathurst-tafe.nsw.edu.au/~steve/index.htm is text/html and http://www.bathurst-tafe.nsw.edu.au/~steve/index.xhtml is application/xhtml+xml When using Windows IE6, for the second link, Windows will try to open the page in another application (usually Dreamweaver if installed). These are both served by Apache from the same directory. -- Regards, Steve Bathurst Computer Solutions URL: www.bathurstcomputers.com.au e-mail: [EMAIL PROTECTED] Mobile: 0407 224 251 _ ... (0) ... / / \ .. / / . ) .. V_/_ Linux Powered! ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] More on printing
Dear listers, Is there anyone out there with experience of avoiding page breaks in daft places? I have a site with the potential to print out some thirty different pages, with each printout length between 1 page and 4. Each page has small illustrations scattered unevenly amongst the text, and I'm finding that some pages attempt a page break half way through an image, with the result that the image splits into two across the pages. Because all the pages are different (and change, too!) I am trying to give universal instructions in the print style sheet. (if image then page-break, but only at the bottom of a page :-). Most users of the site will be using IE, so I'm guessing that @page definitions will be useless? The pages are the same ones I referred to recently in another printing context and an example can be seen at : http://www.rhh.myzen.co.uk/rhh/locations/trevone/tregarne.php?house=Tregarne , though I doubt this is really relevant. I'd be grateful for any help on this. Thanks -- Best Regards, Bob McClelland Cornwall (UK) www.gwelanmor-internet.co.uk ** 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] Through PDA
It might be better to hide the crippled handheld css file from this browserI believe Opera ignores the handheld stylesheet anyway.I devides a neat technique for detecting a small screen device if anyone's interested. Here's the article:
http://theletter.co.uk/longhand?id=1918#device_detectionCheers,BlairOn 06/06/06,
Ted Drake [EMAIL PROTECTED] wrote:
Mobile appliances are notoriously difficult to program for. Cell phone andPDA manufacturers are still stuck in the Wild West days of browser wars. Youjust have to do the best you can and hope the majority of people can view
your stuff.I'm not on the Yahoo! mobile project, but from what I understand they areusing XSL to create customized presentations for each of the major mobileapplications.This is a huge undertaking that the average developer simply
cannot afford.I'm used the handheld media to create a simplified style sheet. I'm hardlyan expert at it, but have gotten moderate success. Take your print stylesheet, add a rule that cancels float on everything
(* {float:none!important}) and start tweaking with what you want to show andhide.This is just a very, very rough draft for a mobile style sheet. It'snot perfect, but it will make your sites more readable in an appliance that
recognizes the handheld media.That said... The opera browser for mobile appliances is really quite niceand can re-render your normal site fairly well. It might be better to hidethe crippled handheld css file from this browser.
Tedwww.tdrake.net-Original Message-From: listdad@webstandardsgroup.org [mailto:
listdad@webstandardsgroup.org]On Behalf Of Leskinen N.Sent: Tuesday, June 06, 2006 9:57 AMTo: wsg@webstandardsgroup.orgSubject: [WSG] Through PDAYesterday I have connected PDA to the Internet and have looked as sites
under web-standards are well looked.http://whale-zx.livejournal.com/8498.htmlNot so well...--Kit
http://www.zamyteam.com/**The discussion list forhttp://webstandardsgroup.org/ See
http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help
The discussion list forhttp://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting helpThe discussion list for
http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help
**-- Blair Millenhttp://theletter.co.uk
http://doepud.co.uk
**The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help**
[WSG]
UNSUBSCRIBE THE LIST DISCUSSION _ Un amor, una aventura, compañía para un viaje. Regístrate gratis en MSN Amor Amistad. http://match.msn.es/match/mt.cfm?pg=channeltcid=162349 ** 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] Through PDA
I believe Opera ignores the handheld stylesheet anyway. Nope. Opera, NetFront and S60Browser are almost the only ones treating screen/handheld stylesheets right. -- Jan Brasna :: www.alphanumeric.cz | www.janbrasna.com | www.wdnews.net ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG]
UNSUBSCRIBE DISCUSSION LIST _ Descarga gratis la Barra de Herramientas de MSN http://www.msn.es/usuario/busqueda/barra?XAPID=2031DI=1055SU=http%3A//www.hotmail.comHL=LINKTAG1OPENINGTEXT_MSNBH ** 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] Through PDA
I think that the simple way to make nice PDA-site -- make the separate version for PDA, because for PDA the superfluous information is not necessary so much then for PC Design in simplicity ;) ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] Microformats and XOXO
So I've been looking into this whole microformats thing. I'm excited (to say the very least!) I've looked over the hCard, hCalendar and xfn overviews. They're relatively straightforward...but then I looked at the XOXO spec and was completely snowed... Can anyone help explain in relatively plain English (maybe with an example or two) what the XOXO microformat is and how is could be implemented? I know this is a sudo-standard but I'm sure it's way more on topic that some of the stuff floating around this list atm. 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] More on printing
On Wed, 07 Jun 2006 13:05:35 +0100, Designer wrote: [...] I have a site with the potential to print out some thirty different pages, with each printout length between 1 page and 4. Each page has small illustrations scattered unevenly amongst the text, and I'm finding that some pages attempt a page break half way through an image, with the result that the image splits into two across the pages. Try adding float: none to the images in your print style sheet. I find this usually fixes the problem, but can't be certain as you don't say which browser you use. No need to un-float all of them - just the ones that give problems. (Bearing in mind that not everyone prints on size A4 in portrait mode.) Cordially, David -- David Hucklesby, on 6/7/2006 http://www.hucklesby.com/ -- ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
