Re: [WSG] Subtractive Box model
Philippe Wittenbergh wrote: You could do something like this: http://dev.l-c-n.com/disp-table/equal-H-nav.php Internet Explorer doesn't support display: table-cell; Can someone remind me why we use the additive box-model? It seems stupid to me, there's no real advantage. -- -David R ** 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] Site Review: whatcanido.com.au
Tatham, When browser window is resized vertically, clouds in the glass.jpg are not aligned with clouds in the background.jpg. Maybe, don't use clouds in glass.jpg. Instead use as a background checkboard pattern 1px colored (white or blue) x 1px transparent. Then, when this image is on top of background.jpg, you would see throught the clouds. I haven't tried it, but have a feeling it may do the trick. Cheers, Irina. ** 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] A different Firefox bug?
Hi, I've encountered a very odd behavior on my blog using firefox (mac). http://blog.jalenack.com If you focus the search box, or the any of the form elements in the comment section, a ~200x50 box appears at the top left corner. I have no idea why it happens, but it has been happening since I started my blog. When you scroll anywhere, it disappears. I have had other firefox mac users confirm this behavior, so it isn't just me. What should I do? Anyone come across this before? BTW, I'm sending as application/xhtml+xml for browsers that understand it. -- Jalenack.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] Site Critique
When I clicked on the reservation link I came to a page that where it asked me to put my reservation information and my credit card details. One huge error that I noticed was that the little pad-lock didn't show up at the lower-right corner of my browser. If I were a customer coming to this page I would immediately leave because of that. - Original Message - From: Debra Reese [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Friday, February 18, 2005 11:05 PM Subject: [WSG] Site Critique Hi List Members! Could anyone spare a moment to give some general comments about a site I am working on? The site is: http://marketstreetgrill.net I'd like to hear from willing Mac users. I am working on a PC. This is my first public critique ever, so please don't lambaste me for any glaring errors. I want to improve, so I'll appreciate your honest constructive criticism. Please e-mail me off-list at [EMAIL PROTECTED] -Debra ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 2/14/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 266.1.0 - Release Date: 2/18/2005 ** 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] Other character sets/languages
woric wrote: Choose charset UTF-8 (not UTF-8 BOM) when saving. Can you explain the difference? In other words, the BOM is a funny character Unicode uses as the very first char in some of its encoding forms to declare which byte is which when characters are composed of more than 1 byte. As stated by the Unicode consortium itself, utf-8 does not need this, so the mark can be safely ignored when creating a utf-8 document (you can even delete it from an existing document without consequences). Using the BOM in a utf-8 webpage would have two unhappy outcomes: Gecko-based browsers would display the thing (not something you'd usually like), and IE would render the page in Quirks mode (as with every other character coming before the Doctype declaration). The second point is really related to the document language, not the character encoding. Declaring it properly (with html lang=en and div lang=vi) should help screen-readers read each part of the page with the correct pronunciation and search engines recognize the content language (eg. every localized Google has an option to search only documents in its native language). djn begin:vcard fn:Dejan Kozina n:Kozina;Dejan org:Dejan Kozina Web Design Studio adr:;;Dolina 346;Dolina;TS;I-34018;Italy email;internet:[EMAIL PROTECTED] tel;work:+39 348 7355 225 tel;fax:+39 040 228 436 tel;cell:+39 348 7355 225 x-mozilla-html:TRUE url:http://www.kozina.com/ version:2.1 end:vcard
Re: [WSG] Other character sets/languages
Hi Dejan, You wrote: woric wrote: Choose charset UTF-8 (not UTF-8 BOM) when saving. Can you explain the difference? In other words, the BOM is a funny character Unicode uses as the very first char in some of its encoding forms to declare which byte is which when characters are composed of more than 1 byte. As stated by the Unicode consortium itself, utf-8 does not need this, so the mark can be safely ignored when creating a utf-8 document (you can even delete it from an existing document without consequences). Using the BOM in a utf-8 webpage would have two unhappy outcomes: Gecko-based browsers would display the thing (not something you'd usually like), and IE would render the page in Quirks mode (as with every other character coming before the Doctype declaration). OK, I understand about the BOM but this still leaves me wondering how to save properly. I usually code using Notepad which offers, from the Save As... menu choice, the Encoding options: ANSI Unicode Unicode big endian UTF-8 but no UTF-6 BOM. How can I be sure I am saving in the right way? In this matter, I am also wondering where using a meta tag specifying iso-8859-1 fits in terms of following the standards. I notice many people do this and I gather the actual coding of keystrokes (on a standard PC keyboard set up for US English) should be the same. Is saving a file as UTF-8 compatible with the iso-8859-1 meta tag? I have been checking in search engines and looking around in our [WSG] list resources, but I have concluded that I have no idea what to call my questions. Regards, Gene Falck [EMAIL PROTECTED] ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
