RE: [WSG] Re: Use of Fieldsets other than in form?

> Nick Gleitzman > Forgot this point: valid doesn't mean correct, or sensible. > It's really > easy to write code that validates, but which is semantic rubbish. The > Validator is a great tool for checking the correctness of markup, but > it can't interpret context - it's just a dumb piece of

RE: [WSG] Re: Use of Fieldsets other than in form?

> Lucien Stals > For a comparison, the w3schools site defines fieldset as "The fieldset > element draws a box around its containing elements." And that's the > complete sentence. Note no mention of form controls. > > I leave it to others to debate the authority of the w3schools > site, and > it'

RE: [WSG] Investigating the proposed alt attribute recommendations in HTML 5

> Alastair Campbell > Does the HTML working group have to take into account > accessibility guidelines? > > What I mean is, does it have to make alt mandatory because WCAG (any > version) does? I don't think HTML5 is expected to be rolled out until 5 years or so. In that sense, WCAG 1 would pr

RE: [WSG] lack of 'lang' attribute fails WAI

> Tee G. Peng > I am working on a bilingual site (chinese/english) that needs > to pass > at least WCAG AA, the site is UTF-8 charset and I didn't use lang > attribute in the meta because it's a bilingual site. [...] > What do you propose I should do to make the 'failure' goes away? Is every

RE: [WSG] Speaking of alt tags . . .

> Tee G. Peng > Hmmm, I didn't think about that. My clients asked me how to add > *decorative* images by themselves, I asked are they any meaning/ > purpose of those images, are they echo to your content, they said no > I just wanted my page looks nice in certain area. I told them sorry > y

RE: XHTML/HTML/Standards Conformance was Re: [WSG] Accessible - Standard Compliant - Club Membership System

> Marghanita da Cruz > While exploring the standards compliance/XHTML/HTML issue, > I was surprised by the variation in the display of Alt text. > On the small sample, the XHTML/HTML did not seem to make a > jot of difference. > > The screen shots are available at >

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

If you're doing business in a country (as in your company has offices and/or stores in that country), that country's legislation applies. P From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Wilson Sent: 03 October 2007 23:58

RE: A: [WSG] Target Lawsuit - Please Make Yourself Heard

> Jermayn Parker > 1992 > that is 15 years ago :shock: > surely its time for a new updated version that includes up to date web > version of rules etc. > > If you want businesses and websites to follow these standards > they need > to be update Because, you know...they've simply been ignori

RE: [WSG] Target Lawsuit - Please Make Yourself Heard

> Julie Romanowski > Please visit Michelle Malkin's site and post your comments - > http://michellemalkin.com/2007/10/03/blind-shoppers-get-green- > light-to-s > ue-target-over-website/. It's reassuring to see the exact same idiotic views still being bandied around, most of them along the "the w

RE: [WSG] Cost of Accessibility

Ok everybody...welcome to the *Web Standards Group* mailing list, where we discuss *Web Standards*. For discussions on history, sociology, politics, law, morals, capitalism, communism, etc, I'm sure there are other places... For those who don't think the DDA and ADA should apply in certain situ

RE: [WSG] Cost of Accessibility

> Gary Barber > Why bother taking the time to make something that is good > quality when > at the end of the day the client just wants cheap and functional and > looks nice. Professionalism? > So the client says "Why should I use you with your standards and > accessibility, Cowboy Design

RE: [WSG] Cost of Accessibility

> And here's me thinking that WCAG 1.0 _WAS_ a web standard !? Guideline, not standard. P Patrick H. Lauke Web Editor Enterprise & Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK T +44 (0) 161 295 4779 [EMAIL PROTE

RE: [WSG] Encoded mailto links

> Rick Lecoat > Is there a way out what seems, to my inexperienced eyes, like > a catch-22 > situation? Fix your spam issues at the mail server + mail client end, not at the web page end, would be my advice. P Patrick H. Lauke Web Editor Enterprise & Developmen

RE: [WSG] Encoded mailto links

Because you can't detect when a screen reader is there or not... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Or Golan Sent: 17 October 2007 15:33 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Encoded mailto links Why not simply di

RE: [WSG] Encoded mailto links

