Re: [WSG] premature to test/worry new site for IE8?
Hi! Ben Buchanan skrev: My take on this is you cannot *really* code for a browser that's not released yet. Alpha/Beta/pre-release versions simply are not the same as final versions. My experience from IE7 beta releases in a nutshell: * bugs changed between betas * no bugs I encountered (and found workarounds for) in betas existed in the final release * a new bug was introduced in the final version, breaking the navigation completely for the sites I was working on ... The cheapest solution is to work with existing software, so coding for IE8 now is a bad idea in my opinion. Any work on finding workarounds for IE8 at this stage may be a waste of time. /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Spolsky on IE8 flag
Spolsky: Enough ugly hacks. 8 billion existing web pages be damned. If I got this right, only around 10 % of web pages are rendered in standards mode http://triin.net/2006/06/12/HTML, and will be affected by the changed behaviour in IE 8. Still a lot of pages, of course. Pages done long time ago or created by amateurs probably are rendered in quirks mode and will be so in IE 8 too, not in best standards mode. Is this so, or did I miss something on this topic? /andersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] linking to images with //
James Ellis skrev: Relative URI references are distinguished from absolute URI in that they do not begin with a scheme name. Instead, the scheme is inherited from the base URI, as described in Section 5.2. // in the beginning of the URI says this is a network path. I have no idea of how the browser support for this is, or how they choose to interpret it. A single / in the beginning says this URI is relative to the domain of the document. So in a sense it's absolute, but the scheme and domain are omitted. Browser support for this is excellent. Can't find the correct references at the moment. /andersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Toggle L2 menu items (within WCAG)
Kit Grose skrev: JonMarc, It sounds to me like he's referring more to a tree layout than a drop-down menu. When it comes to tree menus, I'll add this to the list: http://treemenu.nornix.com/ Standards compliant, keyboard friendly and more ... written by me. /andersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] skip to content: care of accessibility causing usability
Hi! Tee G. Peng skrev: Thanks to your influences, it has become my second nature to have 'skip to content' I use to do it the other way around, having the content first in source and using a link to get to the navigation. And then I simply put a link to the menu, not anything about skipping (all normal links tells you where they go, not where they don't go). Example: http://treemenu.nornix.com/ It's the first link on the page. Could be styled more like a heading or something. In this case there's also a little bit JavaScript magic in the link ... /andersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Encoded mailto links - and mail sender
Mike at Green-Beast.com skrev: That said, even though people are the most difficult to control, they don't seem to be the real problem. The problem seems to be with 'bots so that's the form's main focus. You're right, bots are the real problem to focus on. /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Encoded mailto links
Hi! Chris Knowles skrev: Plus you're still putting the email address in the source code albeit a modified version. If this became a popular way to handle mailtos a harvester is sure to be written to pattern match http://.../com/... or http://.../com/au/... or whatever at some stage and attempt to construct an email address from it. You could either use a key in the URL. http://example.com/mail/key which the server resolves to an emailaddress stored in a database backend, or you could add some arbitrary string to make it more difficult for harvesters: http://example.com/mail/me/arbitrary/stuff/to/confuse/harvesters The domain shouldn't be needed, your server sould already know it. It's a pity that the support for mailto: locations isn't better, though. As for now I still wouldn't attempt using it. /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Encoded mailto links - and mail sender
Hi! Mike at Green-Beast.com skrev: I offer that in my contact form. It's a config option. The contact form owner can enable/disable offering a get-a-copy option to his/her visitors. Is there any way to protect this from being used as a way to send out spam? You can't really know that people enter their own emailaddress ... /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Encoded mailto links
Hi! Nikita The Spider The Spider skrev: You might be interested in an experiment I ran that compared a few techniques for protecting one's email address from harvesting bots. The short answer: entity references worked very well I think the time span of your study is to short. I have used the method you used for äcklig, with mixed decimal and hexadecimal numeric entities. In about a year there was no spam, but somewhere at 1.5 years it started a little, and after 2 years there where 100+ spam/day. So I think you just push the problem forward, which could be fine in some cases. But when a entity-decoding spam harvester finds the email-address, this will get listed in the same databases as all other emailaddresses. The more traffic your site has, the less difference the encoding will make. I think the htaccess-trick linked to by Dejan Kozina looks more promising. I have used this method, but abandoned it because of that some browser wouldn't send the mailto: address to the email client. But this was a few years ago, so this could possibly have changed. If you already use .htaccess rewrite rules this is very simple to implement. The question is of course if harvester have implemented a way to capture those email-addresses too, but I think this would require more knowledge than decoding numerical entities (for instance the PHP manual describes how to do this ...). /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Encoded mailto links
Hi! Ray Leventhal skrev: As a matter of preference, I generally try to eliminate all mailto: links on any site I've been asked to work on. In place, I use a contact form, Me too :-) But then you get form-post spam after a while ... I have begun to add a random token as a hidden field to forms (which is then checked on the server side, ensuring that a form can only be posted once), stopping bots that don't actually read the form every time. (I actually think most of them don't ... when I change the field names in forms the spam form posts continue to use the old ones for a long time.) The random token method is 100 % standards compliant and so on, but rather easy for bots to work around. Still more difficult than decoding mailto links. Also randomly changing the name of the token field would be the next step (requiring bots to examine the form for the current token field name and content in every form every time). A human spammer (not using a bot) will of course be able to send the form, but I think people sitting and copy-pasting spam into forms is not a big concern. Captchas is also a possibilty, but I sometimes have difficulties reading them myself. Not very user friendly. Random tokens are more user-friendly, as they are handled automatically by the browser, and not even seen by the user. But it's not so easy to add it to every site, it depends on the architecture used and you need some scripting language on the server (but I think most sites have this anyway today). IMHO captchas are used too much, as they suck considerably! /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Encoded mailto links
Hi! Chris Knowles skrev: maybe harvesters look for the ASCII value of the @ symbol and find addresses still? Some harvesters decodes the links, so this is not a solution to the spam problem. The decoding is really trivial to perform in most programming languages. /anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] (X)HTML Best Practice Sheet - CSS issues
Keryx Web skrev: The Open Office version has a nice feature. The headings are fixed when you scroll. One can't duplicate that in a table with CSS as far as I know (position: fixed for table columns and rows...) You are looking for thead/tbody HTML elements: http://www.w3.org/TR/html401/struct/tables.html#edef-THEAD http://www.w3.org/WAI/UA/TS/html401/cp1001/1001-THEAD-TBODY-TFOOT-OVERFLOW.html http://www.imaputz.com/cssStuff/bigFourVersion.html /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Usefulness of JSDoc
Hi! Keryx Web: 1. Is JSDoc not a good idea? If so, why not? It's a good idea, but it's not nearly as useful as JavaDoc. I think there are problems arising from the degree to which JavaScript is a dynamic language. 2. If it is, why has it not caught on? Real programmers with experience of automated documentation tools don't care about writing JavaScript. Front-end developers are often not used to set up build script that strips out comments for production code or generate documentation and the like. In a situation today where we use more and more complex JavaScript solutions I think the need for good JavaScript documentation increases. References: http://jsdoc.sourceforge.net/ This project is building a JS documentor in JS on top of the Mozilla Rhino engine: http://code.google.com/p/jsdoc-toolkit/ I have tried both for documenting some of my code, see: http://nornix.sourceforge.net/jsapi/ http://nornix.sourceforge.net/jsapi2/ Both get some things badly wrong. I have tweaked both code and comments to help them out, but the question is if that is a good way to use my time :-) /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Back to the Future
Chris Taylor skrev: Hi all, I've been asked to write a website that MUST work in Netscape 4.03 and Remember to put modern CSS in a separate, imported stylesheet file, as NN4 can crash when encountering CSS that it does not know how to interpret. /Anders *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Firefox web developer icons
Bojana Lalic skrev: Where can I find those icons used in the firefox web developer add-on? I am after the Disable, Information and Green tick ones. Not an answer to your question, but this icon set is good and free to use: http://tango.freedesktop.org/Tango_Icon_Library /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Suggestions rquired on my web portfolio
I would really appreciate, if you guys can take a look at : www.puneetsakhuja.com, and send me your comments/suggestions. Really nice work! The form does not validate, it's easy to fix that, check the validator output: http://validator.w3.org/check?verbose=1uri=http%3A%2F%2Fwww.puneetsakhuja.com%2Fdynamic%2FDefault.aspx /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] css type loop
Rob Kirton skrev: More precisely, the use of id and class can only add semantic value to developers or to those who have to maintain the site. They have no bearing on real world semantics in terms of benefit derived by end users and page retrieval via search engines. Take a look at this: https://addons.mozilla.org/en-US/firefox/addon/4106 It's the Operator Fx extension, which lets end users make use of microformats. I think this or something similar will be a part of Fx 3. And IE 8, actually. /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] doing things right
Bob Schwartz skrev: tdnbsp;/td AFAIK this was needed for NN4. /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Use of Enter key to naviagte between form fields
Hi! Nick Fitzsimons: I would say that the main issue is that the Enter key is used to submit a form. When I fill in a form, I usually Tab from field to field and, when at the end, hit Enter to submit it. There's no way I would be pleased to find the expected behaviour was broken. The implication is that I would be expected to actually move my hands away from the keyboard to use the mouse to submit the form, which is downright annoying. You could implement this so that when pressing the Enter key in the last form field, the focus moves to the submit button. But it won't work any good with multiple submit buttons, of course. And it's better not to change the Enter key behavoiur in the first place :-) /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Use of Enter key to naviagte between form fields
Hi! Nick Roper: A customer has requested that they should be able to navigate between input fields on a form by using the Enter key - i.e. to replicate the action of the Tab key. If your customer wants to avoid that users submit the form by mistake by pressing the Enter key, you could add a confirm dialog to the form submit event. /AndersN *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Re: Encoding test page
Hej! Keryx webb skrev: That's what we were discussing. If a page is sent as XHTML, one could argue that it's supposed to be self-documenting, and that it might mean that the xml-prologue should be more important than the http-header. As my page proves, in FFox, MSIE and Opera (the three I've tested) that is not the case. Look at: http://www.w3.org/International/tutorials/tutorial-char-enc/en/slides/Slide0400.html Precedence rules 1. HTTP Content-Type 2. XML declaration 3. meta charset declaration 4. link charset attribute Related to previous comments -- from an earlier slide of the tutorial: http://www.w3.org/International/tutorials/tutorial-char-enc/en/slides/Slide0300.html For these reasons you should always ensure that encoding information is /also/ declared inside the document. (and not only in the HTTP headers, that is) I think the linked tutorial covers most of the questions regarding declaring encodings. /AndersN ** 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] standards-happy javascript for faq
http://www.nornix.com/testsidor/faq This one has very clean HTML markup. /AndersN SunUp skrev: Does anyone know of a method which will toggle the visibility of the FAQ answers while still displaying everything properly without javascript, and that adheres to current best practise for javascript? ** 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] Article: MIME and Content Negotiation
designer skrev: So I made a simplified version of my opening page (removed counters and other impedimenta) and removed the meta tags. All I got was Chinese and gobbledegook! So I uploaded it to: http://www.rhh.myzen.co.uk/rhh/gam/test.php I was stunned to find that it works a treat when uploaded! On my local machine I am using wampserver for testing. Any ideas as to why this should occur? Is it to do with utf-8? Use http://livehttpheaders.mozdev.org/ to check what http headers are really sent from the wampserver. /AndersN ** 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] content type etc
Hello! Paolo Dodet skrev: That is. If you access my personal site using IE you will notice that I use a meta tag to declare the mime-type, and in the case of IE it would be text/html, whereas if you access using any other browser the page will be served as XML, using a xml declaration, without any meta-tag to declare the mime-type. When using the meta tag to declare content-type, it is best practice to put it as early in the html as possible. I always put it immediately after the head opening tag. The logic behind this is that the browser should have to parse as little as possible before finding the content-type meta tag (as it sometimes has change the encoding of everything before the meta tag). This also shows why this information always should be sent with the http headers in the first place. /AndersN ** 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 filesize and selector names
Hejsan! [EMAIL PROTECTED] skrev: This has made my CSS file nearly 10kb large and consists of nearly 600 rows of CSS code. Is this a problem in general? No. Are there any issues regarding large CSS files? Any recomendations for CSS file sizes both in KB and rows. When hitting 40 KB I think it's time to figure out if the CSS also is overly complex. Such CSS also use to be hard to develop and maintain across different browsers. If you strip whitespace and (more important) use server-side compression the filesize shrinks a lot. My latest main stylesheet is 8kb, stripped and compressed it's less than 2kb that's actually sent!! should avoid underscore and mixing small (lower case) and large letters Mixing lower/uppercase enhances readability, just remember to write it the same way everywhere, class names and ID's are case sensitive. I tend to prefer hyphens, like #btn-save Underscores can cause some trouble, better avoid them. (hyphens are OK) /AndersN ** 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] injecting an extra hook with javascript
James Gollan skrev: You mentioned that you wanted to be able to see it when you view the source - is that important? http://jennifermadden.com/scripts/ViewRenderedSource.html FF extension to see the rendered source ! /AndersN ** 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] form hidden field ?
Dave, Firefox is rendering the border you've defined on the input
selector. Use inline CSS of border:0; or give it a class/ID (as you
have the other form elements) and add a rule to your stylesheet to
stop this from appearing.
I remember this bug from Mozilla a long time ago. I did this:
input[type=hidden]
{
display: none !important; // or whatever rules you need to override
}
/AndersN
**
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] Set min-width using DOM
Thierry Koblentz skrev:
Ian Rifkin wrote:
The min-width was set using CSS expressions which only works in IE. It
actually is javascript that makes it work, but it goes in the CSS
(inline or external stylesheet). It won't work if javascript is off.
I'm not sure about that.
I believe it still works with script disabled.
In Windows XP it did work with scripting disabled, but that was before SP2!
By wrapping a value in expression() you can make it work only
when scripting is enabled. Like this:
#logotype
{
z-index: 5; /* scripting disabled */
}
#logotype
{
z-index: expression(20); /* override when scripting is enabled */
}
/AndersN
**
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] When bugs become patterns - A look at CSS Hacks
Drake, Ted C. skrev: I think the future of CSS is not in hacks but looking seriously into using the conditional comments. I’m saying this as someone that is trying to figure out the best approach for retrofitting older conversions. Conditional comments are IE statements that say if ie6 use this additional CSS file, if IE5Mac, use this style sheet, if neither: ignore this statement. Conditional comments are Windows-only, unfortunately. Otherwise I share Ted's view on this topic. /AndersN ** 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] absolute positioning in IE
Hello! I want to position an element at the top right corner of the document (not the viewport). In standards based browsers this is easy using position: absolute; top: 0; right: 0; But the problem is, on most of the pages where I use this the positioned element disappears in IE. I can't find out what triggers this. The element is the second element in the document, so floating it right is not an option here. /AndersN ** 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] absolute positioning in IE
Kenny Graham skrev: Make sure the page validates. IE should render that fine unless it's in quirks mode. If it validates and still doesnt work, post a link and I'll have a look. The pages render in CSS1Compat (standards) mode. A page with only standards CSS: http://cms3.nawroth.com/testsidor/filer/testpage.html A page with some extra CSS for IE: http://cms3.nawroth.com/testsidor/filer/testpage2.html /AndersN ** 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] absolute positioning in IE
Ingo Chao skrev: Anders Nawroth wrote: http://cms3.nawroth.com/testsidor/filer/testpage.html For disappearing a.p. boxes, see http://www.brunildo.org/test/IE_raf3.html Your testpage shows the problem listed as Example 1 The fix is to rearrange the html, or by inserting an empty box, see the subsequent examples. Thanks for the link. The solution was to add a clearing box (in conditional comments, by the way) after the AP box. And I fixed the validation error too ... (thanks for pointing that out, dwain!) /AndersN ** 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] IE problem with ?xml version=1.0 encoding=iso-8859-1?
Patrick Lauke skrev: Richard Ishida You should at least check that you do declare the encoding in a meta tag, and that it is correct. Although it's best to also send the correct HTTP header to specify the document's encoding (otherwise it's the weird situation in which a browser needs to start receiving the document, then find out via the META what encoding it's in...which can cause problems in edge cases, if I remember correctly). Of course, the header and the META should not contradict each other either. If you are using META providing charset info, put it immediately after the HEAD element, to not not make this construct more weird than necessarily. Even if using HTTP headers is the first choice, including the META tag can prove useful for people saving the page for offline use, as HTTP headers are usually not saved with the page. I always use both methods. /AndersN ** 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] Know any standard's compliant WYSIWYG XHTML editors for a CMS integration?
Login at: http://webstandardsgroup.org/manage/login_edit.cfm and change your mailing list settings to include the CMS list. /AndersN Matt Harris skrev: Also, unfortunately I haven't recieved any CMS invitations. Do you have a link to the list? ** 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] bi-lingual page?
Barry Beattie skrev: this is the first time I've done anything like this but I'm wondering what it takes to display two languages (and therefore two charsets) There can be only one charset on a webpage, but with unicode/utf-8 you still can have content in different languages on the same page. /AndersN ** 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] Encoding, charsets and entities...
Dejan Kozina skrev: The encoding declaration in the XML prolog is required only if you use an encoding that's not utf-8 or utf-16. XHTML documents default to utf-8 if not otherwise specified, while HTML (4.01) documents have no default charset. http://www.w3.org/TR/xhtml-media-types/ Authors should also be careful about character encoding issues. A typical misunderstanding is that since an XHTML document is an XML document, the character encoding of an XHTML document should be treated as UTF-8 or UTF-16 in the absence of an explicit character encoding information. This is *NOT* the case when an XHTML document is served as 'text/html'. /Anders ** 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] PNG, IE JS
Hello!
Since turning JS off in IE also affects HTC-behaviors, I needed a fix
for the logotype on this site, as it covers some content when the
transparancy fails:
http://www.opalen.info/
(I'm using .htc for the logotype, the background of the content is a
simple GIF image.)
What I wanted to change was the layering of the elements, putting the
logotype behind the content instead of in front.
This is what I did (in a CSS-file sent to IE thru conditional comments):
#content
{
position: relative;
z-index: 10;
}
#logotype
{
position: relative;
z-index: 5;
}
#logotype
{
z-index: expression(20);
}
The number in the expression() will only be used when JS is turned on.
Even better would be to swap the image for IE. Any idea of how I could
do this from the CSS? (And I do want the logotype to be a img in the HTML.)
/Anders
**
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] JavaScript and W3C DOM discussion groups?
http://www.quirksmode.org/dom/list.html This list studies the JavaScript implementation of the W3C DOM in the various browsers. It has a strongly practical bend. Discussion of the standards is not forbidden, but the most important topic should be how the standards turn out to work in practice. /Anders Roberto Gorjo skrev: Hi, Im a newbie at this discussion group, but Im loving it and Ive already learned quite a lot just by reading it. It seems that JavaScript (or EcmaScript) and W3C DOM issues are somehow outside of this discussions group scope (judging by the mail list guidelines), which is a shame, from my point of view, as both are actual web standards today. Could anyone point to me any JavaScript discussion group that explores JavaScript having in sight the webstandards and the W3C DOM properties and methods? ** 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] problem with utf-8 page encoding
Vaska.WSG skrev: The Chinese websites I have looked up have latin1 style urls...no sign of Chinese text anywhere in there. Look at: http://zh.wikipedia.org/ Works in FF1 IE6 and the URLs look really nice in Opera8 (and sometimes in IE too). I have no other browsers here right now. Seems like http://www.mediawiki.org/ (used by Wikipedia) supports this kind of URLs. I work with a homegrown Php-based CMS, and I now have decided to go with non-latin1 URLs; I'm at implementing this right now. /Anders ** 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] problem with utf-8 page encoding
tee: These are domains but the one Anders provided does have a path in Japanese character, and it works in FF. http://www.w3.org/International/tests/sec-iri-3 I looked at ja.wikipedia.org and they use this practise. What doesn't always works well, is links from pages with other charsets than UTF-8. IE and Opera (I have only O8) handles this correct, but not FF. Otherwise this is more of a server-side issue, to handle paths in a correct way. I'm currently developing a site in japanese, so I have to decide wich way to go. I thought I'd go with a-z0-9 in the paths, but now I'm not so sure, as wikipedia apparently thinks japanese characters in the path is stable enough! /Anders ** 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] problem with utf-8 page encoding
this wouldn't be possible... http://www..com//.php According to W3C it shold be possible, look at: http://www.w3.org/International/tests/#iri IE needs a plugin to enable IDN: (Internationalized Domain Names) http://www.idnnow.com/ /Anders ** 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] problem with utf-8 page encoding
More in-depth information here: http://www.w3.org/International/articles/idn-and-iri/ Anders Nawroth skrev: this wouldn't be possible... http://www..com//.php According to W3C it shold be possible, look at: http://www.w3.org/International/tests/#iri IE needs a plugin to enable IDN: (Internationalized Domain Names) http://www.idnnow.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 **
Re: [WSG] Making PDF and Word files accessible
I have good experience with Tidy: http://tidy.sourceforge.net/ /Anders George S. Williams skrev: On Fri, 2005-06-03 at 06:36, Angela Galvin wrote: Secondly, with the Word documents, if there is an easier way to convert them to HTML? I use an open source program, antiword, to convert the Word docs to text and then just add the necessary markup. (And, of course, edit out the Word weirdness!) I've found this to be about 5 times faster than cut and paste. This is on a Linux box, but a Windows version of antiword seems to be available at- http://www.informatik.uni-frankfurt.de/~markus/antiword/ George ** 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 **
[WSG] UTF-8 (was: Quirks mode vs Standards mode)
HTMLTidy is the only useful piece of software I've found for web page development, and I use it to clean up my pages and get proper encoding of my Norwenglish lines of text into numeric entities (UTF-8) where needed. What characters needs encoding into numeric entities when using UTF-8? I try to avoid entities with exception for ' /anders (Sweden) ** 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] Re: Quoting Code Snippets
textarea is also an alternative, it handles long lines without making the width increase, and makes it easy to copy the code. http://treemenu.nawroth.com/source/menu /AndersN diona kidd skrev: Wouldn't you know it. As soon as I sent out that email, I found the answer. Behold, the pre tag Thanks, Diona ** 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 **
Re: [WSG] navigation using arrows for location
Paul Novitski skrev: I've been thinking along these lines lately, as I've just drafted another kind of menu that uses connecting lines: http://www.dandemutande.org/ResourceGuide.asp Play with the category location menus -- categories are only two-deep but location's four-deep. It is resizable (to a point). I've tried to come up with a standards-based tree-menu with connecting lines. With JS turned off the lines still show, but you can't open/close the folders client-side. I only use images for the horizontal lines, corners (last items) and icons. The open/close icons are added with JS. http://cms3.nawroth.com/treemenu The tree-menu is only used on this page and it's subpages. (But the tree still shows the entire site.) My problem is, IE gets the positioning wrong sometimes when you open multiple folders client-side (JS). Some bug is triggered, and i can't find any solution to this. /Anders ** 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] navigation using arrows for location
Thanks! I wish we could find out why IE throws the submenus around sometimes ... then it would be *really* useful. /Anders Paul Novitski skrev: Nice work, Anders! Paul At 02:40 AM 3/5/2005, you wrote: Paul Novitski skrev: I've been thinking along these lines lately, as I've just drafted another kind of menu that uses connecting lines: http://www.dandemutande.org/ResourceGuide.asp Play with the category location menus -- categories are only two-deep but location's four-deep. It is resizable (to a point). I've tried to come up with a standards-based tree-menu with connecting lines. With JS turned off the lines still show, but you can't open/close the folders client-side. I only use images for the horizontal lines, corners (last items) and icons. The open/close icons are added with JS. http://cms3.nawroth.com/treemenu The tree-menu is only used on this page and it's subpages. (But the tree still shows the entire site.) My problem is, IE gets the positioning wrong sometimes when you open multiple folders client-side (JS). Some bug is triggered, and i can't find any solution to this. /Anders ** 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 **
Re: [WSG] Help with centering - jumps horizontally depending on presence of vertical scrollbar
I use this code:
html
{
min-height: 100%;
margin-bottom: 1px;
}
It forces the vertical scrollbar on all pages.
/Anders
Mani Sheriar skrev:
Hi All,
Im working on a project which can be seen here:
http://www.manisheriar.com/qualitymine
The page is centered using a div align=center wrapping around a
wrapper div that holds all the content divs (header, content, sidebar,
and footer).
The problem I'm having is in non IE browsers (I've tested FireFox,
Mozilla, Netscape) the content will jump left a little bit when the
presence of a vertical scroll bar is necessary, and then jump back right
when you return to a short page.
I would love some advice on how to center a page and keep it in the same
spot, regardless of page length.
THANKS!!!
Mani Sheriar
Sheriar Designs | www.ManiSheriar.com
925|914.0741
**
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
**
Re: [WSG] Flyout menu questions
Pringle, Ron wrote: Ideas, criticisms, suggestions and opinions welcomed. http://www.aurora-il.org/testsite/index.htm I think it's to difficult to use for many visitors, flyouts are not so easy to handle for everybody! If you make Aldermans office and so on clickable, and point the links to simple menu-pages with the sub-choices, it would be a good alternative for users that have trouble with the flyouts. -- I do it this way myself, creating the submenus dynamically with Php. /AndersN ** 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] Preventing flash of unstyled content
http://www.bluerobot.com/web/css/fouc.asp David wrote: Does anybody know how to prevent the flash of (CSS)unstyled content that appears when a page is loading and the browser is yet to download and apply the stylesheet to the web page? ** 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] Looking for a good standards compliant wiki
Joe Leech wrote: Anybody know of one? Preferably where the user has to login to change the page. http://tavi.sourceforge.net/ Tavi is a extreme-lightweight-wiki. There is no login to change pages as for now. Tavi is written in Php -- it's not very difficult to add password protection or login to edit pages. I'm using the Tavi engine on this site: http://forum-antroposofi.info/ /Anders ** 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] :hover and accessibility
Christopher M Kelly wrote: Could a JavaScript onfocus/onblur combo work for this? I've been trying to create accessible drop-down menus with CSS and JavaScript and haven't quite got it working. What do you think about this kind of menu: http://www.movingart.info/ There should be a skip to menu link, but otherwise I think it's quite accessible with keyboard and mouse. It uses :hover (and csshover.htc for IE). I'd like to know pro's and con's of this method. /Anders ** 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] Web Accessability, SEO, Bookmarking - mod_rewrite
Chris Stratford wrote: So originally my method worked fine! just have the header point to: styles/sheet.css Use /styles/sheet.css. It points to the same location from everywhere in your site. /AndersN * 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] auto generated PHP sessions identifier causes valodation errors
Andrey V. Stefanenko wrote:
I am not able to confignure auto generated PHP output
dta href=./profile/?pid=1025PHPSESSID=6a2db2de31fb7e15728cc68dd01899c4
and not able to avoid ampersands in URL
Should I and how i can setup my PHP?
In your .htaccess file:
php_value arg_separator.output amp;
or in Php:
ini_set('arg_separator.output','amp;');
But i can avoid links - change them with forms and buttons. Is this the BEST
solution for this trouble?
I don't think so. Php will mess up your forms even worse.
You could also avoid using session id's in links, using only cookies.
php_value session.use_trans_sid 0
php_value session.use_only_cookies 1
/AndersN
*
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] Character Encoding Mismatch
Kay Smoljak wrote: I was under the impression - please correct me if I'm wrong - that if the server is sending the character encoding, there is no need to also have the meta tag. Is there any other reason to include it, client-side? Take a look at: http://www.w3.org/International/tutorials/tutorial-char-enc/Overview.html#declaring cite * An in-document encoding allows the document to be read correctly when not on a server. This applies not only to static documents read from disk or CD, but also dynamic documents that are saved by the reader. * An in-document declaration of this kind helps developers, testers, or translation production managers who want to perform a visual check of a document. /cite When using a xml-declaration, the encoding should go there, and not in a meta-tag. /AndersN * 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] Disabilities Survey
Philippe Wittenbergh wrote: One question had me wondering of late: do screen readers read the link element in the head, do they 'see' this as a link in their list ? Examples: link rel=bookmark href=#contents title=Read the article / !-- points to the contents area -- link rel=bookmark href=#navigation title=Site Navigation / link rel=search href=#search title=Search this site / !-- points to the search box, obviously -- I have it implemented at one of my sites [1]. I found this site, using link elements the way you describe and writing about it on this page: http://www.wats.ca/articles/extendinglinkrelationships/53 I think we're out of luck regaring the screen-readers, as long as they are built on top of IE. /AndersN * 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] file extensions
Michael Kear wrote: Whats the point of doing this? Saving 4 characters per image as a way of reducing bandwidth? Is there any other purpose? */ /* There is another purpose. See this W3C Note: http://www.w3.org/TR/chips/#gl3 Serve static content without file extension CM The reason why one should serve static content without file extension is similar to the reason stated above : the content manager may, at some point, want to change the document format used to serve a resource, yet the resource would remain equivalent. For example, switching from an image file format to an equivalent format, or switching from plain text to HTML... File extensions should therefore be hidden for static content, using content-negotiation (see Guideline 7: Server-driven content negotiation.), proxying or URI mapping technologies. /AndersN * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
