Re: [css-d] form formatting...
At 17:00 -0500 on 06/12/2011, Michael Beaudoin wrote about [css-d] form formatting...: Hi all. I've been working on forms but I'm having trouble with some formatting issues. I have to incorporate some outside code for sweepstakes tracking and I'm having a heck of a time getting the birthdate field and the state pulldown to wrap so all is lined up. Can someone take a quick peek and see where I messed up, or what I'm missing? http://ba-doyn.com/junk/widget_test/index_redo.html Thanks, Michael I know that this is a CSS list but your layout might be better done as a Table (with two columns). Your current layout is a single line of data which relies on the Browser to wrap. As noted, different browsers have different widths that that are using. Also the birth date entry should be 3 drop down menus (it makes entry easier). As an alternative to the use of tables, you can force wrapping by just ending each entry with a br /. __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] form formatting...
At 21:30 -0500 on 06/12/2011, Michael Beaudoin wrote about Re: [css-d] form formatting...: On Jun 12, 2011, at 8:47 PM, Bob Rosenberg wrote: At 17:00 -0500 on 06/12/2011, Michael Beaudoin wrote about [css-d] form formatting...: Hi all. I've been working on forms but I'm having trouble with some formatting issues. I have to incorporate some outside code for sweepstakes tracking and I'm having a heck of a time getting the birthdate field and the state pulldown to wrap so all is lined up. Can someone take a quick peek and see where I messed up, or what I'm missing? http://ba-doyn.com/junk/widget_test/index_redo.html Thanks, Michael I know that this is a CSS list but your layout might be better done as a Table (with two columns). Your current layout is a single line of data which relies on the Browser to wrap. As noted, different browsers have different widths that that are using. Also the birth date entry should be 3 drop down menus (it makes entry easier). As an alternative to the use of tables, you can force wrapping by just ending each entry with a br /. I would have loved to knock it out in a table, but the widgets necessary by the third party are not set up for tables... at least I don't believe that are. Thanks, Michael When you talk about widgets I assume that you are using something to generate the HTML code for the page. If each entry is being generated individually, you might still be able to slip a br / before each label which will give you the wrapping that I suggested as an alternative to a table. If you are talking about server side scripting to process the form (and you code the page by hand) the use of tables will not affect what is being sent to the server. How is the page being generated (since I assume that there is some type of generation going on to slip a unique ID in for the hidden field)? __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Erratum
At 16:49 +0100 on 03/30/2011, Philip Taylor (Webmaster, Ret'd) wrote about [css-d] Erratum: Philip Taylor (Webmaster, Ret'd) wrote: Surely the goal is to write fully conformant documents that render reliably (if not necessarily consistently) in all mainstream browsers; if the alternative is to write non- conformant documents in order to pander to the inability of browser vendors to W3C specifications, then count me out, please. ... to pander to the inability of browser vendors to comply with W3C specifications I question if inability is the correct description. With some browser vendors IMO a more accurate term would be refusal. They can but do not for their own reasons. Their attitude, to paraphrase a famous movie line, is W3C Specifications? Our Browsers don't need to obey/conform-to no Stinking W3C Specifications. __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] slight layout change: center numbers in circles.
At 08:17 +0200 on 01/11/2011, Jukka K. Korpela wrote about Re: [css-d] slight layout change: center numbers in circles: Bob Rosenberg wrote: You can also just use the numbers in the U+2776-U+2793 range which will give you 1-10 as Serif numbers in black or white circles as well as Sans-Serif 1-10 in black circles. Why fool around when the characters exist in your fonts? On the theoretical side: because these characters are dingbats, i.e. specific graphics encoded as characters in a technical sense but not true text characters. On the practical side: because they mostly _don't_ exist in fonts. See the short font list at http://www.fileformat.info/info/unicode/char/2776/fontsupport.htm People's computers may have other fonts containing dingbats, but a) the appearances may be surprising and b) those fonts may have non-Unicode encodings. You are looking at the situation backwards. Admittedly the characters do not exist in every font. This does not however prevent them from being displayed. So long as the font-family that is active when the #x; entry is encountered AND one of the fonts listed exists on the user's system, the character SHOULD be displayed. I am not sure what the rules are when the first selected font does not contain the character but a subsequent one does (ie: Will it search the subsequent fonts for the character or just give up since it has found a prior font that is usable). The best solution is to ONLY list fonts that contain the needed character. Also make sure that for each platform (Mac, Windows, Linux) you list a system font with the character (ie: Those Fonts that are common to more than one platform or are always installed on a platform). For Windows and Macintosh listing Arial Unicode MS, ITC Zapf Dingbats, and Zapf Dingbats should insure that you will always find at least one available font on the user's system. I am not sure what font to use for Linux but I think that a Zapf Dingbats font exists there and will be installed. Note the to insure that the first available font is used, you should declare a CSS class (such as dingbat) that lists ONLY the fonts with the characters and code the #x; as span class=dingbat#x;/span. I hope this helps and explains my suggestion. -- Yucca, http://www.cs.tut.fi/~jkorpela/ __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] slight layout change: center numbers in circles.
At 13:53 -0500 on 01/10/2011, Rory Bernstein wrote about [css-d] slight layout change: center numbers in circles.: Hello All, http://mcgivney.ehclients.com/ On this page, you will see a big jQuery slideshow thing. I has some numbers in circles that let you select the slide to see. How can I get the numbers centered exactly in the circles? I can't seem to figure that out. Thank you, Rory You can also just use the numbers in the U+2776-U+2793 range which will give you 1-10 as Serif numbers in black or white circles as well as Sans-Serif 1-10 in black circles. Why fool around when the characters exist in your fonts? -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font-face, alignment issue similar to images
At 11:21 +1100 on 01/10/2011, Andrew Cunningham wrote about Re: [css-d] Font-face, alignment issue similar to images: Nancy, you are mixing encodings within a document. If you do want to use a character rather than an image, you should use the appropriate Unicode character, considering the website is UTF-8: U+260E Look for a font that has this character. It will also allow browsers on various operating systems to sue font fallback mechanisms if the browser can't use web fonts. By giving a number of font families you should be able to list one that will be on the user's machine. ITC Zapf Dingbats (or Zapf Dingbats) along with Arial Unicode would seem to insure that one is in the list for Windows and Macintosh. Wingdings is on the machines also (although I am not sure if it is Unicode Mapped). Linux is a separate issue but I think that there is a list of common fonts that might help. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] browser testing, and redirect.
At 17:59 +0800 on 12/25/2010, Chris Blake wrote about [css-d] browser testing, and redirect.: Hi, http://www.emw8.com/ Mac FF 3.5.16 gets the following PHP errors (which I assume you are aware of) but otherwise seems to work. Warning: imagejpeg() [function.imagejpeg]: Unable to open '/var/www/vhosts/emw8.com/httpdocs/cache/mod_novasfh/tmp/thb_websites.jpg' for writing in /var/www/vhosts/emw8.com/httpdocs/modules/mod_novasfh/helper.php on line 636 Warning: imagejpeg() [function.imagejpeg]: Unable to open '/var/www/vhosts/emw8.com/httpdocs/cache/mod_novasfh/tmp/thb_redrunner3d.jpg' for writing in /var/www/vhosts/emw8.com/httpdocs/modules/mod_novasfh/helper.php on line 636 Warning: imagejpeg() [function.imagejpeg]: Unable to open '/var/www/vhosts/emw8.com/httpdocs/cache/mod_novasfh/tmp/thb_yootheme.jpg' for writing in /var/www/vhosts/emw8.com/httpdocs/modules/mod_novasfh/helper.php on line 636 Also when I use the Default User Agent Plug-In to claim to be Win-IE6, I am NOT directed to http://www.emw8.com/index.php/en/ie6 but just get the normal page with no formatting or images. The same thing happens with Mac Safari 5.0.3 when I use the Develop Menu to tell the server I am Win-IE6. You might want to look at your PHP code to see (and report) the information being passed to the server when these emulate settings are used and how it differs from what is received when a real copy of Win-IE6 connects. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Vendor prefixes and validation
At 13:28 +0100 on 12/20/2010, Gabriele Romanato wrote about [css-d] Vendor prefixes and validation: In response to the criticisms moved against my CSS template #1, here's my point of view on that matter: http://onwebdev.blogspot.com/2010/12/css-vendor-prefixes-and-validation.html Part of the problem in my opinion is the broken nature of the validation routines. They reject as invalid any Vendor Prefix and thus reject as invalid any page that is otherwise valid. There should be switches that you can use to tell the Validator that it is to accept any vendor prefix as valid and just care about standard W3C-Blessed CSS. Vendor Prefixes are ignored by browsers that do not understand them (ie: FF ignores -ms-* and IE ignores -mozilla-*) and WHEN TOLD TO so should the W3C and other Validators. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Hack or conditional comments for small screen aps?
At 17:45 -0400 on 10/31/2010, David Laakso wrote about Re: [css-d] Hack or conditional comments for small screen a: On 10/31/10 5:04 PM, Nancy wrote: Is there a hack or conditional comment that would allow me to change the left positioning of the fixed menu when it is viewed on a cell phone browser? Thank you, Nancy You may want to consider using CSS3 Media Queries. t/ /http://www.w3.org/TR/css3-mediaqueries/#media0 Bruce Lawson-- mobile friendly http://dev.opera.com/articles/view/the-mobile-web-optimization-guide/ Smashing Magazine http://www.smashingmagazine.com/2010/07/19/how-to-use-css3-media-queries-to-create-a-mobile-version-of-your-website/ Stuff and Nonsense: CSS3 Media Queries http://stuffandnonsense.co.uk/blog/about/hardboiled_css3_media_queries Best, ~d Which is predicated on the expectation/hope that the cell phone's browser supports this level of CSS. A way to get the same result is via Server Side Scripting to send a tailored set of CSS. Note that I am NOT advocating this method but only pointing it out. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Fonts, fall-backs Unicode
At 8:51 PM +0900 on 07/13/2010, Philippe Wittenbergh wrote about Re:
[css-d] Fonts, fall-backs Unicode:
A modern OS / browser will do the job for you. You can specify a
fallback font if your first choice is not available:
p { font-family: font-a, font-b, font-c, serif;}
Gecko, WebKit, Opera, and IE 8+ will look for the glyphs in font-a,
if that doesn't have the coverage [*], the browser looks at font-b,
then font-c; if that fail, it takes the default serif font / or /
look for something in the list of installed fonts that provide
coverage.
The problem is two fold (in my opinion).
First is that unlike with printing use, there is no Font of Last
Resort fall-back. That support says to use the defined font BUT if
there are glyphs in the text which are not in the font then to
attempt to display them using the FoLR (ie: The only use of the FoLR
glyphs to display the missing codepoints).
The second problem is that there is no way to request that the
fall-back be done ONLY for missing codepoints (similar to the FoLR
support). In your example above, requesting one or more glyphs that
are not in font-a makes the browser try font-b and then font-c until
a font is found that has support for ALL the requested glyphs. If
none contain all the needed glyphs (even though all the glyphs exist
in the combined list of supported glyphs), you get the browser's
default serif with undefined codepoint glyphs for the codepoints
not in the serif font. What I think should be looked into for the
long term is defining a CSS font-x parm that says use font-a to
display those glyphs that it supports (assuming that the font exists
- non-existence is equivalent for this purpose as does not support a
glyph) and fall-back down the list for the remaining glyphs until
every glyph has been displayed by a suggested font or a missing
codepoint glyph gets defaulted to.
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Changes how (some) browsers handle the a:visited pseudo-class
At 09:20 +0900 on 04/10/2010, Philippe Wittenbergh wrote about [css-d] Changes how (some) browsers handle the a:visited ps: In short, those browsers will limit the ways the a:visited state can be styled. Color, background-color, and to some extend, outline, border are not affected, as long as you don't use alpha-transparency (rgba()), change the border-style or border-width, etc. Other changes will be ignored and fall back to what is specified for the a:link state. Am I reading this to say that font-* (such as style and weight, etc.) will be ignored and set to the :link value even when different in the :visited version? -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Changes how (some) browsers handle the a:visited pseudo-class
At 07:19 +0100 on 04/10/2010, Philip TAYLOR wrote about Re: [css-d]
Changes how (some) browsers handle the a:visite:
A user-controllable feature within the browser, on the other hand,
would provide a convenient way of working around any deficienc{y|ies}
in the specification(s) whilst still allowing the user to have a
fully compliant browser if he/she so wishes.
Also IMO the feature should be OFF unless the user SPECIFICALLY
activates it (not set to ON requiring the user to turn it off to
cripple it).
IOW: If you want to have the Browser play Net Nanny then require the
user to give permission not do it behind the user's back until the
browser is told to stop messing with the page/code and display it as
supplied.
--
Bob Rosenberg
RockMUG Webmaster
webmas...@rockmug.org
www.RockMUG.org
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] doctype
At 12:47 +0200 on 04/01/2010, MB wrote about Re: [css-d] doctype: Chris Blake told: Sorry! This document can not be checked. When i try to validate anything that is UTF8. If you kept reading you would see that the validation page says further down: I am unable to validate this document because on line 35 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding) This means your file contains erroneus characters. What I usually do is to start a new utf-8 encoded HTML-file and start anew. If I have a more full source-file I copy the source and start a new utf-8 encoded HTML-file in my editor and paste the source code into that. Sometimes the erroneus characters may follow with the copy process. In that case you have to make sure you copy only valid parts. This line should read A l l c o n t e n t copy; 2 0 1 0 W C H ... and it will be OK. The problem is that there is a literal © pasted there and this is an invalid UTF-8 character (since it is High-ASCII and thus needs to be UTF-8 Encoded - Use of copy; fixes this issue). -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transcendant web design and CSS3
At 19:40 -0500 on 03/07/2010, Freelance Traveller wrote about Re: [css-d] Transcendant web design and CSS3: Thank you; this does indeed appear to be quite useful - and tells me that CSS3 is not ready for prime time, and probably should not yet be used as I'd like to use it. It is not ready for prime time and will not be ready for the foreseeable future due to the need to serve to IE Browsers. So long as you can ignore IE support (or can serve a stripped down version to the IE holdout users) you can according to the chart use it now since all the other browsers currently support it (or do with all but obsolete versions). -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] FW: bemstrongi tags
At 20:08 + on 03/06/2010, Philip TAYLOR (Ret'd) wrote about Re:
[css-d] FW: bemstrongi tags:
Thierry Koblentz wrote:
fwiw, I don't agree.
If an author wants italics or bold then heemshould/em,
strongmust/strong, usei andb.
To stay on-topic I won't mention semantics (should be a no brainer though),
but CSS: a User Agent does *not* have to makeem italics andstrong
bold, but it has to fori andb.
Although I don't disagree with your underlying premiss,
I do disagree with your conclusions. A User Agent is no
more obliged to render i elements in italics, or
b elements in bold, than it is required to set off
p elements by vertical white space. CSS gives
both author and consumer the opportunity (or right,
or privilege : call it what you will) to override
any of those default renderings, as in :
I {font-style: normal; font-weight: bold}
B {font-style: italic; font-weight: normal}
P {margin-top: 0ex; margin-bottom: 0ex}
Philip Taylor
You are confusing two issues. What the statement you are replying to
said was that i and b will ALWAYS be displayed as respectively
italic and bold by the UA/Browser. em and strong on the other
hand will display in whatever style the Designer of the UA/Browser
decided they should (although the usual method is italic and bold
respectively).
This is how the displays work UNLESS you override the decision of the
UA via use of CSS rules. When you say A User Agent is no more
obliged to render i elements in italics, or b elements in bold
... you are incorrect. In the absence of a CSS override i and b
ARE orders to display in italic or bold.
CSS is a way of changing the built-in defaults for how to display
text enclosed in the different tags.
Bob Rosenberg
RockMUG Webmaster
webmas...@rockmug.org
www.RockMUG.org
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Deprecations in recent versions of HTML cause CSS problems?
At 18:42 -0800 on 02/09/2010, Theresa Mesa wrote about Re: [css-d] Deprecations in recent versions of HTML cause C: One thing you must consider, too, is that on the web, you should only underline something that is an actual link Which is ALSO displayed in BLUE (or the user's selected LINK color) and will have a cursor change when hovered over. Thus an underlined BLACK phrase is NOT identified as a hot link due to its non-link color and non-cursor-altering hover result. BTW: There are a number of cases where the use of an underline AS an underline occurs by using the link color and a dot underline for the real links. If underlining needs to be reserved FOR underlining, the use of an A CSS Rule to dot underline and color the links should handle the possible confusion. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] [OT] RE: u/u - why did it have to die?
At 13:23 -0800 on 01/15/2010, Thierry Koblentz wrote about Re: [css-d] [OT] RE: u/u - why did it have to die?: I don't agree. RADAR is an acronym because you're not supposed to spell the letters. CPU is an initialism, because you are supposed to spell the letters. Considering CPU (or else) as both an acronym and initialism would allow two different pronunciations. Initialisms are a subset of Acronyms - IOW: All Initialisms are Acronyms since both stand for the initial letter(s) of a phrase (RAdio Detection And Ranging and Central Processing Unit respectively). The way the string is pronounced determines where an Acronym is also an Initialism. The pronunciation does NOT prevent a Initialism from being an Acronym. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Bold not working
At 11:01 -0400 on 08/25/2009, Brian M. Curran wrote about [css-d] Bold not working: My CSS validated, but making my text bold for the picture links on my portfolio page isn't working via the pseudo class selectors. Does someone have a minute to give it a glance? http://www.brianmcurran.com/portfolio.html One tip that I have found on an issue of this type (ie: Is the CSS being used?) is to add something such as a color definition to that selector definition. Thus if the text changes to the correct color you know that your selector is being used. You could also try italic in lieu of bold for the same test. That catches the case where a later CSS definition is resetting you back to normal. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] the old 'tables vs. divs'
At 19:36 +0100 on 08/01/2009, MEM wrote about Re: [css-d] the old 'tables vs. divs': I was studying the CSS and the page structure and I noticed that the designer used a series of table cels to create that design. Not only will the page not validate but I wondered what you guys have to say about the notion of using tables to affect this design? I'm like a robot on that: tables, for tabular data. Is the layout structure tabular data? No. CSS will do it. Except for the fact that in some cases CSS is (currently?) incapable of creating the same layout as can be created with a Table (Maybe CSS3 will be able to once it gets rolled out in a few years). -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] the old 'tables vs. divs'
At 19:40 +0100 on 08/01/2009, Christian Heilmann wrote about Re: [css-d] the old 'tables vs. divs': Todd Bingham wrote: Gentlemen, This is not my site, but I went there as a result of a tutorial I was taking on Lynda.com. http://www.nypl.org/ I was studying the CSS and the page structure and I noticed that the designer used a series of table cels to create that design. Not only will the page not validate but I wondered what you guys have to say about the notion of using tables to affect this design? I'd appreciate any comments because I have an old site I did for a client who recently heard the phrase 'table-less' and is bugging me about changing it over, and I'm afraid he's thinking it should be on my nickel. What do you all think.. http://www.shouldiusetablesforlayout.com/ Which responds with a blanket NO ignoring the possibility that there may be layouts that can be done via Tables but is impossible to create via CSS. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Removing the Blank Line/Space between Paragraphs
I use the text-indent CSS parm to indent the first line of each paragraph. I have been requested to remove the blank line/space that occurs between paragraphs triggered by the /pp sequence of tags so the lines occur as one block of text with only the indention and the short line at the end of each paragraph signaling the paragraphs. Is there a CSS parm I can use to eliminate the blank line between the paragraphs and, if so, what parm do I use? Thank you. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Removing the Blank Line/Space between Paragraphs
At 16:13 +0900 on 07/26/2009, Philippe Wittenbergh wrote about Re:
[css-d] Removing the Blank Line/Space between Paragraph:
On Jul 26, 2009, at 3:46 PM, Bob Rosenberg wrote:
I use the text-indent CSS parm to indent the first line of each
paragraph. I have been requested to remove the blank line/space that
occurs between paragraphs triggered by the /pp sequence of tags
so the lines occur as one block of text with only the indention and
the short line at the end of each paragraph signaling the paragraphs.
Is there a CSS parm I can use to eliminate the blank line between the
paragraphs and, if so, what parm do I use?
parm ? You probably mean 'property'.
Yes. I am just used to thinking of them as parameters (like with HTML
Tags). They are basically the same thing.
p {margin:0;} ought to do what you want.
http://www.w3.org/TR/CSS21/box.html#margin-properties
Thanks. That did it.
Philippe
---
Philippe Wittenbergh
http://l-c-n.com/
--
Bob Rosenberg
RockMUG Webmaster
webmas...@rockmug.org
www.RockMUG.org
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Problem with all Mac browsers according to BrowserCam
At 20:47 -0500 on 07/18/2009, Reese wrote about Re: [css-d] Problem with all Mac browsers according to Brow: It isn't asnSEO-friendly as text links and SEO-friendliness is important. So long as each image has an ALT tag with the text, the SEO Police should be reading it and treating it as if it were the text itself. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] firefox problem
At 15:55 +0100 on 07/08/2009, David Dorward wrote about Re: [css-d] firefox problem: The second thing to deal with is the syntax errors: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.hcam.net%2Fposts.htmlcharset=%28detect+automatically%29doctype=Inlinegroup=0 Once you've dealt with the machine detectable errors, then start worrying about browsers rendering things other than as you expect. They are NOT syntax errors per-sa but harmless Markup from his WebDesign program. They can be automatically eliminated from the copy uploaded to the Web Site (while leaving them in the master copy on his computer) by having the WebDesign program create a clean copy for manual uploading or having it clean the copy it uploads itself. This is the same type of crud that Office creates when it outputs HTML so that the HTML can be round-trip read back into Office as if it were a .DOC not a .HTM/.HTML format file. There are no REAL (ie: HTML statement) syntax errors there only non-HTML tags. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] List bullet sizes
At 23:30 -0400 on 07/07/2009, Stephen Tang wrote about Re: [css-d]
List bullet sizes:
On Tue, Jul 7, 2009 at 6:34 PM, Daniel Navarrowebpe...@gmail.com wrote:
Hi,
li {
list-style-type: none; /* remove default bullets */
}
li:before {
content: \2022; /* hex codification bull; */
color: blue;
margin-right: 0.3em;
}
(this doesn't work in IE6)
Broken IE6 strikes again. Since this is IMO the correct solution/way
to insure the correct bullet gets used, why not use it and use a
conditional statement to tell IE6 to just do its own thing by not
doing these overrides.
--
Bob Rosenberg
RockMUG Webmaster
webmas...@rockmug.org
www.RockMUG.org
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Alignment issue
At 09:59 -0800 on 11/22/2006, Russ Peters wrote about [css-d] Alignment issue: http://www.redcanoecu.com/index1.asp This gets a error message. The text is: There was error while processing your request. Please try again. Contact Red Canoe Credit Union at 800-562-5611 or email i...@redcanoecu.com if you continue to receive this error or try a search. Also, in IE6 if you go from the home page to the LOANS page do you get an error message? I keep an error only in IE6 and it's so vague that I can't pinpoint the problem. I'm still working on that one...but if you see something there I'd love to hear it. When I go to your index.asp page (which I assume is the index1.asp page without modifications, you have the following tags which, since you are XHTML, should be lower case (they get validation errors): META HTTP-EQUIV=Pragma CONTENT=no-cache META HTTP-EQUIV=Expires CONTENT=-1 They should be: meta http-equiv=pragma content=no-cache meta http-equiv=expires content=-1 -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] CSS Menu Over Many Web Pages in a Site
At 17:20 -0500 on 04/04/2009, Wayne Wickson wrote about [css-d] CSS Menu Over Many Web Pages in a Site: I'm new to CSS, but a conceptual problem has occurred to me. If this is a stupid question, please humour me. Lets assume I am designing a web site of one hundred pages. I design a horizontal dropdown menu which links to each of the one hundred pages. So each page is available from each of the other pages. I need to add a new page or several pages. Is there a way, using only CSS, to easily change the menu on each of the one hundred pages on the site without actually using an editor and modifying the one hundred lists one list at a time? Thanks for any help I receive. If you are willing to require that your users are not paranoid enough to cripple their Browser's JavaScript support, you can do this by just generating the navigation menu with a JavaScript (you update the script with the new links and they get inserted as the page loads). This method will also allow the link to the current page to have its own CSS Definition so it will display differently to indicate that it is the link for the current page (this is done by assigning a different class if the page-id matches the href link - it can also cause that link to just have the link text without the A tag). If you use a design tool like BBEdit, GoLive, Dreamweaver, etc., it can insert the menu from a separate file that is inserted into each page. When you update that file, all the pages are automatically rewritten (and then just need to be re-uploaded to your site). -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font size dilemma
At 11:01 + on 03/13/2009, Bobby Jack wrote about Re: [css-d] Font size dilemma: Having said all that, I don't think we need to be too dogmatic about it. Web pages are NOT the same as books - I believe there should be more of a visual identity to a site than just a logo and a couple of images. If browsers did a better job of handling font-sizing, every web site could easily be readable by all whilst maintaining a unique look of its own, even in regards to the 'base' font size. In some ways CSS is a step backwards on this issue from the old HTML FONT tag. With FONT ... you display in the USER'S defined font size and increase/decrease the display via the SIZE parm. With CSS you can get the same result via use of EM or % sizes but using PT (or other measures that ignore the user's default font size) causes the user's settings to be overridden and ignored. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font size dilemma
At 21:26 -0400 on 03/14/2009, Felix Miata wrote about Re: [css-d] Font size dilemma: It's also possible for fonts to show up at the preferred size, regardless how large or small that happens to be. It's also possible that the difficulties resulting from common too small fonts will be reduced or eliminated. There is also the problem that the character height on a site designed on a Windows Machine makes the characters look smaller on a Macintosh Computer (to get the same image size on the Mac you must bump the size up one notch). This has to do with the 96dpi font sizing on the Windows Machine requiring larger letters than the Macintosh fonts which are based on 72dpi measurements. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font size dilemma
At 16:59 +0100 on 03/15/2009, =?ISO-8859-1?Q?Gunlaug_S=F8rtun?= wrote about Re: [css-d] Font size dilemma: 6: if a printed work has too small text, the end-user can either use a magnifying glass or throw the entire work into the fireplace. Or just buy the book (or get it from your local public library) as a LPE (Large Print Edition - ie: 16pt type [like the children's books use]) in the first place. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css, in place of javascript
At 00:29 +1100 on 03/08/2009, karla pringle wrote about Re: [css-d] css, in place of javascript: Is there a way to rollover an image and have text elsewhere on the page apply a hover attribute. for example I mouse over an image on the page and the text below is highlighted. How about: a href=# id=Ximg ...brText/a and doing the CSS hover to point at X? -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Centering images with caption in a column
At 15:09 -1000 on 01/01/2009, david wrote about Re: [css-d] Centering images with caption in a column: As long as visitors (like me) can use their browsers at widths narrower than 1024, we should accommodate them. Also, the web reaches beyond the desktop. Users of iPhones/iTouches and other mobile browsing devices don't have a choice. That difference is what the media=handheld parm is for. To support iPhones/etc. you just have a separate set of CSS definitions that takes the limited screen width into account. -- Bob Rosenberg RockMUG Webmaster webmas...@rockmug.org www.RockMUG.org __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] declaration specificity - less-specific line overrides more-specific line?
At 08:36 + on 10/13/2008, Bobby Jack wrote about Re: [css-d]
declaration specificity - less-specific line ov:
On Oct 12, 2008, at 11:25 AM, Erik Harris wrote:
I've got a ul element buried with this
hierarchy:
div#sidebar ul li#pages ul
I've got the following two lines in my stylesheet:
#sidebar ul ul {margin: 5px 0 0 10px;}
#pages ul {margin: 0em; padding: 0em;}
Despite the fact that it seems that the second line
should be more
specific (#pages is more specific because it's
deeper in the
hierarchy),
--- On Sun, 10/12/08, Philippe Wittenbergh [EMAIL PROTECTED] wrote:
#sidebar ul ul : a=1 b=0 c=2 -- 102
#pages ul a=1 b=0 c=1 -- 101
http://www.w3.org/TR/css3-selectors/#specificity
Just to expand on Philippe's brief (although totally correct) explanation:
CSS does not take hierarchy into account when calculating
specificity, however illogical that might seem. The first rule
'wins' merely because of the additional 'ul'. You could rewrite that
second selector #sidebar #pages ul to resolve this issue.
This change wins because it scores 201 (2 IDs). The problem with
the scoring (as you note) is that if the first had one one ul, both
would score 101 and hierarchy in theory need to come into play to
select. If I remember correctly, the order of encounter of the rules
is what ends up getting used as the tie-breaker in the case of
duplicate scores (ie: Either the first or last winning rule). A
better method (at least for tie-breaking if not specificity) is to
use the hierarchy (ie: Which one is included in the range covered by
the other as if they were nested SPANs).
- Bobby
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
--
Bob Rosenberg
RockMUG Webmaster
[EMAIL PROTECTED]
www.RockMUG.org
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Overflow and no
At 11:14 AM -0600 on 10/7/08, Jack Blankenships wrote about [css-d] Overflow and no: Any ideas on how to have an element's overflow property apply to some children but not to others? For example, I have a div that contains a table/grid that I want to have set to overflow: auto on a specific height. This way the results stay within a specific set of dimensions and do not push the rest of the layout into undesirable locations. The problem is that I also want to include some css tooltips for specific cells in this table/grid, some of which are large enough that I would like to expand them out of this standard boundary because they would be displayed above the layout content and disappear when :hover is not activated. Thanks, Jack You might try creating a Class definition with the overflow setting you want for the special cells and add the class= parm to those cells. This SHOULD override the setting inherited from the div. -- Bob Rosenberg RockMUG Webmaster [EMAIL PROTECTED] www.RockMUG.org __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] start an ordered list at a number 1
At 18:22 -0500 on 02/07/2008, Tim White wrote about Re: [css-d] start an ordered list at a number 1: You can use ol start=x (whatever number you need) to start a list at a new number. Or, you can use li value=x to skip numbering within a list. Both attributes are deprecated, so they are only valid under HTML 4.01 or XHTML 1.0 Transitional. OTOH, by use of an ID= on the LI, you can use a CSS command to [re]set the index value. -- Bob Rosenberg RockMUG Webmaster [EMAIL PROTECTED] www.RockMUG.org __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Transitional Vs. Strict Doctype
At 09:46 -0800 on 02/06/2008, Elli Vizcaino wrote about [css-d] Transitional Vs. Strict Doctype: Hello List, Not sure if this would fall under off topic. But I wanted to know what the reasons are for using a strict doc type as opposed to transitional. I use strict in my documents but wondered why it seems to be a bad idea to go with transitional as I've seen a couple of topics graze the issue from time to time. Can someone elaborate? And if this is off-topic please email me off list. TIA, Elli Aside from the different treatment of CSS with the two Doctypes, the simplistic answer is that if you use depreciated tags (ie: Those that have been declared illegal in Strict) you need to use Transitional when they are occur in your HTML. -- Bob Rosenberg RockMUG Webmaster [EMAIL PROTECTED] www.RockMUG.org __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] How will firefox 3 affect web developers?
At 11:31 -0800 on 11/29/2007, David Hucklesby wrote about Re: [css-d] How will firefox 3 affect web developers?: As for content, you don't say whether FF 3 is available on Mac? Yes. -- Bob Rosenberg RockMUG Webmaster [EMAIL PROTECTED] www.RockMUG.org __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] clearfix tweak needed on IE7
At 11:00 AM -0700 on 10/6/07, David Hucklesby wrote about Re: [css-d]
clearfix tweak needed on IE7:
Of course, you could simply use:
.clearfix {zoom: 1;}
since only IE 5/6/7 Win recognize zoom.
Won't fix IE 5.01 Win though. You will still need the height: 1%;
if you care about that browser.
You can support IE5 with an IF IE5 clause with IE6/7 getting its
clearfix via another IF that only checks for IE6+.
--
Bob Rosenberg
RockMUG Webmaster
[EMAIL PROTECTED]
www.RockMUG.org
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] IE6 Back function fubar?
Thanks to some great advice from list members, I have a (large) file
up and running with a fixed menu that *stays* fixed in IE6.
[http://users.rcn.com/rtberg2/hp_ctr.html] But now I find that the
Back function doesn't work in IE6! Does anyone have any insight
into this sort of problem? It happens on another file that uses the
same construction, which I've sketched below. The solution I arrived
at for the fixed menu is to have a duplicate menu nav *outside*
container1 that only shows up in IE6--nav1 is for everyone
else. Everything works like a charm except for the Back problem.
Any hard-won wisdom on this one?
Thanks.
--Bob R.
***
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
head
style
. . .
#nav {display: none;}
#nav1 {font-size: 80%; width: 25%; position: fixed; left: 2%; top: 85px;}
. . .
/style
!--[if IE 6]
style type=text/css
body {height: 100%; overflow: hidden; padding: 0px; margin: 0px; }
#container1 {height: 100%; overflow: auto; position: relative; z-index: 1;}
#nav {display: block; font-size: 80%; width: 20%; position: absolute;
left: 5%; top: 80px; z-index: 2;}
#nav1 {display: none;}
/style
![endif]--
/head
body
div id=nav
list
list
. . .
/div
div id=container1
image
div id=container
div id=nav1
list
list
. . .
/div
div id=content
. . .
Lots of good stuff (6MB worth)
. . .
/div
/div
/div
/body
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Ah, hell
Please ignore that last post. Eudora mangled the illustration. I'll try again. --Bob R. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] IE6 Back function fubar?
Thanks to some great advice from list members, I have a (large) file
up and running with a fixed menu that *stays* fixed in IE6.
[http://users.rcn.com/rtberg2/hp_ctr.html] But now I find that the
Back function doesn't work in IE6! Does anyone have any insight
into this sort of problem? It happens on another file that uses the
same construction, which I've sketched below. The solution I arrived
at for the fixed menu is to have a duplicate menu nav *outside*
container1 that only shows up in IE6--nav1 is for everyone
else. Everything works like a charm except for the Back problem.
It's the xhtml1-transitional DTD. (I've had to replace the angle
brackets below with square brackets to keep Eudora happy.)
Any hard-won wisdom on this one?
Thanks.
--Bob R.
***
[style type=text/css]
. . .
#nav {display: none;}
#nav1 {font-size: 80%; width: 25%; position: fixed; left: 2%; top: 85px;}
. . .
[/style]
[!--[if IE 6]]
[style type=text/css]
body {height: 100%; overflow: hidden; padding: 0px; margin: 0px; }
#container1 {height: 100%; overflow: auto; position: relative; z-index: 1;}
#nav {display: block; font-size: 80%; width: 20%; position: absolute;
left: 5%; top: 80px; z-index: 2;}
#nav1 {display: none;}
[/style]
[![endif]--]
[/head]
[body]
[div id=nav]
. . .
[/div]
[div id=container1]
image
[div id=container]
[div id=nav1]
. . .
[/div]
[div id=content]
. . . Lots of good stuff (6MB worth) . . .
[/div]
[/div]
[/div]
[/body]
__
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] IE6 Non-Existant Class Bug
At 12:59 -0400 on 09/26/2007, Seth Green wrote about [css-d] IE6 Non-Existant Class Bug: As you will see if you load the page below... In IE6 the div remains red, even though it is explicitly set to green in the last rule. It seems that the middle rule, which targets a non-existant class is causing the problem. Remove that, and the div is green, even in IE6. Note: If instead of using the additional class selector in the last rule, I just use the id, then this problem also goes away. Has anyone ever experienced this issue? Is there a workaround? Yes. Embed the correct version of the rule on the page. ID has to be unique on the page so IE6 is correct in stopping on the mismatch since when it finds the ID'ed tag with the wrong class on it since there can not be another tag with that ID to match. While it is theoretically valid to have more than one possible match, this would only be valid if the rules occur in a *.css Style Sheet. In that case, at least in theory, the rules could be intended to apply to different pages and should thus the rules should be fully parsed. Also, again at least in theory, if you rewrite the DOM text (and thus alter the class), the mismatch should NOT stop the parse. -- Bob Rosenberg RockMUG Webmaster [EMAIL PROTECTED] www.RockMUG.org __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] fixed div in IE6
Greetings: I hope this is not too trivial for comment, but searching for it in the archive has proved fruitless--it's just too hard to narrow down the search. On a page like http://users.rcn.com/rtberg/Adam/animag1.htm I have a left-column menu (div id=nav) that stays nicely fixed in FF or IE7 (for example), but which will not behave in IE6. It's a big file, but it's not complex HTML or CSS, and in IE6 I simply cannot make #nav hold still (or, for that matter, even show up in the left column). I do not want a second scroll bar on the page. I have tried fixes found on CSS advice websites (like http://divinentd.com/experiments/emulating-position-fixed.html), but at best they give me ugly double scroll bars. The CSS is at the top of the document. Thanks for any help offered. --Bob R. PS: And thank you for not suggesting that I break the file into smaller pieces. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Insertions rather than popups
Greetings: I'm working on a large document with translations and footnotes, and I do not want popup windows. Instead, I have the text appearing in place (mockup sample at http://users.rcn.com/rtberg/try_me.html), using javascript and enclosing the note or translation text--which is sometimes fairly structured--in object tags. Is there a way to do this with pure CSS and no javascript? (I'm new to the list, and I searched the archive with popup, but that didn't help much. My apologies if this is old hat.) Thanks. --Bob R. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Insertions rather than popups (reprise)
I'm sorry--I should have noted that right now the sample does not work in IE6. That's a problem for another day. Probably the day after I settle this one. --Bob R. __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] How can I do an image overlap with CSS?
At 21:35 -0700 on 06/17/2006, Robert Lane wrote about Re: [css-d] How can I do an image overlap with CSS?: Well those lines lost it in transmission - sorry. Basically I want Img A Img B where Img B overlaps and covers the lower right 2/3 of Img A. Cheat. Bring the two picture into Photoshop and put Image A in Layer 1, Image B in Layer 2, and save a flattened copy. Use the copy in your layout. -- Bob Rosenberg RockMUG Webmaster [EMAIL PROTECTED] www.RockMUG.org __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
