Frank P
-
Posts
168 -
Joined
-
Last visited
Everything posted by Frank P
-
@droidus: You could save all of us a lot of time if you could either put it online, or post the whole code, in one code block, stripped of all irrelevant matters.
-
How about the doctype/standards mode?
-
Have a look here: How to Get 100% Height in CSS. There are three objectives with 100% height, with solutions for all, in the tutorial.
-
Generally it is because the browser, IE usually, is in quirks mode, in which mode it doesn't render margin:auto. Make sure to have a valid and standards mode-eliciting doctype and nothing above it. Not even a comment.
-
Freakie, That page that you linked to from there, why is that a sticky footer? If I make the browser window a bit smaller, the footer disappears. See http://prntscr.com/35v1d.
-
I haven't tried it yet, but this may be what you're looking for: http://blog.mapmyglobe.com/css-text-stroke/. It is Javascript-based.
-
You gave the container a max-width of 1000px and a min-width of 700px. Just change the two into a (fixed) width of 980px. That way you're sure that also with a not fully maximized window there still will not appear a horizontal scrollbars on a 1024 screen.
-
OK, but like I wrote, if I convert your code to valid and rendered code, and change the wrapper width to 980px, there does not seem to be a problem. Perfectly centered and vertically lined up without any horizontal scrollbars.
-
There's nothing in your code that would generate the black lines, and if I convert your code to valid and rendered code, and change the wrapper width to 980px, there does not seem to be a problem: <!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> <title>Demo</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <style type="text/css"> body{ background: pink url(../images/bg_top.gif) repeat-x 0 0; font-family: 'Droid Sans', arial, serif; font-size:12px; color:#333; } #wrapper{ width:980px; /* from 1052px */ margin:0 auto; } #header{ width:100%; /* not necessary, delete if border or padding is added */ height:177px; background: blue url(../images/header_bg.jpg) no-repeat; } #main{ background: green url(../images/content_bg.png) repeat-y; padding:13px 55px; position:relative; min-height:400px; z-index:1; } </style> </head> <body> <div id="wrapper"> <div id="header"></div> <div id="main"></div> </div> </body> </html>
-
Where? Which black line?
-
Properties with prefixes like -moz- and -webkit- are non-standard properties. Having said that, I don't care much about valid CSS. My websites always have valid HTML, but I only use the CSS validator if I have a problem and want to see if maybe I misplaced a character or something like that. Confining oneself to valid CSS takes away far too much creative and economical techniques.
-
Broken link: W3 Validator testresults. No less than 49 errors, with a number of them serious ones...
-
Connecting wasn't a problem, but your code is: W3 Validator. The best advice I can give is to start (anew) learning to write html/css, via http://htmldog.com and/or http://w3schools.com. Both free.
-
New 'READ BEFORE POSTING' for HTML and CSS forums
Frank P replied to Frank P's topic in PHPFreaks.com Website Feedback
Pop! Cheers! I will indeed wait until a mod or admin joins this thread, also for the final draft, because maybe s/he wants something altered. -
How to make the fallback font italic, but not the imported font
Frank P replied to tommybfisher's topic in CSS Help
In principle, the fonts installed locally (on your server) and invoked with an @font-face rule will indeed always be downloaded and rendered. And unless your site doesn't have a separate page for mobile phones (which it should have), you could take the chance that there will be a handful of visitors with browsers that don't support @font-face. -
Your link is broken and I don't understand your question. Why don't you just open your stylesheet with e.g. Notepad and have it printed from there (File | Print)?
-
They indeed do, but jQuery would be a humongous overkill here.
-
How to make the fallback font italic, but not the imported font
Frank P replied to tommybfisher's topic in CSS Help
On my machines, Vista Basic and XP Pro, there is a separate Georgia Italic installed. And I didn't do that myself, so at least when it concerns Windows computer, you should be able to just write "Georgia Italic". -
New 'READ BEFORE POSTING' for HTML and CSS forums
Frank P replied to Frank P's topic in PHPFreaks.com Website Feedback
'over the message forum' should have been: 'over the message form'. -
New 'READ BEFORE POSTING' for HTML and CSS forums
Frank P replied to Frank P's topic in PHPFreaks.com Website Feedback
@CssFreakie: Glad you like the overall idea. You're saying: "a guideline for posting () as far as it is not already mentioned in the general guidelines", but the bad posts are generally from people who are in a hurry and/or who don't like reading. Those people are even less likely to read the general guidelines. That's why I'm proposing this sticky, which is much shorter. Regarding the title, that could also be in normal letters. Matters are not as bad here, and if need be we can always put a line directly over the message forum, directing newcomers to it. I can imagine you'd want to confer with your co-moderators. Just let me know what I should do further. [side note 1: the 'ones' in e.g. 'the list I ones provided' and 'But ones you played around with it' should be 'once'. Side note 2: only now do I see the male gender sign under your name. No more 'his/her' from me. ] -
Hi, Its is a perfectly normal question, but where did you see it? Must have been on a website, but why didn't you look in the source code of that page? If you don't know how to do that or how to read source code, it will be impossible for your to implement any code that we would give you here. Because it indeed is a combination of javascript and css, called dynamic html (DHTML).
-
New 'READ BEFORE POSTING' for HTML and CSS forums
Frank P replied to Frank P's topic in PHPFreaks.com Website Feedback
I have the illusion that with these points it will get significantly less, even though I must say -- or should have said to begin with -- that it is not as bad on PHP forums as it is on general HTML forums. (So I'm deleting the exclamation mark in the final draft.) Good point. I'll include that. -
New 'READ BEFORE POSTING' for HTML and CSS forums
Frank P replied to Frank P's topic in PHPFreaks.com Website Feedback
Ignace, Thanks for the reply, but I would like to focus this thread on whether people like the new 'Read before posting' that I'm proposing. What the contents of '6 basic rules for the newbie webmaster' should be deserves a separate thread. -
Hi, For the CSS Help forum, Cssfreakie wrote a good set of instructions for newbies who want to design a website: http://www.phpfreaks.com/forums/index.php?topic=327775.0. However, items #3, 4, 5 and 6 do not cause rendering problems. They could well create problems for the next web master of that site, but not rendering problems that people come here with. Also, people post questions here with the same annoying omissions and habits for those who help out, that I've seen on other forums I participate in (since 1998). Omissions/habits that are not covered by Cssfreakie's instructions. I would therefore suggest to give his/her sticky the title 'CSS CHECKLIST: 6 basic rules for the newbie webmaster', and to post the following sticky with the title 'READ BEFORE POSTING': <message> Before you post a question, please take note of these instructions: 1. If possible and applicable, put the object on the web so we can see it live. If not possible but still applicable, post the whole code in one code block from <!doctype ..> to </html>, stripped of all irrelevant matters. Replace any relative urls with absolute urls, also in the head and in the style block. 2. Enclose any code you post in code tags (the button over the form with the #). 3. See if your code is basically sound by running it through the W3 Validator: http://validator.w3.org/. 4. Don't over-ask. We will help you with all your problems, but we won't (re)design a webpage for free. If you have multiple problems and a crash course in html/css (http://htmldog.com) doesn't solve the problem, start multiple threads. 5. Try to write proper English in proper sentences. Use your/a spelling checker (http://8help.osu.edu/2143.html/) or Google's translation service (http://translate.google.com/) if necessary. Use capital letters and punctuation marks where called for -- lest we think that you will be a sloppy coder as well, hardly worth helping. 6. Give a clear description of your problem, also in the title (not: Help!). Do not use exclamation marks or all capital letters in your title! 7. No phony problems just to advertise your website! Your message will be removed! 8. As a matter of common courtesy, please report back how suggestions worked out. Welcome to the forum! </message> My name does not have to go under it. My aim is just to make this forum a greater joy for those who (would like to) help out. And newbie webmaster will have to follow strict (coding) rules anyway, it they are to become successful. The above message could also be posted on the HTML Help forum; that does not contain any before-posting instructions at all.
-
Why did you not read or believe the new one, started just three days ago: http://www.phpfreaks.com/forums/index.php?topic=342205.0 with a similar title?