Re: [WSG] RE: Poetry needing block format but with line-breaks
On Tue, Feb 16, 2010 at 10:54 PM, Susie Gardner-Brown susi...@uq.edu.auwrote: Oh, thanks Jens – I forgot about that option!! I’ll give it a go . And Brad – yes I am using the br / tag, but that stops it being block-formatted ... I did some work for a poetry trust recently, and I set up two different templates for displaying poems. One allowed for line breaks (so lines would break correctly), and the other one used pre to preserve formatting for poems where the shape of the text was important. - Matthew *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] Invitation to connect on LinkedIn
LinkedIn Srecko Micic requested to add you as a connection on LinkedIn: -- Nick, I'd like to add you to my professional network on LinkedIn. - Srecko Accept invitation from Srecko Micic http://www.linkedin.com/e/7L1XvhOEro1RJ5LtYH3XHbryRcefSR7tSTTS06J/blk/I1819147079_2/1BpC5vrmRLoRZcjkkZt5YCpnlOt3RApnhMpmdzgmhxrSNBszYOnPATc3sQcjANe359bQV8mzp1rDgJbPgTdjANdP0Uc34LrCBxbOYWrSlI/EML_comm_afe/ View invitation from Srecko Micic http://www.linkedin.com/e/7L1XvhOEro1RJ5LtYH3XHbryRcefSR7tSTTS06J/blk/I1819147079_2/39vejsMdPgNej4UckALqnpPbOYWrSlI/svi/ -- DID YOU KNOW that LinkedIn can find the answers to your most difficult questions? Post those vexing questions on LinkedIn Answers to tap into the knowledge of the world's foremost business experts: http://www.linkedin.com/e/ask/inv-23/ -- (c) 2010, LinkedIn Corporation *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Print style sheet
On 17 February 2010 03:42, c...@fagandesign.com.au wrote:
Hi all,
Just wondering about best practice, accessibility and practical
implementation of a print stylesheet.
I have been asked to place a different header image in my HTML templates
specifically for print (only shows when printed and replaces usual header).
I would like to know if this is deemed acceptable use of CSSAND if a
hard-coded image has to be downloaded on page load or page print??
eg.
div id=print-header style=display:none;
img src=img/elements/print-header.jpg alt=blah blah width=600
height=254 /
/div
div id=header
img src=img/elements/normal-header.jpg alt=blah blah width=800
height=300 /
/div
!-- PRINT STYLESHEET --
.print-header {display:block!important}
This duplication of content is unnecessary and would be rather
difficult to maintain in the long term.
.The issue has been dealt with in http://www.w3.org/TR/CSS2/media.html..
Use one element id in a document for one element e.g.
div id=header
and then define it differently for different media as per examples in
that link.n
@media print {
#header { font-size: 10pt }
}
@media screen {
#header { font-size: 13px }
}
@media screen, print {
#header { line-height: 1.2 }
}
This method achieves independence of data (web page content) from
design/style (whether it is screen, print or other media type).
HTH
Lesley
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
Re: [WSG] Progressive Enhancement related article
YES! THanks SO much! Sorry Mr. Clarke ;-) On Tue, Feb 16, 2010 at 6:12 PM, Simon Wilder simon.wil...@gmail.com wrote: http://24ways.org/2009/ignorance-is-bliss is that article. Was by Andy Clarke for 24ways. I hope this was the one you were after. On 16 Feb 2010, at 21:29, Tom Livingston tom...@gmail.com wrote: List, I recently came across an article - possibly by Roger Johansson - where in the article the author discussed a web page design that was shown to 2 different people from the same client but in different locations. Based on the browser being used, they each received a different experience but each loved what they saw, not knowing each saw a slightly different experience. It may have been a fictitious scenario. Not sure. Does this ring a bell with anyone? I am going nuts trying to track it back down. It was one of those link-in-an-article-that-was-a-link-from-another-article kinda things and I unfortunately didn't bookmark it. If you know of this article, please forward a link - OFF LIST. Thanks a bunch, if you spend any time on this. I appreciate it. -- -- Tom Livingston | Senior Interactive Developer | Media Logic | ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
Re: [WSG] Minimal forms or marking up a search field
A practical distraction for the standardistas and accessibility gurus�
Hoping tap your brain for an alternative perspective on the simple and
common HTML scenario of a site search form.
...
To revisit this topic, I'm considering the
following and would appreciate feedback:
_
a) Submit button as label:
form ...
div
input type=text id=search name=search /
label for=search
input type=submit value=Search /
/label
/div
/form
_
b) Label hidden from view:
form ...
div
label for=search id=search-labelSearch:/label
input type=text id=search name=search /
input type=submit value=Search /
/div
/form
label#search-label
{
position: absolute;
left: -1000em;
}
_
The rationale for both of these is that the
Search submit button serves as a clear and
unambiguous label for the input field. In listing
a) the button is literally the label; in b) there
is a separate literal label present in the markup
but hidden from cosmetic view.
Both validate for W3C HTML Cynthia 528 Accessibilty.
Can you see any problems with them?
I favor a) but it feels edgy.
Regards,
Paul
__
Paul Novitski
Juniper Webcraft Ltd.
http://juniperwebcraft.com
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
Re: [WSG] Minimal forms or marking up a search field
On 17 Feb 2010, at 19:24, Paul Novitski wrote: To revisit this topic, I'm considering the following and would appreciate feedback: a) Submit button as label: b) Label hidden from view: Neither The label element is not used for the following because labels for these elements are provided via the value attribute (for Submit and Reset buttons), the alt attribute (for image buttons), or element content itself (button). — http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-TECHS/H44.html -- David Dorward http://dorward.me.uk *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
RE: [WSG] Print style sheet [SEC=UNCLASSIFIED]
You seem to be on the right track, Oliver.
Matthew's response regarding targeting media types is also helpful. One of the
implementations I've used before is described below.
Note that:
- The print-only version of the logo is the near-last element in the page. I
assume that someone will read all (or most) of the document before printing,
giving the browser time to download the print-only [hidden] inline image.
- Both images are requested at page load, not at page print
- Background image printing is unlikely to be enabled by default on a user's
browser, hence the use of inline images
- When printing, the screen version of the logo is entirely hidden, and the
print logo is positioned absolutely on the top left of the page.
- ContentWrapper is given a top margin related to the height of the printable
logo (preventing nasty overlaps)
- Both images are downloaded in the same page request.
- I do not regard this as a duplication of content - a print-optimised version
of a logo may have very different requirements from a screen-optimised version
of a logo.
- Similar approaches should work for other @media types
- CSS-less browsers will expose both versions of the logo - one at the top of
the page, one at the bottom (not a deal breaker, IMO).
Markup:
==
html
head
...
link type=text/css rel=stylesheet media=print href=print.css/
link type=text/css rel=stylesheet media=screen href=screen.css/
/head
...
img id=headerLogo ... /
div id=contentWrapper
...
/div
...
img id=printLogo height=80px width=120px .../
...
/body
/html
print.css
==
...
#printLogo {
position: absolute;
left: 0;
top: 0;
}
#headerLogo {
display: none;
}
screen.css
==
...
#printLogo {
display:none;
}
#contentWrapper {
margin-top: 80px;
}
Good luck!
- Gordon
I have been asked to place a different header image in my HTML templates
specifically for print (only shows when printed and replaces usual header).
I would like to know if this is deemed acceptable use of CSSAND if a
hard-coded image has to be downloaded on page load or page print??
eg.
div id=print-header style=display:none;
img src=img/elements/print-header.jpg alt=blah blah width=600
height=254 /
/div
div id=header
img src=img/elements/normal-header.jpg alt=blah blah width=800
height=300 /
/div
!-- PRINT STYLESHEET --
.print-header {display:block!important}
This duplication of content is unnecessary and would be rather
difficult to maintain in the long term.
.The issue has been dealt with in http://www.w3.org/TR/CSS2/media.html..
Use one element id in a document for one element e.g.
div id=header
and then define it differently for different media as per examples in
that link.n
@media print {
#header { font-size: 10pt }
}
@media screen {
#header { font-size: 13px }
}
@media screen, print {
#header { line-height: 1.2 }
}
This method achieves independence of data (web page content) from
design/style (whether it is screen, print or other media type).
HTH
Lesley
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
Finance Australian Business Number (ABN): 61 970 632 495
Finance Web Site: www.finance.gov.au
IMPORTANT:
This transmission is intended only for the use of the addressee and may contain
confidential or legally privileged information. If you are not the intended
recipient, you are notified that any use or dissemination of this communication
is strictly prohibited.
If you have received this transmission in error, please notify us immediately
by telephone on 61-2-6215- and delete all copies of this transmission
together with any attachments.
If responding to this email, please send to the appropriate person using the
suffix .gov.au.
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
