Re: RE: [WSG] Lower portion of lower case y does not appear in h1 in IE7
http://www.nichemktghouston.com/mneiman/mneiman.css
body {
/*text-align: center - centers the web page for IE only*/
text-align: center;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 13px;
line-height: 16px;
margin: 0px;
background-color: #33;
padding: 0 0 5px 0;
}
change the line-height: 16px; to line-height: 1.2;
***
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 goes live - correct link
I'm afraid this doesn't give me much confidence when your label for HTML5 is (X)HTML 5 One of the major points about HTML5 is that it is _not_ XML based. Second point would be what do you mean by Block(ish)? Regards, Mike *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Markup an Address?
Ryan Moore: Looking for best practice markup for addresses. is it correct to use dl dtMain Office/dt dd123 Fake Street/dd ddSomewhere, SomeCountry, SomeZip/dd /dl or is there a better practice for this? Diego La Monica: Ryan, I don't think is the correct use for dl+dt/dd because dt is a term while dd is a definition for the term, and in a dictionary it would be the best method (IMHO) because a term could have more than one definition, but in an address, each definition (in your example) is right, but any of them must be omitted. I suppose that the correct way to represent an address is by microformats. Bye. -- Diego La Monica Web: programmazione, standards, accessibilità e 2.0 Brainbench certified (transcript ID # 6653550) for: RDBMS Concepts; HTML 4.0 W3C HTML WG IWA/HWG Member Responsabile liste IWA Italy ( [EMAIL PROTECTED] ) Web Skill Profiles WG Member ( http://skillprofiles.eu ) phone +390571464992 - mobile +393337235382 MSN Messenger: [EMAIL PROTECTED] Email: [EMAIL PROTECTED] Skype: diego.la.monica - ICQ #: 249-460-264 Web: http://diegolamonica.info *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Markup an Address?
Use a microformat: http://microformats.org/wiki/hcard - Original Message - From: Diego La Monica To: wsg@webstandardsgroup.org Sent: Saturday, August 11, 2007 5:52 PM Subject: Re: [WSG] Markup an Address? Ryan Moore: Looking for best practice markup for addresses. is it correct to use dl dtMain Office/dt dd123 Fake Street/dd ddSomewhere, SomeCountry, SomeZip/dd /dl or is there a better practice for this? Diego La Monica: Ryan, I don't think is the correct use for dl+dt/dd because dt is a term while dd is a definition for the term, and in a dictionary it would be the best method (IMHO) because a term could have more than one definition, but in an address, each definition (in your example) is right, but any of them must be omitted. I suppose that the correct way to represent an address is by microformats. Bye. -- Diego La Monica Web: programmazione, standards, accessibilità e 2.0 Brainbench certified (transcript ID # 6653550) for: RDBMS Concepts; HTML 4.0 W3C HTML WG IWA/HWG Member Responsabile liste IWA Italy ( [EMAIL PROTECTED] ) Web Skill Profiles WG Member ( http://skillprofiles.eu ) phone +390571464992 - mobile +393337235382 MSN Messenger: [EMAIL PROTECTED] Email: [EMAIL PROTECTED] Skype: diego.la.monica - ICQ #: 249-460-264 Web: http://diegolamonica.info *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** 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 goes live - correct link
On 11/08/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm afraid this doesn't give me much confidence when your label for HTML5 is (X)HTML 5 One of the major points about HTML5 is that it is _not_ XML based. The HTML 5 WG have not only a non-SGML serialisation for text/html as one of their chartered deliverables, but also an XML serialisation that is intended to replace XHTML1.0/1.1. See the HTML WG charter: http://www.w3.org/2007/03/HTML-WG-charter 2. Deliverables 2.1 New publications and Milestones There is a single specification deliverable for the HTML Working Group, the HTML specification, a platform-neutral and device-independent design with the following items in scope: * A language evolved from HTML4 for describing the semantics of documents and applications on the World Wide Web. This will be a complete specification, not a delta specification. * An extensible, serialized form of such a language, using XML. * A serialized form of such a language using a defined, non-XML syntax compatible with the 'classic HTML' parsers of existing Web browsers. * Document Object Model (DOM) interfaces providing APIs for such a language. * Forms and common UI widgets such as progress bars, datagrids, menus, and other controls. * APIs for the manipulation of linked media. * Editing APIs and user-driven WYSIWYG editing features. Second point would be what do you mean by Block(ish)? Elements that behave like block level elements, I'd say. -- David liorean Andersson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Lower portion of lower case y does not appear in h1 in IE7
Thank you, but I need the background image that I used in the #title tag, How about putting the background image on the H1 instead? -- E. Michael Brandt www.divaHTML.com divaGPS : you-are-here menu highlighting divaFAQ : FAQ pages with pizazz www.valleywebdesigns.com JustSo PictureWindow JustSo PhotoAlbum -- *** 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 goes live - correct link
[EMAIL PROTECTED] skrev: I'm afraid this doesn't give me much confidence when your label for HTML5 is (X)HTML 5 One of the major points about HTML5 is that it is _not_ XML based. Already answered by liorean. May I add that prominent members of the WHAT-WG mailing list have read and OK'd my document as well. Second point would be what do you mean by Block(ish)? Block(-ish)/Inline(-ish)/Table refers to default CSS rendering. Blockish: Real block elements, list-item Table-ish: table, table-row-group, table-header-group, table-footer-group, table-row, table-column-group, table-column, table-cell, table-caption No element defaults to: run-in, inline-block, inline-table, marker or compact. Lars Gunther *** 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 updated for MSIE
I have now made it possible for MSIE to see my sheet as well.
I have provided an plain HTML version, but do not want any linking to
it. This is the set of rules in my .htaccess that I think should do the
trick:
---
RewriteEngine On
# The simple html version shall not be directly accessible!
RedirectMatch 301 html-elements-plain\.html \
http://egen.keryx.pad/resources/html-elements.xhtml
# The next ruleset changes nothing but should stop the following \
from executing
RewriteCond %{HTTP_ACCEPT} application/xhtml\+xml
RewriteCond %{HTTP_ACCEPT} !application/xhtml\+xml\s*;\s*q=0
RewriteCond %{REQUEST_URI} \.xhtml
RewriteCond %{THE_REQUEST} HTTP/1\.1
RewriteRule .* - [L]
# Go easy on MSIE and some bots
RewriteCond %{REQUEST_URI} \.xhtml$
RewriteRule html-elements.xhtml html-elements-plain.html [T=text/html] [L]
---
It works with FFox, Opera 9.2, Safari for Windows (complained at first
about too many redirects for no apparent reason) and MSIE 6. The latter
will miss two CSS 3 selectors and inserts line breaks like this:
[B]
lock(-
ish)/
[I]
nline(-
ish)/
[T]able
Any easy way to fix this except for nobr?
Please report any problems ASAP as I see that some people have started
to link to my little sheet. (At least three on Magnolia...)
Lars Gunther
P.S. MSIE will not recognize the check mark on my XP box, neither will
Safari.
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] Lower portion of lower case y does not appear in h1 in IE7
At 8/10/2007 05:01 PM, Joyce Evans wrote: When I view the following link (which Im working on) in IE7, the lower portion of the y in the word Physician does not appear. I see the entire y in IE 6 and FF 2 but not in IE7. This text is sitting within an h1 tag within a #title tag. Does anyone have an idea why I cant see the lower portion of y? http://www.nichemktghouston.com/mneiman/physician.html Also, in the content div, I have a background image bg_content.jpg that has graphics to the left and to the right, and the center is simply white. I have been told in the past that this type of background image is not a good idea meaning the white portion, but how could I get the left and the right graphics to appear and repeat as more content is added, without including the white portion of the graphic? Joyce, The problem of IE7 cropping off the font descenders is fascinating and I look forward to reading an explanation. Perhaps if you posted the problem to the CSS-D list you'd get an answer to that from the likes of Ingo Chao et al. Part of the overall problem you're having with this page is that the background image is just 35px tall so it can't accommodate text enlargement. The image includes its own top side borders so it can't be repeated vertically or horizontally as the text expands: http://www.nichemktghouston.com/mneiman/images/bg_title.jpg You tried to suppress this problem by sizing the font in pixels, but of course that succeeds only in IE. In other browsers the font enlarges out of its container and becomes not just ugly but also a nearly unreadable white on pale grey. Two simple ways to change this situation are a) to make the background image much taller so that more of it will be revealed as the headline increases in size and b) to split the background image into two components: the unrepeatable top borders and the repeatable orange body. Taking a step back, however, I don't see the need for a background image at all. The background imagery consists entirely of rectlinear monochrome spaces and lines that can be reproduced exactly with background colors and borders. The only complication in reproducing your page precisely this way is that adjacent CSS borders meet on a diagonal at the corner of a box and your top grey border butts flat on top of the gray side borders. This detail can be sacrificed for easy layout or reproduced exactly by using an extra nested div. Your nav menu as rendered is another sticky wicket, with the light dark grey pill shapes. Again you've created a fixed-height background that's inadequate to contain enlargeable text. An easy way to start solving this is to make that background image quite tall with a light grey body and the dark grey curves only at the bottom, and position the background image in the bottom of its container. It doesn't solve your menu's other problem which is that as the text enlarges the menu spills horizontally out of the page block. Allowing the menu items to wrap around within your fixed-width column will keep the menu on-screen while the font enlarges but you'll need to re-think its background image. One possibility is to use a segment of the light dark grey background for each nav menu LI so that each menu item maintains its grey blobby background even as it wraps. This would almost certainly require you to re-visualize the menu's graphic design to keep it looking good as text enlarges. Regards, Paul __ Paul Novitski Juniper Webcraft Ltd. http://juniperwebcraft.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] (X)HTML Best Practice Sheet updated for MSIE
Philip Kiff wrote Tested this link: http://keryx.se/[...].html Ooops. That isn't the link I tested. I tested the xhtml one that is supposed to get rewritten in the htaccess rules: http://keryx.se/resources/html-elements.xhtml Phil. *** 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 updated for MSIE
Keryx Web wrote: This is the set of rules in my .htaccess that I think should do the trick: [snip] It works with FFox, Opera 9.2, Safari for Windows (complained at first about too many redirects for no apparent reason) and MSIE 6. Tested this link: http://keryx.se/resources/html-elements-plain.html This link does not seem to work in MSIE 7, 6, or 5.55 on my test machines. The same link works on the same machines in Opera v.9.22. Did not test beyond that. Not sure about your htaccess code. You might also consider an alternative scripting method of serving the page to MSIE versions, such as one of these: http://sitesurgeon.co.uk/articles/serving-xhtml-correctly.html http://www.workingwith.me.uk/articles/scripting/mimetypes Phil. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
RE: [WSG] Lower portion of lower case y does not appear in h1 in IE7
Very nicely stated. Unfortunately, I have not yet adjusted to the possibility that a visitor to a site might change the text size on me. I need to change my way of thinking. Thanks for the feedback. Joyce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Novitski Sent: Saturday, August 11, 2007 10:07 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Lower portion of lower case y does not appear in h1 in IE7 At 8/10/2007 05:01 PM, Joyce Evans wrote: When I view the following link (which I'm working on) in IE7, the lower portion of the y in the word Physician does not appear. I see the entire y in IE 6 and FF 2 but not in IE7. This text is sitting within an h1 tag within a #title tag. Does anyone have an idea why I can't see the lower portion of y? http://www.nichemktghouston.com/mneiman/physician.html Also, in the content div, I have a background image - bg_content.jpg that has graphics to the left and to the right, and the center is simply white. I have been told in the past that this type of background image is not a good idea - meaning the white portion, but how could I get the left and the right graphics to appear and repeat as more content is added, without including the white portion of the graphic? Joyce, The problem of IE7 cropping off the font descenders is fascinating and I look forward to reading an explanation. Perhaps if you posted the problem to the CSS-D list you'd get an answer to that from the likes of Ingo Chao et al. Part of the overall problem you're having with this page is that the background image is just 35px tall so it can't accommodate text enlargement. The image includes its own top side borders so it can't be repeated vertically or horizontally as the text expands: http://www.nichemktghouston.com/mneiman/images/bg_title.jpg You tried to suppress this problem by sizing the font in pixels, but of course that succeeds only in IE. In other browsers the font enlarges out of its container and becomes not just ugly but also a nearly unreadable white on pale grey. Two simple ways to change this situation are a) to make the background image much taller so that more of it will be revealed as the headline increases in size and b) to split the background image into two components: the unrepeatable top borders and the repeatable orange body. Taking a step back, however, I don't see the need for a background image at all. The background imagery consists entirely of rectlinear monochrome spaces and lines that can be reproduced exactly with background colors and borders. The only complication in reproducing your page precisely this way is that adjacent CSS borders meet on a diagonal at the corner of a box and your top grey border butts flat on top of the gray side borders. This detail can be sacrificed for easy layout or reproduced exactly by using an extra nested div. Your nav menu as rendered is another sticky wicket, with the light dark grey pill shapes. Again you've created a fixed-height background that's inadequate to contain enlargeable text. An easy way to start solving this is to make that background image quite tall with a light grey body and the dark grey curves only at the bottom, and position the background image in the bottom of its container. It doesn't solve your menu's other problem which is that as the text enlarges the menu spills horizontally out of the page block. Allowing the menu items to wrap around within your fixed-width column will keep the menu on-screen while the font enlarges but you'll need to re-think its background image. One possibility is to use a segment of the light dark grey background for each nav menu LI so that each menu item maintains its grey blobby background even as it wraps. This would almost certainly require you to re-visualize the menu's graphic design to keep it looking good as text enlarges. Regards, Paul __ Paul Novitski Juniper Webcraft Ltd. http://juniperwebcraft.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