> Rick Lecoat > To join with Andrew Maben, however, I'd be curious to know whether > spambots decode encoded entity text, eg: > > 'user' > becomes > 'user' > > (ignore quote marks). > > > I assume that they can read them perfectly easily -- browsers > can, after > all -- but it'd be g

RE: [WSG] Encoded mailto links

> Rick Lecoat > If you are talking about actually hiding markup from certain agent > types, I'd certainly like to know your method. Screen readers run on top of normal browsers like IE of Firefox, so user-agent-wise you won't be able to really distinguish them. You *may* be able to catch some s

RE: [WSG] how a href with javascript pass in A level

> Gaspar > I think this should get a manual check or warning. You should ALWAYS do human checks of whatever an automated validation tools tells you, unless it's something purely technical (e.g. does markup validate to spec). P Patrick H. Lauke Web Editor Enterp

RE: [WSG] Appropriate use of the ABBR tag and Roman Numerals

> Matthew Pennell > It's not an abbreviated form of the full date by any stretch of the > imagination. Tell that to the microformats crowd - they've practically stretched the idea of "abbreviation" to anything, just so they can fit their machine readable data into the page... > Why not just u

RE: [WSG] Appropriate use of the ABBR tag and Roman Numerals

> E Michael Brandt > How about >MMVII ? I think this may stretch the meaning of DFN. A "defining instance" is the occurrence of the term where the term is defined. It does not enclose the actual definition. It also should only occur once per page for each defined term. P _

RE: [WSG] About Lightbox and SEO

> Matthew Pennell > 1) Many (most?) screenreaders do not read the title attribute by default. > 2) Many (most?) screenreaders are perfectly able to execute JavaScript, so > when the user clicks the link, what happens? It might announce that the > document structure has been updated (by the addit

RE: [WSG] About Lightbox and SEO

Wow, nobody decided whether or not it was a good idea or not. Screen readers sit on top of the regular browser (in most cases on Windows, Internet Explorer). They don't support javascript, they read the browser's DOM. The DOM is affected by javascript. As users work their way through a page, the

RE: [WSG] File comparison tool for Dreamweaver CS3

Assuming you mean on Windows, I've used WinDiff in the past and was reasonably happy with it (though purely to get an "at a glance" comparison, not to actually do any further processing of compared files - it doesn't seem to like UTF-8, for a start...) P Patric

RE: [WSG] BBC in Beta

A few things I noticed (being ultra-critical perhaps at this stage): First three links on the page are invisible skip links that don't show up, even on focus, plus there's another hidden link to accesskey definitions after the "accessibility help" link. On the separate "modules", it's initially

RE: [WSG] Usability for downloading documents

> Should we be making this decision for the user though? If, by > default, > PDFs open within the browser, then won't we be changing their user > experience by forcing them to open/save? In principle yes, but because so many other sites have "worked around" this issue (usually by opening new w

RE: [WSG] long description and its implementation

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ted Drake > Sent: 04 February 2008 14:41 > To: wsg@webstandardsgroup.org > Subject: RE: [WSG] long description and its implementation > > It's been a while since I've dealt with the issue of screen rea

RE: [WSG] long description and its implementation

Interesting...so what DO you get? Is that with JS enabled? P > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Steve Green > Sent: 04 February 2008 14:23 > To: wsg@webstandardsgroup.org > Subject: RE: [WSG] long description and its implementation >

RE: [WSG] ie8 & flash scripts

> kevin mcmonagle > hi, > anyone know how ie8 will work with ufo flash detection js and and the > standard dreamweaver flv embedding scripts? > thanks in advance > kevin There's not even a downloadable beta of ie8 out yet...so I think there won't be much of an answer beyond speculation? P ___

RE: [WSG] IE8 news

> Tate Johnson > I agree with your latter point. However, I fear that it > protects lazy > developers who refuse to adopt standards based practices. That said, > the more and more you look at the community on the whole; it seems > less ignorant today than at the start of the decade. The pr

RE: [WSG] firefox 3 beta5

> Korny Sietsma > Release Candidate 1 is out now, so hopefully things will get more > stable when Ubuntu picks it up, but at the moment it's a world of pain > - at least for my configuration! Beta5 and RC1 have been rock-solid on my systems (WinXP). And, as far as I understand, RC1 is fairly fea

