[WSG] XSLT/XPATH doc-available problem
Hi, I'm using XSLT2 and having a problem with the doc-available function. I have an href attribute (@href) whose value is 'wiki.xml' resolve-uri(@href,'file:/c:/clipsworkingdir/rss/temp/') returns file:/c:/clipsworkingdir/rss/temp/wiki.xml (this file exists and is valid XML). resolve-uri(@href,document-uri(/)) returns file:/c:/CLIPSW~1/rss/temp/wiki.xml doc-available(file:/c:/clipsworkingdir/rss/temp/wiki.xml) returns false doc-available(file:/c:/CLIPSW~1/rss/temp/wiki.xml) returns false doc-available(resolve-uri(@href,document-uri(/))) returns false document(file:/c:/clipsworkingdir/rss/temp/wiki.xml) returns nothing indicating it silently fails document(resolve-uri(@href,document-uri(/)))returns nothing indicating it silently fails Does anyone know what could be going wrong? Grant Focas ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ***
[WSG] XSLT: looping through ancestors looking for a specific node
Hi, Is there a way in XSLT to loop through the ancestors until I find the first instance of a node called foo? For context what I'm trying to do is see if a bookmark is in the same section as the link/@href (and to find this out when I'm processing the link). Grant Focas ** Example XML: ?xml version=1.0 encoding=utf-8? content titleInline links across sections/title section titleHeading 1title paragraphHere is a link href=#myPopupBookmark type=internalparagraphlink/paragraph/link to a in the popup below/paragraph paragraphHere is a link href=#myNestedSectionBookmark type=internalparagraphlink/paragraph/link to a bookmark in a nested section/paragraph section titleMy popup sectiontitle heading level=1My Heading 1heading paragraphbookmark id=myPopupBookmark/This is the line with a bookmark/paragraph /section /section section titleInline Link across nested sections/title section visible=true display=popup titleMy popup sectiontitle heading level=1Heading 1 in Popup/heading section visible=true display=newWindow titleA new window in a popup/title heading level=1Heading 1 in my new window/heading paragraphHere is a line with a book mark on itbookmark id=myNestedSectionBookmark//paragraph /section /section /section /content ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Javascript Code not working in IE6
IE does not support the W3C addEventListener, it uses attacheEvent so
you need a cross-browser way to attach events. Here's one:
function attachEventListener(target, eventType, functionRef, capture){
// function can be called with a pointer or a string representing
a function name
if (typeof(functionRef)== 'string') {
functionRef=eval(functionRef);
}
if (typeof target.addEventListener != undefined){
target.addEventListener(eventType, functionRef, capture);
} else if (typeof target.attachEvent != undefined){
target.attachEvent(on + eventType, functionRef);
} else {
eventType = on + eventType;
if(typeof target[eventType] == function){
var oldListener = target[eventType];
target[eventType] = function(){
oldListener();
return functionRef();
};
}else{
target[eventType] = functionRef;
}
}
}
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Alexander Uribe
Sent: Wednesday, 24 October 2007 10:09 AM
To: wsg@webstandardsgroup.org
Subject: [WSG] Javascript Code not working in IE6
In my javascript class at college, I have to find out why this piece of
code does not run in IE6.
I can't seem to figure out why.
If anyone knows, that would be great
cheers,
Alex.
Code below
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN
http://www.w3.org/TR/html4/strict.dtd;
html
head
titleExercise 4/title
meta http-equiv=Content-Type content=text/html; charset=utf-8
style type=text/css
.borders {
border: 1px solid red;
width: 150px;
}
.li_borders {
background: yellow;
border: 1px solid blue;
color: red;
}
.li2_borders {
background: blue;
color: white;
}
#ul2 {
xwidth: 150px;
}
#ul2 li {
border-color: silver;
border-style: solid;
border-width: 1px 1px 0px 1px;
display: inline;
font-weight:bold;
margin: 0;
padding: 0 4px;
}
/style
script type=text/javascript
window.onload = init;
function init()
{
var liArr = new Array();
var idx;
//--- process first UL block
var id = document.getElementById(ul1);
id.addEventListener(mouseover, ul1on, false);
id.addEventListener(mouseout, ul1off, false);
liArr = id.getElementsByTagName(li);
for(idx=0; idxliArr.length; idx++ ) {
liArr[idx].addEventListener(click, li_s, false);
liArr[idx].addEventListener(mouseover, li_on, false);
liArr[idx].addEventListener(mouseout, li_off, false);
}
//--- process second UL block
id = document.getElementById(ul2);
liArr = id.getElementsByTagName(li);
for(idx=0; idxliArr.length; idx++ ) {
liArr[idx].addEventListener(click, li_s, false);
liArr[idx].addEventListener(mouseover, li2_on, false);
liArr[idx].addEventListener(mouseout, li2_off, false);
}
}
function ul1on() { document.getElementById(ul1).className=borders;}
function ul1off(){ document.getElementById(ul1).className=;}
function li_s() { alert(this.innerHTML); }
function li_on() {
document.getElementById(this.id).className=li_borders;}
function li_off(){ document.getElementById(this.id).className=;}
function li2_on() {
document.getElementById(this.id).className=li2_borders;}
function li2_off(){ document.getElementById(this.id).className=;}
/script
/head
body
pThis doesn't work in Internet Explorer 6. Why and whats the
solution?/p
ul id=ul1
li id=li11item 1/li
li id=li12item 2/li
li id=li13item 3 /li
/ul
ul id=ul2
li id=li21item 1/li
li id=li22item 2/li
li id=li23item 3 /li
/ul
/body
/html
Join Lavalife for free. What are you waiting for?
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Flavalife9%2Eninemsn%2Ec
om%2Eau%2Fclickthru%2Fclickthru%2Eact%3Fid%3Dninemsn%26context%3Dan99%26
locale%3Den%5FAU%26a%3D30288_t=764581033_r=email_taglines_Join_free_OC
T07_m=EXT
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
RE: [WSG] cool FAQ page [follow up]
It's very nice Thierry. IE/Mac cannot access it via keyboard though. The only way I see around it is: a) Ignore IE/Mac as it's now officially unsupported b) Add an onkeypress event, check for enter key, do stuff. Messy. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thierry Koblentz Sent: Friday, 3 February 2006 03:23 To: wsg@webstandardsgroup.org Subject: [WSG] cool FAQ page [follow up] Following a bug report (not in the script, but in a browser), I have made a few changes to the original solution; it now uses images and seems to work in everything but Opera 6.05. http://www.tjkdesign.com/articles/toggle_elements.asp Regards, Thierry | www.TJKDesign.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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] [Fixed div elements] - Having troubles with IE
Andrew, You could also look at this - the code explains what's happening. http://www.homebass.info/fixedPosTest/ Grant That is exactly what am I talking about. I applaud your skill, but not your memory :) I am trying to pick away at your css to figure out how you got it working but so far I have had no luck. I will most likely create a new page away from the code I have no to see if I can just get it working. Thanks for pointing me in some direction! -Andrew Brown -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bert Doorn Sent: February 1, 2006 2:16 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] [Fixed div elements] - Having troubles with IE G'day Andrew Brown wrote: I changed the doctype to strict locally and still the scrollbar does appear. I also already have those additional tags added. Do you know of a website that has enough content that scrolls and has div banners such as mine only done in css? I cannot say I have saw many that do. I am still on top of this. Kinda like www.sure-kleen.com ? Don't ask me how I did it - I forgot. But if it does what you want, feel free to reverse-engineer. Regards -- Bert Doorn, Better Web Design http://www.betterwebdesign.com.au/ Fast-loading, user-friendly websites ** 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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Safari frameset link tabbing bug
Hi, Id like to alert people to a bug I have found in Safari (1.2 and 2.0 and maybe more thats all I have access to). When using framesets (I know we have a good reason that we have to use them OK?) and navigating by keyboard: The first link in a frame is skipped if both frames have links. An example - http://www.meridian-records.co.uk/recmd.html . After the link Z the focus goes to the second link in the next frame Adar. You can go back to the first by using shift tab but its not intuitive. If there are 3 frames with one link in each an example is http://cita.rehab.uiuc.edu/wai-eval/frames/frame-test.html - the focus skips from frame 1 to frame 3 and frame 2 cannot be accessed via keyboard even with shift-tab. Grant Focas **This message is intended for the addressee named and may containprivileged information or confidential information or both. If youare not the intended recipient please delete it and notify the sender.**
[WSG] WCAG1.0 guideline 8.1
Hi, Im wondering if anyone has any thoughts regarding WCAG1.0 Guideline 8.1: Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority1 if functionality is important and not presented elsewhere, otherwise Priority2.] My thoughts are that it is redundant because you simply should not put important functionality that is not presented elsewhere in a script or applet. In fact Guideline 6.3 says this (although usable may mean different things to different people): 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority1] Grant Focas **This message is intended for the addressee named and may containprivileged information or confidential information or both. If youare not the intended recipient please delete it and notify the sender.**
RE: [WSG] Can't select text on IE
Title: Message Id say selecting text is a usability/accessibility issue. Grant From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Noone Sent: Wednesday, 16 November 2005 03:55 To: wsg@webstandardsgroup.org Subject: RE: [WSG] Can't select text on IE Or...View Source and copy. Assuming that's an option. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CHAUDHRY, Bhuvnesh Sent: Wednesday, 16 November 2005 3:48 PM To: wsg@webstandardsgroup.org Subject: RE: [WSG] Can't select text on IE Paul, It a simplecopy and paste requirement. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Noone Sent: Wednesday, 16 November 2005 15:39 To: wsg@webstandardsgroup.org Subject: RE: [WSG] Can't select text on IE Why do you want to select the text? This might go some way towards providing an adequate solution that doesn't involve totally overhauling your stylsheet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CHAUDHRY, Bhuvnesh Sent: Wednesday, 16 November 2005 3:03 PM To: wsg@webstandardsgroup.org Subject: [WSG] Can't select text on IE Importance: High Hi, I have written an html page based on CSS layout. The page has a parent div tag which contains many other div tags including one for Side Menu, one for Masthead and one for the Content. The problem: Using IE6, I am unable to select a part of the text from the content area. When I try to select a para or a line, all the text on the page within the parent div tag including the side menu bar get selected. Does anyone have any suggestions about this problem ? Thanks __ Bhuvnesh Chaudhry * This e-mail message (along with any attachments) is intended only for the named addressee and could contain information that is confidential or privileged. If you are not the intended recipient you are notified that any dissemination, copying or use of any of the information is prohibited. Please notify us immediately by return e-mail if you are not the intended recipient and delete all copies of the original message and attachments. This footnote also confirms that this message has been checked for computer viruses. * * This e-mail message (along with any attachments) is intended only for the named addressee and could contain information that is confidential or privileged. If you are not the intended recipient you are notified that any dissemination, copying or use of any of the information is prohibited. Please notify us immediately by return e-mail if you are not the intended recipient and delete all copies of the original message and attachments. This footnote also confirms that this message has been checked for computer viruses. * **This message is intended for the addressee named and may containprivileged information or confidential information or both. If youare not the intended recipient please delete it and notify the sender.**
RE: [WSG] Can't select text on IE
Title: Can't select text on IE IE has a bug where you cant select text in your content area if it is positioned absolutely. Try relative positioning and use margins. Grant From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of CHAUDHRY, Bhuvnesh Sent: Wednesday, 16 November 2005 03:03 To: wsg@webstandardsgroup.org Subject: [WSG] Can't select text on IE Importance: High Hi, I have written an html page based on CSS layout. The page has a parent div tag which contains many other div tags including one for Side Menu, one for Masthead and one for the Content. The problem: Using IE6, I am unable to select a part of the text from the content area. When I try to select a para or a line, all the text on the page within the parent div tag including the side menu bar get selected. Does anyone have any suggestions about this problem ? Thanks __ Bhuvnesh Chaudhry * This e-mail message (along with any attachments) is intended only for the named addressee and could contain information that is confidential or privileged. If you are not the intended recipient you are notified that any dissemination, copying or use of any of the information is prohibited. Please notify us immediately by return e-mail if you are not the intended recipient and delete all copies of the original message and attachments. This footnote also confirms that this message has been checked for computer viruses. * **This message is intended for the addressee named and may containprivileged information or confidential information or both. If youare not the intended recipient please delete it and notify the sender.**
RE: [WSG] Visited links
Have you checked that you have the pseudo classes in the right order in the CSS? See http://www.w3schools.com/css/css_pseudo_classes.asp Grant On Fri, 11 Nov 2005 19:18:18 +1030, Tim Burgan wrote: Do you have any suggestions as to how to overcome this? ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Firefox onblur and onfocus event bubbling bug
Hi standardistas, Ive had a problem with onfocus and onblur where Firefox is calling onblur before onfocus when clicking on an input element. This is a bug (https://bugzilla.mozilla.org/show_bug.cgi?id=53118 ) because it goes against the DOM2 Event handling spec. The only way around it at the moment seems to be to check whether youre running on Gecko via client sniffing and insert a conditional code fork in your _javascript_ so [] you explicitly preventBubbles on the event that really shoulndt bubble in the first place. (from the page referred to above). Just thought Id let those of you unaware of this issue know so you dont have to suffer the same frustration Ive had trying to figure out whats happened. Anyone with Firefox 1.5 beta know if this issue is fixed in that version? Heres my test: HTML: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN html head titleonblur test/title /head body input name=test type=text id=test called'); called'); called'); called'); / /body /html IE6 using a mouse to click into the textbox alerts onfocus called using a mouse to click outside the textbox alerts onblur called keyboard tabbing to the textbox alerts onfocus called keyboard tabbing out of the textbox alerts onblur called, followed by onkeydown called followed by onfocus called followed by onblur Firefox 1.07 using a mouse to click into the textbox alerts onblur called followed by onfocus called using a mouse to click outside the textbox alerts onblur called keyboard tabbing to the textbox alerts onblur called followed by onfocus called keyboard tabbing out of the textbox alerts onblur called, followed by onkeydown called Grant Focas **This message is intended for the addressee named and may containprivileged information or confidential information or both. If youare not the intended recipient please delete it and notify the sender.**
[WSG] disabling autocomplete and validation
Hi, Im trying to implement a similar thing to Google suggest but have found that the browsers default autocomplete gets in the way. The only way Ive found to override this is to use the non-standard autocomplete=off attribute of the input element. This can be added by _javascript_ after loading to keep the validators happy (see http://_javascript_.weblogsinc.com/entry/1234000130021541/ ) But is there any good reason to trick the validators other than the gold stamp on the back on the hand and the warm inner glow of knowing youve passed (by cheating)? Alternatively does anyone know of a method to disable the autocomplete in a standards-based way? Thanks, Grant **This message is intended for the addressee named and may containprivileged information or confidential information or both. If youare not the intended recipient please delete it and notify the sender.**
RE: [WSG] disabling autocomplete and validation
Terrance Wood said: Manipulating an attribute with javascript (even a non-standard one) so it doesn't interfere with your other javascript functionality sounds like the ideal solution to me. Yes, but what purpose - if any - is served by hiding a non-html standard attribute. It's still there isn't it? I suspect there may be a reason to do this beyond the warm inner glow of validation. But I can't see it. At the moment it feels like merely tricking the validator in order to fudge a validation. Grant ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Keep all content to a single page using CSS for printing?
Is it possible to keep all content to a single page using CSS for printing? Not to my knowledge. You can maximise the chances of it happening by setting the font-size, padding, margins (margins can be negative) and line-height of elements. But ultimately the amount of content in a page will determine the amount of paper needed. Readability and browser differences when printing should also be taken into consideration. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Smales Sent: Wednesday, 12 October 2005 12:32 To: wsg@webstandardsgroup.org Subject: [WSG] Keep all content to a single page using CSS for printing? Hi standardistas, Is it possible to keep all content to a single page using CSS for printing? I have a client that made it a requirement. The client is fairly pedantic. Regards, Martin ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Meta Keywords?
I'd also add that for semantics we should be using them - so what if search engines choose to use/not use/change they way they handle them. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andreas Boehmer [Addictive Media] Sent: Friday, 7 October 2005 2:59 PM To: wsg@webstandardsgroup.org Subject: RE: [WSG] Meta Keywords? I would advise anybody against taking Meta Tags (description and keywords) out of their sites. Although major search engines have publicly declared that they put less emphasis on the tags, there are still search engines around that read them. Google and Yahoo never really said we don't support meta tags anymore. They just say they have implemented new ways of ranking sites. We leave the meta tags in all our websites and have had extremely good results with our rankings. Of course other factors (such as cross linking and page content) play a huge role in the ranking as well. BTW, even if search engines didn't put emphasis on the Meta tags, they still display the Meta Description in their search results (at least Google does). So if it's not for improving your ranking, at least put a meta description onto your site for the sake of informing people in a short sentence what your site is all about. ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] WE05 - who's going?
I'm going, see you there. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Webmaster Sent: Tuesday, 27 September 2005 2:19 PM To: wsg@webstandardsgroup.org Subject: [WSG] WE05 - who's going? So who's going to the Web Essnetials conference this week? Anyone interested in a group catch-up? I thought it might be nice to put some faces to all these names. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] WE05 - who's going?
Ok, this is me, http://we04.com/gallery/index.cfm?imgid=dsc_0044 see you there, Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andrew Krespanis Sent: Tuesday, 27 September 2005 3:28 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] WE05 - who's going? How about a secret password that you have to sneak into the first 60 seconds of meeting someone :)..? Or how about everyone interested just bites the bullet and posts their photo contact details like I just did? This secret handshake/signalling in crowded room nonsense isn't going to work. We either need know who we're looking for or decide on a place and time to meet up. -Andrew :) N.ȨX+i nZ֫v+hym쵩jl.f.ץwq(b(,)උazX)i ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** N���.�Ȩ�X���+��i�� n�Z�֫v�+��h��y�m�쵩�j�l��.f���.�ץ�w�q(��b��(��,�)උazX����)��
RE: [WSG] keyboard onclick activation on Mac
Thanks for the help,
My solution has been to change:
a href=# onclick=if(!window.print){alert('Your browser does not
support this feature.Please select print from the file
menu')}else{window.print()};return false;Print/a
to this:
HTML:
a href=# onclick=printPage(); onkeypress=return
handleEnter(event); class=topNavPrint/a
JAVASCRIPT:
function handleEnter(ev) {
var ENTER_KEY=13;
var keyCode = ev.keyCode ? ev.keyCode : ev.which ? ev.which :
ev.charCode;
if (keyCode == ENTER_KEY) {
printPage();
return false;
}
}
function printPage(){
window.print?window.print(): alert('Sorry, your browser does not
support this feature. Please choose print from the file menu.');
}
This now works in Mac IE5.0,5.1,5.2 but Safari 1.0.3 and Mac Netscape
7.2 still do not even allow keyboard tabbing.
Grant
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Webmaster
Sent: Thursday, 22 September 2005 9:49 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] keyboard onclick activation on Mac
Patrick H. Lauke quoth:
Or, if you must, and your audience does include Mac users, write your
own
little javascript filter function to ignore TAB before activating
whatever
behaviour is in the onclick.
And indeed one for the Enter key.
I guess the point I was trying ot make is that these keys already had
specific amnd well understood functions well before the Internet
infected
the ether.
It shouldn't have been a leap of thought to reserve them for exclusive
functions. As you say, the W3C got it wrong. Nuff said.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**
**
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] keyboard onclick activation on Mac
Hi,
Can anyone enlighten me about keyboard onclick activation problems on Mac?
I have found problems when I have a link such as this:
a href=# onclick=if(!window.print){alert('Your browser does not support
this feature.Please select print from the file
menu')}else{window.print()};return false;Print/a
Mac IE 5.2 - can tab to the link but pressing return does nothing
Mac IE5.1 - can tab to the link but pressing return does nothing
Safari 1.0.3 - cannot even tab to the links
Safari 2.0 - works
Netscape 6.2 - works
Netscape 7.0 - works
Netscape 7.2 - cannot even tab to the links
Firefox 1.0.6 - works
On Windows all browsers I have tested work fine.
*
thanks in advance!
Grant
**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**
**
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] Accessibility, the possibilities
In my opinion WatchfireXM is a terrible product - it considers perfectly valid things to be problems, has misleading documentation and is not very intuitive. DreamweaverMX has a good but not completely thorough accessibility checking feature. Online tools will only check one page at a time. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Geoff Deering Sent: Wednesday, 24 August 2005 5:02 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Accessibility, the possibilities Stuart Sherwood wrote: Are any of the validation tools: Bobby, Cynthiasays, Watchfire...more respected then the others? Regards, Stuart. You can use any of these, and all of them, but you should combine them with your own knowledge base and common sense. I also use Marc Gueury's HTML Validator(http://users.skynet.be/mgueury/mozilla/). There's no tool that I trust explicitly, but if you arm yourself with some basic knowledge, then even if a tool has it's short falls or faults, and you are aware of them, you can still use what it renders correctly to assist you. Tabindex: one piece of advice, if you code tabindex, don't use intervals of 1, use something like 10, 20 or even 50; tabindex=10 tabindex=20 tabindex=50 whatever. If you have to go back and change the order or add items, it's a pain in the arse if you have to change every tabindex in the document. Tabs will naturally flow to the next highest value, it doesn't matter if the interval is 10 or 100, whatever, this allows you to insert other items later on, without having to edit the rest of the document. What I usually do is break the document down into sections, and within the section increase at intervals of 10, but when I go to a new section, jump either one hundred or even a few hundred, even a thousand. Gives breathing space... phew. But in general, if the document is well structure, and still reflects that structure when styles are turn off, the tab flow is often the same with or without coding tabindex. If that is the case, why bother coding tabindex (I realise there are exceptions like using an initial tab to set the focus/skip navigation)? --- Geoff ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Firefox MAC OSX checkbox keyboard tabbing problem
Hi, I've discovered a problem with Firefox and checkboxes and want to see if anyone elses experience is the same. I'm using Firefox 1.06 on Mac OSX 10.2.8 (though it also occurs in Firefox 1.04) and cannot use a keyboard to navigate to a checkbox. Two example pages where it does not work are: http://www.quirksmode.org/js/formex.html http://www.w3.org/WAI/UA/TS/html401/cp0101/0101-ACCESSKEY-CHECKBOX.html It is working fine on Firefox on PC. Notice that in the first page the radio buttons, select, submit and reset also will not recieve focus. Grant Focas ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Firefox MAC OSX checkbox keyboard tabbing problem - ANSWER (of sorts)
Hi, thanks for the replies Ben and Terrence. I found that the System Preferences did nothing. I've checked 3 Mac OSX machines here, 2 are 10.2.8 and one is 10.3.2. The 10.2.8 machines had 'Turn on full Keyboard access' off by default. The 10.3.2 had it turned on by default. Even when I changed it to on for the first 2, it made no difference ( I also tried changing the 'For Windows and dialogs, highlight' option from 'Text boxes and lists only' to 'any control' - this made no difference). Even after restarting browsers and then the machines. The other thing i discovered is that Safari is acting the same as Firefox - on both systems (unable to tab to a checkbox, radiobox, select,reset or submit input). What did work was changing the config in Firefox (by typing in about:config, then changing the accessibility:tabfocus value from its default OSX setting of 1 - 'Text field form controls only' to 7 'All form controls and hyperlinks'). Thanks for the url Terrence. The only unresolved issues are: a) why did the systems preference settings seemingly make no difference b) why is Safari still unable to tab to anything but text field form controls. Is there a Safari version of 'about:config' ? cheers, Grant Ben wrote: Mac OSX has a system preference for 'Enable full keyboard access' which in Safari at least is responsible for controlling whether you can access form controls with the keyboard. Switching it on allows you to do it. On 7/28/05, Focas, Grant [EMAIL PROTECTED] wrote: Hi, I've discovered a problem with Firefox and checkboxes and want to see if anyone elses experience is the same. I'm using Firefox 1.06 on Mac OSX 10.2.8 (though it also occurs in Firefox 1.04) and cannot use a keyboard to navigate to a checkbox. Two example pages where it does not work are: http://www.quirksmode.org/js/formex.html http://www.w3.org/WAI/UA/TS/html401/cp0101/0101-ACCESSKEY-CHECKBOX.html It is working fine on Firefox on PC. Notice that in the first page the radio buttons, select, submit and reset also will not recieve focus. Grant Focas ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Firefox MAC OSX checkbox keyboard tabbing problem - ANSWER (of sorts)
Under Safari - preferences - advanced, I only get 2 options: stylesheets and proxies. Thanks for the info on Firefox 1.5. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Philippe Wittenbergh Sent: Friday, 29 July 2005 12:38 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Firefox MAC OSX checkbox keyboard tabbing problem - ANSWER (of sorts) On 29 Jul 2005, at 9:45 am, Focas, Grant wrote: The only unresolved issues are: a) why did the systems preference settings seemingly make no difference b) why is Safari still unable to tab to anything but text field form controls. Is there a Safari version of 'about:config' ? 1/ For the upcoming Firefox 1.5, you won't need to add the pref in about:config, just make sure you check the system prefs. Firefox 1.0x and Camino 0.9a2 don't know about the system pref, and need the 'accessibility:tabfocus' setting. 2/ For Safari, open up the application prefs and under the Advanced pane, you'll see a checkbox for that purpose. Philippe --- Philippe Wittenbergh http://emps.l-c-n.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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] HR - Presentation or Structure?
I don't think anyone here is arguing for HTML to be not accessible, but I feel what Mike may be trying to point out is that visual design can be an important part of the meaning. For example, I work primarily on educational sites and we know that whitespace and the amount of words in a line are part of what determines how sighted people absorb the information and learn. The same information is available to a screen reader but the ability to absorb the information into learning is lessened - not just different but lessened. MathML is a classic example of this. It is accessible (except that for visual browsers it will only work on modern browsers) in that it can be interpreted by screen readers. However you have to be able to hold so many more concepts inside your head at one time when reading an equation through a screen reader than a visual browser. Math equations are intrinsically more suited to a visual medium. In so many ways we must ensure that our content is as accessible as possible but it is wishful thinking to assume it is equally accessible or that one medium (vision) is not favoured over another. Yes the technology (HTML) does not favour it but human practice of communication does. Grant Focas -Original Message- Subject: Re: [WSG] HR - Presentation or Structure? Mike Whitehurst wrote: what do you mean by primarily? please elaborate. To simplify, what Nathan seems to be arguing is that HTML is mainly meant to mark up documents in the tradition of print, and as such has a bias towards visual rendition in a browser to sighted users. Our argument is that HTML is more generalised than that, and was not intended to mark up content that would only be delivered visually in a browser; it was meant to mark up information so that it can be presented to the user in a variety of ways. Yes, most users are sighted and can therefore use a web browser which renders HTML as a visual document, but the same markup is also good for being read out by a screenreader, for instance. The visual representation is not inherent in HTML, it's only that it's the most common way to present HTML to the user. -- Patrick H. Lauke ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] HR - Presentation or Structure?
Damian wrote: (Essentially, a big equation can be broken down into component parts. This can make it easier for blind users to read the equation and for sighted users to understand the equation. The equation is the same, it is just constructed in a more accessible form.) It is accessible (except that for visual browsers it will only work on modern browsers) in that it can be interpreted by screen readers. It is not accessible until you realign the original material so that it is not constructed purely for the visual register. Grant replies: Well, no. MathML by its nature is not purely for the visual register. And no - we should not have to realign a complex formula if the materials merit it because what we are doing then is making the content less accessible/comprehensible for many people to allow it to be equally accessible to all. If breaking the formula up into little chunks makes comprehension harder for the vast majority of people then we should not do it and I do not agree with your assertion that breaking a complex formula will make it more understandable - it may in fact undermine the learning. In most learning materials complexity builds throughout the learning. We should be very wary of dumbing down content in the name of accessibility. Accessibility is a continuum not an absolute and we often have to make judgement calls that balance the interests of one group of people against another. Equally accessible doesn't exist. As accessible as possible is a fine aim. Grant Focas ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] detecting css display properties
Hi Steve,
What about document.getElementById('something').style.display
when there is an element with an id.
In your example you would have to use
document.getElements.ByTagName(li)[2].style.display
(presuming you knew which list item you were targetting)
Also, the display property may not yet be set. Try checking:
var state = (document.getElementById(id).style.display== ||
document.getElementById(id).style.display==none)?none:block;
Grant
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, 22 June 2005 3:17 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] detecting css display properties
I have been trying to detect ,using javascript , the css display
property
(set via an external @import style sheet) of an element
Example
page: http://www.jimthatcher.com/site_resources.htm has a LI
(class=skip
with CSS display:none.
but when i try to find this via the (IE DOM) i cannot locate it.
any ideas?
with regards
Steven Faulkner
Web Accessibility Consultant
National Information Library Service (NILS)
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: [EMAIL PROTECTED]
National Information Library Service
A subsidiary of RBS.RVIB.VAF Ltd.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
**
**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**
**
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] Ten questions for Joe Clark
In regard to Ten questions for Joe Clark: http://webstandardsgroup.org/features/joe-clark.cfm This is an interesting article but in answer to question 9 Joe suggests scope as being the most effective way to associate different-level headers and data cells. Unfortunately neither Window Eyes nor JAWS supports scope so we're back to another situation where we either follow the standards and allow people to be let down by their adaptive technology's lack of standards support or we come up with another way to do things. I think the best bet would be to use id and headers as in http://www.cli.nsw.edu.au/optionkeys/guidelines/tables_2.htm Grant Focas ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Firefox and vulnerabilities?
Another way tp ortect yourself without disabling JavaScript is to disable the Allow web sites to install software radio button in Tools/Options/Web Features Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Amit Karmakar Sent: Tuesday, 10 May 2005 1:40 PM To: wsg@webstandardsgroup.org Subject: [WSG] Firefox and vulnerabilities? http://www.enterpriseitplanet.com/security/news/article.php/3503751 Sorry if OT! The Mozilla Foundation is aware of two potentially critical Firefox security vulnerabilities as reported publicly Saturday, May 7th. There are currently no known active exploits of these vulnerabilities although a proof of concept has been reported. Changes to the Mozilla Update web service have been made to mitigate the risk of an exploit. Mozilla is aggressively working to provide a more comprehensive solution to these potential vulnerabilities and will provide that solution in a forthcoming security update. Users can further protect themselves today by temporarily disabling JavaScript. Regards, Amit Karmakar http://karmakars.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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] CSS Document layout/structure
Another thing to consider is whether other people have to read your CSS. If working in groups (or still learning) its best to minimise redundancy. see http://www.mezzoblue.com/archives/2005/01/20/redundancy_v/ cheers, Grant Having sorted out the html code to make it more readable and modifiable it seems that we have shifted the mess to style sheets. Many of the sheets I look at are long, comment-less and very difficult to understand. So that I don't fall into the same trap, can anyone recommend some reading on how to make style sheet structure and layout both understandable and also easily modified? ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Styling Forms
If you use label elements around your text then you can simply do this:
HTML:
plabel for=firstNameFirst Name/labelinput type=text id=firstName
//p
CSS:
form p{
clear:both;
}
form p label{
float:left;
width:30%;
}
Grant
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Darren Wood
Sent: Tuesday, 5 April 2005 12:35 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Styling Forms
[EMAIL PROTECTED] wrote:
Good evening all,
I know there's two schools of thought regarding forms where one uses a
table and the other a definition list to style and layout the data fields.
I have a simple form on a client's Contact Us page, and I wondered if
there's a consensus as to which method is more semantically correct?
Please advise...
There's a simple question I ask myself before I decide whether something
goes in a table or not, and that question is:
Is it tabular data?
In this case I'd have to say that a form is _not_ tabular data. Its
form data, and thus I'd try to make use of the tags designed to deal
with forms:
form
fieldset
legend
label
input
textarea
Hope that helps
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
**
**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**
**
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] !important via script possible?
A warning against using the !important declaration as a hack: see http://tantek.com/log/2004/09.html#d07t1434 here's an excerpt: IE (all platforms) supports !important, just go try the CSS1 Test Suite section 3.1 (http://www.w3.org/Style/CSS/Test/CSS1/current/sec31.htm) important test suite page for yourself. And if you check any of the CSS feature support charts out there, you'd see the same. There is however a kernel of a bug hidden in this tip: margin-top: 3.5em !important; margin-top: 2em So, the top margin will be set to 3.5em for all browsers except IE, which will have a top margin of 2em First, the reported problem only occurs for IE/Windows based browsers (i.e. IE5/Mac handles !important properly, including in this case. Another reason to question the article, as it appears the author doesn't distinguish between IE/Windows and IE/Mac rendering engine behavior, which can be quite different.) Second the problem actually has nothing to do with !important, but with the processing of multiple declarations of the same propertry in the same style rule. Similar problems result in IE/Windows if you try multiple declarations of the 'color' property for example with a CSS1 value followed by a CSS3 Color value that latter user agents support. hope this helps, -Grant Rebecca Cox wrote: I'm pretty sure this isn't possible, but does anyone know if its possible to add the !important declaration to a style set with script, [...] Its fine in Gecko but not IE6... Any ideas? As just mentioned in the reply to another thread, IE ignores !important -- Patrick H. Lauke ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Semi-newbie: advice needed
Mark, A book called The CSS Anthology (101 Essential Tips, Tricks and Hacks) by Rachel Andrew is the best i've found so far. As for online tutorials the CSS positioning one at Brainjar is great - http://www.brainjar.com/css/positioning/default.asp cheers, Grant Mark B wrote: Hiya. I'm an experienced HTML CSS coder who has dabbled a little with the XHTML/CSS way of doing things, but frankly, am a little lost. All the tutorials I've found on the web assume that you are either experienced and trying to do some advanced stuff, or are completely new and don't know CSS. I'm looking for an online tutorial or book that will help me go from the old ways to the new ways - help wean me off tables! :) Can anyone offer suggestions? I'm sure many others on this list have been down this path. Cheers, Mark ** 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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] vertical drop-down menu
Hi, The problem with these drop-down menus is that they rely on Javascript for cross-browser compatibility. http://www.easymenu.co.uk/ is a classic example. Try disabling JavaScript in Firefox and finding the pages under the navigation item About us. For example contact us takes you to http://www.easymenu.co.uk/contactus.asp but there is no way to get there from the homepage without JavaScript. Be careful to consider this when designing sites that use this 'standards-compliant' method. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Christian Peper Sent: Friday, 25 February 2005 3:19 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] vertical drop-down menu john wrote: Can anybody recommend a tutorial and/or some examples of a standards-compliant menu with a vertical orientation? Specifically, I need something that allows the user to see the second-level options when you either click or mouseover the main menu. Check out AListApart (ALA) for some excellent resources in this area! www.alistapart.com I can't find the vertical one I'm sure I've seen it being mentioned there (anyone else remember?). Otherwise, try EasyMenu http://www.easymenu.co.uk/ Hoep this helps, Chris. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] empty named anchors
Empty link elements are not good (as Patrick pointed out)but what about named anchors (destination anchors)? Is there any reason why they should not be empty? I ask this because I am evaluating a site management application called Watchfire WebXM and it warns me of accessibility problems because I have a id=toc name=toc/a above the table of contents. It warns me that WCAG priority 2 guideline 13.1 states Create link phrases that make sense when read out of context. My initial thoughts are that it's just a typical glitch of software unable to percieve the difference between a named anchor and a link. I think this because there are plenty of examples of accessibilitistas using them, for example: Mark Pilgrim's Dive Into Accessibility site (http://diveintoaccessibility.org/day_11_skipping_over_navigation_links.html) uses: a name=startcontent id=startcontent/a Joe Clark's Building Accessible Websites (http://joeclark.org/book/sashay/serialization/Chapter08.html) has this: This construct is legal HTML: a href=#zip_to_search title=Zip to search/aa name=zip_to_search/a Can anyone clarify? thanks, Grant ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] color schemer
Ryan, The AIS Web Accessibility Toolbar is great for that - see your site as greyscale, colour blindness, glaucoma, all sorts.. and that's only one small part of it. http://www.nils.org.au/ais/web/resources/toolbar/index.html Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ryan Reynolds Sent: Thursday, 23 December 2004 7:44 AM To: [EMAIL PROTECTED] Subject: RE: [WSG] color schemer Flipping this on its ear: are there any tools to help those with good colour perception to preview what a design might look like to those who are colour blind. I know certain schemers do this, but I'm thinking more for reviewing finished products. Sadly my eyes didn't come with a colour blindness setting. ;) Ryan Reynolds ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] neat code in A9 search
WinMerge will get rid of them. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wong Chin Shin Sent: Tuesday, 21 December 2004 1:46 AM To: [EMAIL PROTECTED] Subject: RE: [WSG] neat code in A9 search How do I remove this BOM marker once it's inserted? Damn it, it causes all my XSL transformations on Java to fail! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kornel Lesinski Sent: Monday, December 20, 2004 10:30 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] neat code in A9 search there appears some funny characters. !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN This is another Microsoft invention - BOM marker used to recognize UTF-8 files. ByteOrderMarker makes no sense in UTF-8. Notepad and other MS-tools silently insert it in all UTF-8 files, making them invalid. This breaks HTML validation, causes trash in some browsers and breaks PHP4 buffering... Use Notepad2 for unicode - http://www.flos-freeware.ch/notepad2.html -- regards, Kornel Lesiski ** 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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** N.X+i nZv+hymjl.f.wq(b(,)azX)i
RE: [WSG] help with fixed positioning in IE
john,
the solution requires putting the an html comment above the doctype declaration.
If you also add this CSS hack it will work in IE/Mac, Safari and IE5 and 5.5/Windows:
/* Mac IE cannot read this \*/
* html body{
/* only IE Win and MacOSX can see this,
but is hidden from Mac IE by previous filter.*/
overflow:hidden;
}
* html div#content{
/* only IE Win and MacOSX can see this,
but is hidden from Mac IE by previous filter.*/
height:100%;
width:100%;
overflow:auto;
}
hope this helps,
Grant
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of john
Sent: Wednesday, 13 October 2004 12:36 AM
To: [EMAIL PROTECTED]
Subject: Re: [WSG] help with fixed positioning in IE
I appreciate the discussion on this...really, I do. :) Is there
somebody who might be able to help me integrate this into my existing
CSS? Am I to understand that I can't have my DOCTYPE set to XHTML (I'm
not very well-versed in what IE Quirk Mode is)?
Thanks.
~john
_
Dr. Zeus Web Development
http://www.DrZeus.net
content without clutter
john wrote:
After a bit of searching, I found a site that explains how to get fixed
positioning in IE. This is great news for me, since I really would like
such a thing on the design of one of my sites. Trouble is, I'm having a
difficult time incorporating it into my existing CSS, and I'm wondering
if there's a kind-hearted soul who could possibly assist me. What I
need is both #banner and #tabmenu to stay put (as it does in Firefox).
The site I'm working on is at http://www.drzeus.net/redesign/cslewis/
The page with the CSS code for fixed positioning in IE is at
http://limpid.nl/lab/css/fixed/header
My gratitude to any who can 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
**
**
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**
**
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 with fixed positioning in IE
I almost thought a problem that had been plaguing me for ages (apart from Howard) had been solved by this until I tried to view it in Mac/IE5.0. No scrollbar appears until a link is clicked (fixed positioning). In the time it takes to load the next page a scrollbar appears on the first page. In Mac/IE5.1, Mac IE5.2 and Safari no scrollbar appears at all. Does anyone have any suggestions to overcome this? Grant Focas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Patrick H. Lauke Sent: Tuesday, 12 October 2004 8:25 AM To: [EMAIL PROTECTED] Subject: Re: [WSG] help with fixed positioning in IE john wrote: The page with the CSS code for fixed positioning in IE is at http://limpid.nl/lab/css/fixed/header Interesting...although I wonder why Anne didn't actually construct proper html documents with a html, head and body...because it seems to work in that situation as well? Patrick H. Lauke _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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 with fixed positioning in IE
I've solved the Mac scrollbar problem. http://www.homebass.info/fixedPosTest/ Now the only issue left (besides that it uses CSS hacks) is that the back to top link only takes you to the top of the content div minus the height of the header. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Focas, Grant Sent: Tuesday, 12 October 2004 9:37 AM To: [EMAIL PROTECTED] Subject: RE: [WSG] help with fixed positioning in IE I almost thought a problem that had been plaguing me for ages (apart from Howard) had been solved by this until I tried to view it in Mac/IE5.0. No scrollbar appears until a link is clicked (fixed positioning). In the time it takes to load the next page a scrollbar appears on the first page. In Mac/IE5.1, Mac IE5.2 and Safari no scrollbar appears at all. Does anyone have any suggestions to overcome this? Grant Focas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Patrick H. Lauke Sent: Tuesday, 12 October 2004 8:25 AM To: [EMAIL PROTECTED] Subject: Re: [WSG] help with fixed positioning in IE john wrote: The page with the CSS code for fixed positioning in IE is at http://limpid.nl/lab/css/fixed/header Interesting...although I wonder why Anne didn't actually construct proper html documents with a html, head and body...because it seems to work in that situation as well? Patrick H. Lauke _ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.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 ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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 with fixed positioning in IE
Using a body id will not work because the top of the page is alsways in view. It is the top of the content div which is hidden. But the DOCTYPE was wrong and its now fixed, thanks. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nick Gleitzman Sent: Tuesday, 12 October 2004 2:31 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] help with fixed positioning in IE On 12 Oct 2004, at 1:27 PM, Focas, Grant wrote: I've solved the Mac scrollbar problem. http://www.homebass.info/fixedPosTest/ Now the only issue left (besides that it uses CSS hacks) is that the back to top link only takes you to the top of the content div minus the height of the header. Grant Try adding an id to your body tag and linking to that instead of the named anchor. Also, your DOCTYPE is incomplete - it should include a URL for the DTD to which it refers... HTH N ___ Omnivision. Websight. http://www.omnivision.com.au/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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 with fixed positioning in IE
For me it goes to the top but not quite. Safari 1.02 does make it go higher than Netscape 7.2 or IE5.2 but it still doesn't go right to the top. For instance, in Netscape 7.2 on Mac the back to top takes me back to 'Adapted from fixed positioning' not to 'Fixed header and footer'. This isn't too bad when the header is only 60px but if it were 120 the difference would be quite a worry. Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nick Gleitzman Sent: Tuesday, 12 October 2004 3:22 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] help with fixed positioning in IE On 12 Oct 2004, at 2:55 PM, Focas, Grant wrote: Using a body id will not work because the top of the page is alsways in view. It is the top of the content div which is hidden. Well, in that case I've misunderstood what you're trying to do with the link. In all my Mac browsers (IE5.2, Safari 1.2, Netscape 7.2, Firefox 0.9) the link 'resets' the page to the way it looks when it frist loads - which is what I always have my 'top' links do... - ? N ___ Omnivision. Websight. http://www.omnivision.com.au/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] Table-style admin layouts
Ryan, this is tabular data, just what tables are built for. Go for it! Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ryan Sabir Sent: Tuesday, 5 October 2004 4:23 PM To: [EMAIL PROTECTED] Subject: [WSG] Table-style admin layouts Hi all, Is there a best-practice way to build an item display with multiple columns, but without using tables? What I want to do is build something like this: Name Price Quantity EditDelete Apple $5.0025 [edit] [delete] Pear $4.00 3 [edit] [delete] Banana $12.00 5 [edit] [delete] But without cluttering the HTML with table layout data... Or is this a case where its better to bite the bullet and just do it in a table...? I'm new here to please be gentle if this is a dumb question :) thanks, bye! --- Ryan Sabir Newgency Pty Ltd 2a Broughton St Paddington 2021 Sydney, Australia Ph (02) 9331 2133 Fax (02) 9331 5199 Mobile: 0411 512 454 http://www.newgency.com/index.cfm?referer=rysig ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** 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] increasing font size breaking layout
I was wondering if people had any opinions on when its acceptable if at all for a layout to break when users increase font size. Sites I am working on look fine if text is increased or decreased 1 or 2 times but when they are increased repeatedly the layout goes a bit whacky in some browsers (Netscape 6.2 on PC, IE5 Mac). Specifically, elements which are absolutely positioned get overlapped by wrapped list navigation. It seems to me that this only happens when text gets extremely large on small resolution screens and therefore I shouldn't worry too much, but is extreme all in the eye of the beholder? Grant Focas ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
[WSG] multiple versions of Internet Exploder
Be careful when running multiple versions of IE in side-by-side mode. I've experienced problems where the IE5 or 5.5 has inherited some of the properties of IE6, which do not show up when testing on a machine with a 'proper' version of IE5 or IE5.5. Mostly it's OK but i'm not using it anymore because i can't trust when it will truly act like IE5.x and when it won't. I'm sorry that i can't be more specific at this point but i've forgotten which things have been the problem other than conditional comments (ok, i know i shouldn't be using them anyway...) has anyone else had problems? Grant Focas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nick Lo Sent: Tuesday, 28 September 2004 12:36 PM To: [EMAIL PROTECTED] Subject: Re: [WSG] Mac site check please... Hi Francesco, It has some issues in earlier versions of IE PC You might want to check out (Just got my multiple versions of IE installed ( http://www.skyzyx.com/archives/94.php ) so it's nice to be able to say that! ). I had a quick look in IE Mac and it does have a few things needing sorting. I started giving it a crack but then thought: You seem to have a lot of div s and a fairly complicated HTML structure for a relatively simple page. Perhaps the best place to start would be to simplify as much as possible. e.g. just from a glance: div id=banner div id=bannerLeft div id=logoimg src=media/logo.gif alt=Blackcoil Productions title=Blackcoil Productions //div div id=pageimg src=media/pageHome.gif alt=Home title=Home //div /div div id=nav ulli id=navHomea href=Home.aspx alt=Home title=Homeimg src=media/navHome.gif //a/lili id=navAbouta href=About.aspx alt=About title=Aboutimg src=media/navAbout.gif //a/lili id=navCodea href=Code.aspx alt=Code title=Codeimg src=media/navCode.gif //a/lili id=navPhotoa href=Photo.aspx alt=Photo title=Photoimg src=media/navPhoto.gif //a/lili id=navBloga href=Blog.aspx alt=Blog title=Blogimg src=media/navBlog.gif //a/li/ul /div /div ...looks like it could easily become... div id=banner div id=bannerLeft img id=logo src=media/logo.gif alt=Blackcoil Productions title=Blackcoil Productions / img id=page src=media/pageHome.gif alt=Home title=Home / /div ul id=navli id=navHomea href=Home.aspx alt=Home title=Homeimg src=media/navHome.gif //a/lili id=navAbouta href=About.aspx alt=About title=Aboutimg src=media/navAbout.gif //a/lili id=navCodea href=Code.aspx alt=Code title=Codeimg src=media/navCode.gif //a/lili id=navPhotoa href=Photo.aspx alt=Photo title=Photoimg src=media/navPhoto.gif //a/lili id=navBloga href=Blog.aspx alt=Blog title=Blogimg src=media/navBlog.gif //a/li/ul /div ...and looks like it could potentially still be reduced. The simplified HTML would allow simpler CSS and therefore make debugging a lot easier as well. S'what I think anyway, Nick From: Francesco [EMAIL PROTECTED] Date: Tue Sep 28, 2004 8:47:38 AM Australia/Sydney To: wsg [EMAIL PROTECTED] Subject: Re: [WSG] Mac site check please... Reply-To: [EMAIL PROTECTED] It looks perfect to me on: Win IE 6, Win FF 0.9, and Win Opera 7. Francesco ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
RE: [WSG] onClick question
Yes, like that except i've led you astray with the capitalisation, sorry. It should be more like this: p id=photobutton a href=# onclick=window.print();return false onkeypress=window.print();return false Click here... /a Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Barry Beattie Sent: Wednesday, 22 September 2004 11:22 AM To: [EMAIL PROTECTED] Subject: RE: [WSG] onClick question you mean like this? p id=photobutton a href=# onClick=window.print();return false onKeyPress=window.print();return false Click here... /a (just curious, wanting to get it right) barry.b -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Focas, Grant Sent: Wednesday, 22 September 2004 9:56 AM To: [EMAIL PROTECTED] Subject: RE: [WSG] onClick question Try putting an onKeyPress as well, so that it's device independent Grant Focas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ted Drake Sent: Wednesday, 22 September 2004 9:36 AM To: [EMAIL PROTECTED] Subject: [WSG] onClick question I'm getting an error message when I try to validate this page: http://v4.csatravelprotection.com/csa/packinglist.do From the W3C validation service: Line 514, column 40: there is no attribute onClick p id=photobuttona href=# onClick=window.print();return falseClick here... Here is the offending code: p id=photobuttona href=# onClick=window.print();return falseClick here to print this page/a/p Why wouldn't this validate? I looked into the O'Reilly htmlxhtml guide and it doesn't say anything about it being deprecated. Does anyone have a suggestion? I've got the page set to xhtml 1.0 transitional Thanks Ted ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** ** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
