Jump to content

F-Man

Members
  • Content Count

    222
  • Joined

  • Last visited

Everything posted by F-Man

  1. Or make your site work well on any resolution as it should.
  2. Well let's say you wanted your headings to be in bracket [like this]. You could do:h1:before { content: "["; }h1:after { content: "]"; }Also you can decide to disable or enable quotation marks around quotes like this:q:before { content: open-quote; }q:after { content: close-quote; }You can also use p:after { content: url(image.gif); } to place some signature image at the end of a paragraph, and so on.
  3. a#leftcol is if your anchor has that ID. Instead you have a division with that ID, so you're probably looking for something like#leftcol a { color: red }ordiv#leftcol a { color: red }Also, leftcol is not a good name for an ID. ID and class names are part of the HTML and therefore should relate to content and not presentation. You never know if you want to change your "leftcol" to actually go to the right someday.
  4. F-Man

    two Background

    Put one div inside another. Apply "background: url(image.jpg) no-repeat scroll bottom left" to one and "background: url(image.jpg) no-repeat scroll bottom right" to the other.
  5. The object tag has no required attribute.
  6. The classid/codebase use an ActiveX control to embed WMP inside IE, so of course that does not work in Firefox. Try to just embed the file with its appropriate MIME type (probably type="video/x-ms-wmv") and get rid of the classid plus codebase. Then see if that works (also pretty much all params will probably become useless as they all rely on the WMP to work).Also, yeah, use XHTML 1.0 Strict.
  7. I don't think he wants to insert paragraph inside his cells (in fact that'd be stupid). td { font-size: 80%;}
  8. Specify a background-color, of course. Though I personnally think it's useless...background-color: transparent should be good enough, but since that validator sucks it'll give you the warning anyway I think. So you're left with background-color: inherit, which takes the same bg color as the parent element.
  9. ...Wow.That's really shooting in accessibility's foot.
  10. CSS is for style only. Browser behaviour is for DOM scripting.
  11. F-Man

    Iframes

    Go to your page with the image, and add this CSS in the head: <style type="text/css">body { margin: 0;}</style>
  12. Use percentage values. width="70%" per example.
  13. F-Man

    CSS2 with CSS1

    IE7 will support PNG alpha transparency, as seen in the link I posted above.Also, Firefox will also increase images size if you specify their size in ems; something that should be done more often but isn't because HTML only supports pixel units, oppositely to CSS.
  14. F-Man

    IE woes

    Wrong. Using the XHTML DOCTYPE with a .html extension is for HTML compatibility mode, so that your page can work in most browsers and will only need you to change the extension or the MIME type through your server settings if you want to use true XHTML in the future.Anyway, we're really off-topic here.EDIT: Yeah, if you want to use XHTML that is, this should have been the case in 1999 but IE really is slow.
  15. F-Man

    IE woes

    Because it is an XML only.http://www.w3.org/TR/2002/NOTE-xhtml-media...020801/#summaryXHTML 1.0 may be used with the text/html MIME type (.html, .htm extensions) for compatibility reasons, as long as you follow Appendix C of the spec, but this makes XHTML totally unextensible and therefore loses its purpose, which is why the W3C decided to make every new version of XHTML application/xhtml+xml (.xhtml, .xht extensions) only (and other generic XML MIME types (.xml extension for example)).
  16. XHTML 1.0 Frameset or HTML 4.01 Frameset.Btw, DTD Declarations = Document Type Declaration Declarations.
  17. F-Man

    IE woes

    XHTML 1.1 as HTML text = no-noUse XHTML 1.0 Strict instead.Also, instead of JavaScript, you should try just to use padding-left on your links and a background-image. Then using the :hover pseudo-class, make it so that the background-image changes. I usually never have IE problems with that (except IE 5.0 that doesn't like padding on inline elements...).
  18. No problem.Also that's because I set it as an object parameter, and not as an attribute.
  19. ^Because of the different way browsers treat file type inputs, this is not quite recommended. If I remember well, Safari displays them very differently...
  20. A select menu is vertical. If you want something horizontal try radio buttons.
  21. Valid way that works in all mainstream browsers: <object data="/Buttons/chargeworks.swf" type="application/x-shockwave-flash" width="200" height="90"> <param name="movie" value="/Buttons/chargeworks.swf"> Alternate content for people who don't have Flash player, it can be as much HTML as you want.</object>
  22. F-Man

    margins with <span>

    Looks to me that you should be using an unordered list instead. <ul>Then you could give a left margin or padding to every <li> inside that list. If you want to remove the bullets, you can use CSS list-style-type: none; <h2>History</h2><ul id="example"> <li>Western Society for Pediatric Research (Member of Council 1971-74)</li> <li>Association of Medical School Pediatric Chairmen, Inc., California Chapter Organizer and Administrative Officer, 1983-88</li> <li>Special Recognition Award for Services to the Department of Pediatrics
  23. Copy and paste your stylesheet here so we can take a look at it.
  24. F-Man

    CSS2 with CSS1

    Firefox 1.5 has surpassed Opera in CSS support by just a little bit, but that's mainly because of its CSS3 support.Personally I prefer Firefox over Opera, because Opera is way too bloated. Firefox is completely open-source so if there's a feature you want you can just download it, even features not included in the hundreds that Opera has!By the way, IE7's CSS2 support will be much more improved.
  25. CSS values should not be in quotes.Also, you html closing tag (at the very end) is actually an opening tag.
×
×
  • Create New...