RE: [WSG] HTML special characters coding

> Rick Lecoat > So let me see if I have this right: as long as my page declares an > encoding (I use UTF-8) I don't need to encode the entities, I > can just > type them straight into the markup. Is that correct? Make sure that your whole environment is UTF-8 (your code editor, any database

RE: [WSG] html vs. html

> jody tate > Most of their recommendations > include URI examples that use the .html extension and the > site itself > appears to use .html extensions: > http://www.w3.org/TR/xhtml1/Cover.html. In fact, there's some advice that advocates ditching file extensions altogether for future-proo

RE: [WSG] Marking Up Poems

Well yes, you could mark it up as XML behind the scenes, but you shouldn't be sending XML to the browser. They might or might not be able to cope with it, but you'd be breaking validation (unless you used XHTML sent as actual XML and start namespacing things). In simple terms, I'd mark up each

RE: [WSG] html vs. html

> Jonathan D'mello > To go off on a tangent Patrick, this is getting to be a rather common > excuse from some developers. If they don't want to change code, they > say it will break W3C standards. The core tenet of "web standards" is to choose the most semantically/structurally appropriate way t

RE: [WSG] Forcing a vertical scrollbar in Firefox 3

> [EMAIL PROTECTED] > html { overflow-y: scroll; } Ah, back in the days I tried it Opera wasn't playing ball. I now see that (at least Opera 9.5) understands this now. Good stuff. P Patrick H. Lauke Web Editor Enterprise & Development University of Salford Room

RE: [WSG] Forcing a vertical scrollbar in Firefox 3

> Mark Voss > html{min-height:100.2%;} even more subtle html { min-height: 100%; margin-bottom: 1px; } http://www.splintered.co.uk/experiments/49/ P Patrick H. Lauke Web Editor Enterprise & Development University of Salford Room 113, Faraday House Salford,

RE: [WSG] Browsers and Zooming

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Stickley Sent: 03 July 2008 14:56 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Browsers and Zooming I wonder what a partially sighted user would t

RE: [WSG] Who are the "Away on leave" Notices from? [SEC=UNCLASSIFIED]

wondering what part of THREAD CLOSED people don't understand... *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED]

RE: [WSG] RE: Tools or analytics to detect assistive devices

> http://www.accessifyforum.com/viewtopic.php?t=3775 The flash method (detect presence of software that hooks into MSAA) may be of some help if you write a small swf that then pings Google Analytics or similar. But worth noting this recent article http://www.paciellogroup.com/blog/?p=61 More fund

RE: [WSG] inline-block effect

> Brett Patterson > what does OP mean? Original Poster, i.e. the one who started this thread. P Patrick H. Lauke Web Editor Enterprise & Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK T +44 (0) 161 295 4779 [EMAIL

RE: [WSG] Downloading Fonts

> Ted Drake > Safari and firefox3 support the @font-face attribute. I don't know the status of Opera and IE8. I think current Opera doesn't, but the next version (Opera 10, currently available as alpha) will http://www.opera.com/browser/next/ P Patrick H. Lauke W

RE: [WSG]WCAG 2.0 enlarging text to 200% ?

> Heather > With WCAG 2.0 finally coming out yesterday - I was wondering how many ctrl + clicks in (firefox for example) 200% is? > I would say it was 3 but some colleagues argue 2 or 4 ? Any suggestions? I'd say conceptually that's quite a nitpicky argument...say a page broke spectacularly afte

RE: [WSG] Blockquote

Bringing it all back to the core question: cite is an optional attribute, so can be omitted when using the blockquote element. P Patrick H. Lauke Web Editor Enterprise & Development University of Salford Room 113, Faraday House Salford, Greater Manchester M5 4WT UK

RE: [WSG] Copyright Issues

> James Milligan > What about coming up with your own?Not meaning to sound rude, but it could be an opportunity for you. +1 Particularly since, if I remember correctly, you already ended up with the same problem with your startrek-related site that forced you to take it offline? P _

RE: [WSG] IE and the element

> Chris F.A. Johnson > On Tue, 24 Feb 2009, John Horner wrote: >> 1) Button elements don't need styling, they take their styling from >> the user's operating system, which they are, I assume, familiar and >> comfortable with. I won't be reinventing the wheel. > Button elements are styled by

RE: [WSG] Code scan, complient to guidelines version 2.0

> David Dorward > I use siteSifter - http://www.sitesifter.co.uk/ With the usual caveat that automated testing tools can flag up false positives and false negatives (for instance, on one site I just ran through the free sitesifter service, it flagged the lack of Content-Language in the HTTP heade

RE: [WSG] a WCAG 2.0 question

> Jon Gunderson > I think this requirement is a little out dated, screen readers today do a good job of telling people that a new window is open. But, as discussed, the requirement actually doesn't concern itself directly with links popping up new windows, but more things like the page all of a s

RE: [WSG] add to favorites?

> designer > Does anyone know of a modern, valid, reasonably cross-browser way to provide a link on a page so that a user can add the page to favourites? The only one I can find is IE only: I know you're probably asking because a client insists on having it, but...have we not evolved yet beyond re

RE: [WSG] Where is browser compatibility in wcag?

> Andreas Boehmer [Addictive Media] > to be accessible the site doesn't necessarily have to look great, but at least the content should show up in all browsers, even the old ones, right? Well, just talking WCAG 2, the requirement would be to use accessibility-supported technologies (see http:/

RE: [WSG] Quick accessibility question

Tested with JAWS 4.02, and yes, it reads it as "search". That's not to say, though, that all screenreaders behave this way... Let me guess...underlines for accesskeys ? One thing that worries me about doing those sorts of things is that the result is very...non semantic. Not sure how, say, search

RE: [WSG] Quick accessibility question

> From: Hugh Todd > Just tried it with a preview version of Apple's Spoken Interface in > Safari. I stuck your code into the middle of a standard form > element to > see what would happen, and it read it as "S" "earch". I'd be > interested > to know why (how the reader determines what to rea

RE: [WSG] ALPHA Testers Needed

Sounds interesting, but...I can do all that already with some find/replaces, so I'm not sure if people will be willing to pay for it (even if $5 is such a low price).   Or are you planning to have your tool parse the actual CSS, rather than simply looking for occurences of comments, spaces

RE: [WSG] invalid xhtml

> The best solution is to sniff if the UA accepts > application/xhtml+xml, > and if so, serve XHTML, otherwise, convert it to HTML4.01 and > serve it > that way. or you could convert it to xhtml 1.0 strict, which *may* still be sent as text/html Patrick Patri

RE: [WSG] Accessibililty and the positioning of navigation

There's two schools of thought: 1) navigation first, content second, with a "skip to the content" link 2) content first, navigation second, with a "skip to the navigation" link It's often argued that 2) is better for SEO, as it "top-loads" your documents, putting your relevant content fairly high

RE: [WSG] Tim Berners-Lee - Keeping Web Universal

I found it interesting that the IHT article page does not work unless you have javascript enabled... and even when it *is* enabled, their navigation (hitting the third column to move to the next "page") is fairly non standard, and is not backed up by any other cues to the user (heck, even a tooltip

RE: [WSG] invalid xhtml

> From: Andrew Sione Taumoefolau [...] > XHTML 1.0 strict is still XML, which means that you should not send it > as text/html. I beg to differ on this hair-splitting point: http://www.w3.org/TR/2002/NOTE-xhtml-media-types-20020801/#text-html "[XHTML1] defines a profile of use of XHTML which is c

RE: [WSG] invalid xhtml

> From: Andrew Sione Taumoefolau [...] > I'm not sure that we differ on this point. after re-reading your message, you're right. As I skimmed over the 100 odd emails in this list's folder that accumulated over the weekend, I could have sworn you had written MUST NOT, instead of SHOULD NOT. Ah, I

RE: [WSG] Tim Berners-Lee - Keeping Web Universal

> From: Stephanie [...] > In > fact, if you disable javascript and then go to the article, you can't > even see the first page. I was just working on something else at the time, and had javascript disabled...and that's what happened when I followed the link to the article. Confused the hell out of

RE: [WSG] Australian accessiblitly and the law?

> From: Kay Smoljak [...] > an online store selling rubber > widgets probably wouldn't be covered under "provision of services > including professional services So are they going to sell those rubber widgets in an unprofessional manner? Patrick Patrick H. Lauke We

RE: [WSG] 508??

Tim knows that. What Tim was asking was: what on earth is the thread starter asking when he says "Would someone please explain why the WSG thinks Section 508 is what should be used?" I'd be interested in what on earth he's talking about as well, coincidentally... Patrick -Original M

RE: [WSG] 508??

Despite some minor flaws, Joe Clark's "Building Accessible Websites" is still one of the best around. Captioning of quicktime (you mean via SMIL, I assume) is still not widely implemented due to flaky support in certain areas http://lists.w3.org/Archives/Public/w3c-wai-ig/2004AprJun/0651.html Of co

RE: [WSG] is REQUIRED

If I'm not mistaken, a single fieldset around your entire form content will do the trick. So, just change ... to ... Patrick -Original Message- From: Barry Beattie [mailto:[EMAIL PROTECTED] Sent: Fri 02/07/2004 01:38 To: [EMAIL PROTECTED]

RE: [WSG] id or class on html or body

Keep in mind that you can't have id or class attributes on the HTML element (not in xhtml, nor html4). Apply them to the BODY instead. Patrick Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk > -Original Message- > From: Mordecha

RE: [WSG] HELP REQUEST: netscape float:absolute problem

Haven't really waded through your css, so pardon me if it's an obvious one: have you set the parent to position:relative or absolute to force the float to use it as a point of reference? And your question is confusing, as there is no such beast as float:absolute http://www.w3.org/TR/REC-CSS2/visur

RE: [WSG] Internal CSS in XHTML served as application/xhtml+xml

Derek, have a read through http://devedge.netscape.com/viewsource/2003/xhtml-style-script/ ...but to answer the question quickly: it should work if you use // Patrick Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk > -Original Me

RE: [WSG] id or class on html or body

> is it good style to do so just to get the > correct behavior from a menu, since, after all, I'm not using them to > style the body at all (although I suppose I could). if you look at it the other way around though, it makes sense: the id/class is something intrinsic to the document itself; you

RE: [WSG] Internal CSS in XHTML served as application/xhtml+xml

> This breaks down though, for references like this in the page for > bookmarklets (pardon the length): but wouldn't you say that bookmarklets are a bit of a perversion of the standard, in which case it becomes academic to discuss how these can be served in a standards-compliant way? or is it jus

RE: [WSG] setting width for s when inline

> From: Scott Reston [...] > Is it possible to set width on an inline element? even though you now have a solution, I'd just like to answer this part of your question. As per http://www.w3.org/TR/REC-CSS2/visudet.html#q4 "10.3.1 Inline, non-replaced elements The 'width' property does not apply

RE: [WSG] CSS Opacity

This may be of interest http://archivist.incutio.com/viewlist/css-discuss/39758 In short, you could avoid the problem completely by using a 24bit PNG for the background, rather than using opacity. Patrick Patrick H. Lauke Webmaster / University of Salford http://w

RE: [WSG] Web Accessability IE Toolbar

> From: Lee Roberts [...] > It's bad enough everyone > thinks they need > to do it, but for an accessibility group to do it I'm flabbergasted. most current screenreaders / assistive technologie hook into IE in some way to provide web browsing. so it's still a harsh reality that some user groups W

RE: [WSG] setting width for s when inline

> From: Scott Reston > Does this suggest that > inline elements cannot have a width property at all? Yes. Any browser that applies width specified in CSS to an inline element (or even a block element that has been set to display:inline) is not behaving in line with the spec. > Can you clarify w

RE: [WSG] text field size tag

> It could be > that if padding, border and margin values are set (let's say > to zero) the widths of the different form controls may be the > same - or at least a bit closer ;) I wouldn't hold my breath on that one. Form elements are notoriously difficult to consistently style, as they are rep

RE: [WSG] setting width for s when inline

> Is the issue that giving an element float makes > the browser treat it as a block element? LI is a block level element by default, so you can apply width, regardless of whether or not it's floated. Patrick Patrick H. Lauke Webmaster / University of Salford http:

RE: [WSG] technique of converting to tablefree layout

Depends on how bad the table-soup is, but I usually like to start with some basic cleanup with find/replace using regular expressions in DWMX. Search for: ]*)> Replace with: You can, of course, add more tag names in there depending on your situation, with the obvious caveat that this only remove

RE: [WSG] Comment syntax in external javascript files?

I may well be wrong, but as far as I understand it it's not needed at all if your files (javascript, or stylesheets for that matter) are external. When your script is embedded in the page, it needs the proper commenting there as it needs to "live" within a well-formed XML file. When it's outside of

RE: [WSG] Titles Acronyms Abbr etc

Gah...not this discussion again... Acronyms are a subset of abbreviations. All acronyms are abbreviations, but not all abbreviations are acronyms. Now, once it comes to defining what an acronym is, there's cultural/regional differences as well: some argue that acronyms need to be pronounceable, o

RE: [WSG] semantic way to mark up form help?

Maybe a slight stretch, but how about wrapping these related elements (label, input, etc) up in their own fieldset, and using the legend for that text (thus associating it with the (input and label within). This is the title of your news post (does not accept HTML input) ... Other suggestion

RE: [WSG] After CSS?

Mike, nicely worded, if a bit convoluted. May I suggest WCAG checkpoint 14.1 ;) > -Original Message- > From: Mike Pepper > Sent: 23 July 2004 13:07 > To: [EMAIL PROTECTED] > Subject: RE: [WSG] After CSS? > > > Accessibility. Extend your skillsets with an understanding of > the challen

RE: [WSG] Web Accessability, SEO, Bookmarking - mod_rewrite

> If you are using from day one > you only need to change the path within one tag. But you still need to do it for every page in your site that uses it... So we are comparing the merit of making find/replaces site wide for all links vs. find/replace site wide for a specific tag. Or am I missing

RE: [WSG] Smooth fonts with CSS

http://www.alistapart.com/articles/dynatext/ > -Original Message- > From: Olajide Olaolorun [mailto:[EMAIL PROTECTED] > Sent: 30 July 2004 09:57 > To: [EMAIL PROTECTED] > Subject: Re: [WSG] Smooth fonts with CSS > > > hmmm I know just what I can do. > > I could probaly use a little

RE: [WSG] Fixed vs flexible layouts

I'd argue that the best compromise are elastic layouts, where things are positioned and sized in relation to other factors like font size. To say that if we just set our width to 100% or something and rejoice that the site will work in all sizes is misguided; there will always be extremes at both

RE: [WSG] Hacks

> From: Andy Budd [snip] > So I'm interested to hear what you folks think. Do you hack > or are you > hack free? Pretty much hack free here as well. Only thing I may use occasionally is using import to hide things from generation 4 browsers (and occasionally exploiting the flawed handling of sin

RE: [WSG] Fixed vs flexible layouts

> From: Geoff Deering [snip] > If you are designing for handheld you should be considering > display:none for > the none content columns, header and footer and just be using the link > element for prev, next, etc. Some sort of minimalist > approach may be more > appropriate for that media. act

RE: [WSG] Hacks

Just to pipe in on one small detail I noticed (not just in this message, but I'll piggy back onto it here) > Normally I would say avoid using hacks by taking time to > build the css > properly, It's often not just the CSS that needs to be changed to work properly, but it's a case of revisiting

RE: [WSG] Form labels

Firefox never had any problems with labels in my experience. It sounds more like your problem is the javascript? (at least I'm assuming that's what you mean when you talk about populating the fields) Do you have a URL we can have a look at? Patrick H. Lauke > -Original Message- > From:

RE: [WSG] DOM setAttribute in IE?

I'd suggest using Scott Andrews' addEvent helper function (see http://www.scottandrew.com/weblog/articles/cbs-events) function addEvent(obj, evType, fn, useCapture){ if (obj.addEventListener){ obj.addEventListener(evType, fn, useCapture); return true; } else if (obj.attachEvent){ v

RE: [WSG] Flash in Windows Mozilla 1.6

Does it use features specific to Flash7, and Browser Cam only has 6? (as I don't use Browser Cam I'm not sure if that last bit actually applies, but thought I'd throw that in as a potential cause) Work for me anyway on Win2k/Moz1.6/Flash7 Patrick Patrick H. Lauke

RE: [WSG] PHP is stopping my page validating as xhtml 1.0 Strict

As already mentioned, it's due to the url rewriter. You need to get it to write the session id inside a fieldset, and not directly in the form. So: add a fieldset around your form's content and then have a look at http://uk.php.net/manual/en/ref.session.php#ini.url-rewriter.tags. As I don't have

RE: [WSG] navigation problem

It's your logo which is overlapping the navigation with its padding. Effectively, there's invisible space over the navigation, making the links unclickable.   The solution would be something like   /* to give the positioning later on a point of reference */ #container { position: relative;}

RE: [WSG] web essentials briefing/ westciv CSS Guide

> From: Andy Budd > Web Essentials 04 looks like is turning out to be one killer event. I > wish it was a little closer to home so I could make it. Yup, same thoughts here... Patrick Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk **

RE: [WSG] Horizontal Scroll

Keeping in mind that overflow-x was originally an IE only proprietary extension, which has since found its way into the CSS3 draft, meaning that most non-IE browsers at this point don't support it. Firefox, for instance, doesn't work with the example you give (although I hear that a recent alpha

RE: [WSG] Does "display:none" work on img replacements?

display:none has been discourages early on in the whole image replacement discussion, as it completely hides the element from screen readers. Patrick > -Original Message- > From: Lorenzo Gabba @ Quirk [mailto:[EMAIL PROTECTED] > Sent: 08 September 2004 14:52 > To: [EMAIL PROTECTED] > Subj

RE: [WSG] I need advice with following font size standards and IE

Hardline reply: the onus is, at least in part, on the user. She needs to learn about the browser's settings, and if she's got the font size set to "smallest" in her browser, well then...she shouldn't really complain. Having said that, you can use absolute sizes xx-small, x-small, small, large, x-la

RE: [WSG] WYSIWYG Editors

www.editize.com offers solid performance and (despite its limited support for any but the most common xhtml elements) value for money, if you don't mind the fact that it's a java applet. Patrick > -Original Message- > From: Olajide Olaolorun [mailto:[EMAIL PROTECTED] > Sent: 16 Septembe

RE: [WSG] Moz vs. FF

A bit off topic perhaps, but: I'd suggest always starting with a fresh profile when installing a new version of FF. Export your bookmarks, make a note of any passwords etc you may have, write down which extensions you absolutely need...then download the new version, start it from the command line

RE: [WSG] Embedding Flash

> > I'd remind you to replace some of the alt tags though > (intro1.jpg etc). > > The client controls those. I'll remind them to make their alt tags > accessible. They're attributes...ATTRIBUTES...not tags! Sorry, bit of a rant. Feel better now ;) Patrick **

RE: [WSG] Semantics of Breadcrumb "you are here" links

Option 3 for me, on the grounds that yes, it's a list, but that the order of the list items is important (as it effectively denotes a step-by-step path from the site's home page to the current page, and these steps need to be taken in that particular order). It's this hierarchy inherent in the orde

RE: [WSG] Yahoo CSS'ing

Weird indeed. From home, I see the new table-less design. From work here, it's still the old one... Patrick > -Original Message- > From: Tony Crockford [mailto:[EMAIL PROTECTED] > Sent: 30 September 2004 09:15 > To: [EMAIL PROTECTED] > Subject: Re: [WSG] Yahoo CSS'ing > > > I'm a bit c

RE: [WSG] Why wont this validate

You need to move inside a block level element (in your case, move it into the fieldset which immediately follows it). Also, as it's an empty element, you need to make it self-closing Patrick > -Original Message- > From: Kim Kruse [mailto:[EMAIL PROTECTED] > Sent: 04 October 2004 16:54

RE: [WSG] please help validate

Stefan, crashes such as the one on your site are usually caused by something in the CSS that IE doesn't like. I didn't get a chance to actually look through it, but I'd suggest commenting out your different blocks in the stylesheet, one at a time, and trying to isolate the problem that way. Pa

RE: [WSG] Semantics of Breadcrumb "you are here" links

> -Original Message- > From: Ryan Nichols > Really a browser doesn't understand what any of the tags are. What you > see are only the browsers default behavior at rendering certain items > it's aware of in the DTD. This was all put in by whoever made the > browser, and is totally up to th

  1   2   3   4   >