SitePoint Sponsor

User Tag List

Results 1 to 20 of 20
  1. #1
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    very odd spacing issue

    I'm having a really odd spacing issue. I have this main page:

    Code:
    <?php
    
    
    
    
    
    $content .= "
    <div id=\"content\">
    
    <div id=\"rules\">";
    
    include ("rules/general.php");
    include ("rules/automaticpromod.php");
    include ("rules/outlaw105.php");
    include ("rules/limitedstreet.php");
    include ("rules/ezstreet.php");
    include ("rules/modifiedstreet.php");
    include ("rules/hotstreet.php");
    include ("rules/500index.php");
    include ("rules/600index.php");
    include ("rules/700index.php");
    
    $content .= "</div>
    
    <div id=\"staticmenu\" class=\"wireframemenu\" style=\"left: 15px; top: 0px\">
    <ul>
    <li><a href=\"#general\">General Rules</a></li>
    <li><a href=\"#automaticpromod\">Automatic Promod</a></li>
    <li><a href=\"#outlaw10.5\">Outlaw 10.5</a></li>
    <li><a href=\"#limitedstreet\">Limited Street</a></li>
    <li><a href=\"#ezstreet\">EZ Street</a></li>
    <li><a href=\"#modifiedstreet\">Modified Street</a></li>
    <li><a href=\"#hotstreet\">Hot Street</a></li>
    <li><a href=\"#500index\">5.00 Index</a></li>
    <li><a href=\"#600index\">6.00 Index</a></li>
    <li><a href=\"#700index\">7.00 Index</a></li>
    </ul>
    </div>
    
    </div>
    
    ";
    
    
    
    
    ?>
    The general.php page has something in it that is causing my content div to shift down about 21px. Here is my general.php file:

    Code:
    <?php
    
    $content .= "<h1><a name=\"general\">ORSCA GENERAL RULES</a></h1>
    
    <h2>SECTION 1: GENERAL RULES - ALL CLASSES SECTION </h2>
    
    <h3>1.1 - Credentials and License</h3>
    
    All participants must purchase and present a tech card at the time of
    
    inspection. All drivers must have a valid state or government issued
    
    drivers license, proper credentials to compete in 7.0, 6.0, EZ Street,
    
    Limited Street, Outlaw 5.30 Index and Outlaw 10.5 classes. Drivers must
    
    show a valid copy of their NHRA competition license to compete when
    
    that class requires the license. All drivers must be a member of ORSCA
    
    to receive driver points and to participate in the points championship.
    
    Membership cards must be in your possession and presented at time of
    
    tech. If you attempt to compete without a physical license, regardless
    
    of whether or not ORSCA has viewed your license before, it shall be
    
    assumed that no valid license exists. All drivers are strongly
    
    encouraged to acquire the competition license prior to an ORSCA event.
    
    
    
    <h3>SECTION 1.2 - Competition Numbers and Crew Access</h3>
    
    Each vehicle entered into competition must have an official ORSCA
    
    membership number affixed to the windshield and on each side window.
    
    The competition number must be accompanied by the class designation
    
    (Outlaw 10.5, Limited Street, EZ Street, Outlaw 5.30 Index, Outlaw 6.0
    
    Index and Outlaw 7.0 Index). A racer may use an official competition
    
    license number for the vehicle; however, this must be approved by
    
    ORSCA prior to the season of competition and must remain with the
    
    Vehicle throughout the season. All crewmembers should be wearing crew
    
    shirts and must have signed a waiver at ORSCA Tech and have been issued
    
    a wristband to be allowed in the starting area. No more than four (4)
    
    crewmembers per vehicle allowed in the staging area and must possess
    
    proper credentials. No crewmembers are allowed to touch the vehicle
    
    during the burnout or once a vehicle is pre-staged.
    
    
    
    <h3>SECTION 1.3 - Staging</h3>
    
    Points will not be awarded until a vehicle has self-started and
    
    self-staged. This applies to single runs as well. In all classes,
    
    deep staging is allowed, but at the risk of the competitor. Once both
    
    vehicles are staged, this activates the autostart to begin the run. If
    
    any competitor leaves the starting line after being staged and before
    
    system is activated, the run will be disqualified.
    
    
    
    If both drivers of a race leave the line before the starting system is activated, The driver leaving first will be disqualified.
    If the starter is unable to determin who left first both drivers will be disqualifed.
    Any E'Ts posted would be void of any lane choice or other considerations
    The final staging motion using applied power must be in a forward motion going from pre-stage to stage position.
    This will be the procedure ORSCA will follow from this point forward on staging and disqualification proceedure.
    You may review this rule in the 2006 NHRA rule book page 234 section 17 race procedure.
    
    
    
    <h3>SECTION 1:4 - Qualifying and Eliminations</h3>
    
    Qualifying positions will be determined on luck of the draw pairing.
    
    Once a competitor has received a qualifying position and lane no
    
    changes may be made, except by an official from ORSCA. If any
    
    competitor fails to qualify in the assigned position, then that round
    
    of qualifying will be forfeited. All classes will qualify and eliminate
    
    on a pro-ladder. During eliminations, the number one qualifier will be
    
    given the option to run where he/she chooses in the ladder. Otherwise,
    
    we will start with the slowest qualified pairing and continue to the
    
    quickest. Lane choice will be given to the quickest qualifier during
    
    first round. Subsequent to that, it will be awarded to the previous
    
    rounds quickest E.T. All vehicles must weigh at the conclusion of each
    
    run during qualifying and eliminations.
    
    
    
    <h3>SECTION 1.5 - E.T. Records</h3>
    
    Only qualifying, elimination, and final round runs will be counted
    
    Toward E.T. records. The record will only be awarded to the driver
    
    holding the record at the end of the event. In the case of a tie, the
    
    record goes to the driver who records the fastest speed or lowest E.T.
    
    on the record setting run. If a tie still exists, the driver who set
    
    the back-up record first, within 1&#37; at the same event will have the
    
    record. In the event that two runs exceed the record, the latter run
    
    being faster, it will be used to back & shy; up the first and the first
    
    shall be established as the record. All records must be backed-up
    
    within 1%.
    
    
    
    <h3>SECTION 1.6 - Single Runs</h3>
    
    On a single run only those competitors who stage in accordance with
    
    All applicable standards and take the green light shall be considered
    
    the  winner. Cars must stage and take the green light under their own
    
    power. If you cross the centerline on a single run, during
    
    eliminations, you will lose lane choice for the next round.
    
    
    
    <h3>SECTION 1.7 - Foul Starts, Red Lights, Crossing Centerline</h3>
    
    Disqualification will be determined on a first or worst offense. The
    
    First competitor to commit a foul is eliminated. If a competitor red
    
    lights and the opponent crosses the centerline, then the competitor's
    
    opponent will be disqualified and the competitor who red lighted
    
    will be re-instated. Any vehicle whose tire completely passes beyond
    
    either the center yellow line or the outside boundary line shall be
    
    disqualified.
    
    
    
    
    
    <h3>SECTION 1.8 - Scoring Equipment Failure</h3>
    
    Unless one competitor concedes defeat voluntarily, ORSCA will award
    
    The victory at its discretion or may choose to re-run the race. ORSCA
    
    may  choose to review videotape, if available, to determine a winner.
    
    All decisions will be final.
    
    
    
    <h3>SECTION 1.9 - Track Preparation</h3>
    
    Track conditions vary from track to track in factors such as, track
    
    temperature, humidity, and heat index. Every effort will be made by
    
    track personnel and ORSCA to make each venue as equal as possible. Any
    
    competitor found to be dropping debris or liquid that could have an
    
    affect on traction or other racers will not be allowed to run until
    
    their  issues are addressed to the satisfaction of track staff. Teams
    
    are strongly recommended to report any debris or concerns to the track
    
    official before their car enters the burn out box. Entering the burn
    
    out box constitutes a team's acceptance of track conditions.
    
    
    
    <h3>SECTION 1.10 - Weights and Scales</h3>
    
    All vehicles upon completion of a qualifying or in eliminations run
    
    Must cross the scales or the run may be disqualified. ORSCA utilizes
    
    track scales, which may vary from track to track. This shall be the
    
    sole means of measuring weight (irregardless of what your car weighed
    
    at the shop or previous event). Any team member or driver observed
    
    adding weight to a vehicle after a run and prior to crossing the scales
    
    will be disqualified from the event.
    
    
    
    <h2>SECTION 2 - TECHNICAL AND SAFETY EQUIPMENT</h2>
    
    <h3>SECTION 2.1 - Head </h3>
    
    Protection
    
    Helmets are required in all classes of competition. For any vehicle
    
    with a 6.39 or quicker E.T., must have a helmet meeting a Snell 95,
    
    2000, 31.1,31.2, 41.1, or 41.2 specs. Any helmet that is modified in
    
    any way, other than painting, shall be deemed unsafe and not suitable
    
    for competition. Helmets must be worn prior to entering the burnout
    
    area.
    
    
    
    <h3>SECTION 2.2 - Clothing</h3>
    
    All drivers are required to wear a jacket meeting SAFETY
    
    specifications. Any vehicle with a 6.39 or quicker E.T., jacket and
    
    pants must meet spec 3.2A/5 and gloves meeting spec 3.2A/1 and a neck
    
    collar meeting 3.3  spec and shoes meeting spec 3.3/5. Any vehicle
    
    utilizing methanol as its primary source of fuel, must have the
    
    following safety clothing:  jacket and pants, meeting spec 3.2A/20,
    
    gloves, boots meeting 3.2/A15 spec and shoes meeting spec 3,3/5.
    
    
    
    <h3>SECTION 2.3 - Seat Belts & Roll-over Protection</h3>
    
    All cars require a roll bar or cage and must have a 5-point driver
    
    restraint system meeting spec 16.1. Driver restraint systems must be
    
    updated two years from the date stamped on the tag of the belt. All
    
    vehicles with an E.T. of 6.39 or quicker must have a roll cage and be
    
    certified as per class requirements. All vehicles with a roll cage
    
    must have padding meeting spec 45-1 in any area where the driver's
    
    helmet may contact it. All vehicles 6.39 or quicker must have a window
    
    net, either ribbon or mesh type meeting spec 27.1. A permanent
    
    attachment must be present at the bottom of the window net. No eyelet
    
    clips, dog leash, or hose clamps can be used.
    
    
    
    <h3>SECTION 2.4 - Chassis Certifications</h3>
    
    All cars running faster than 6.39 or 135 mph must have a valid
    
    NHRA/IHRA Chassis certification sticker in place in order to compete.
    
    Should any vehicle make a pass faster than 6.39 or 135 mph that run
    
    shall be disallowed in all cases and no points or qualifying status
    
    shall be awarded to that run. All applicable regulations as they
    
    pertain to the vehicle shall be enforced. Any runs made without
    
    applicable chassis or driver certifications shall be disallowed.
    
    
    
    <h2>SECTION 3: ENGINE AND DRIVETRAIN</h2>
    
    <h3>SECTION 3.1 - Cooling System</h3>
    
    All water-cooled entries must have a one pint minimum capacity overflow
    
    reservoir hooked to the radiator in such a way so as to ensure no
    
    coolant shall be dropped on the track. All coolant systems must use
    
    water only. No antifreeze or additives allowed.
    
    
    
    <h3>SECTION 3.2 - Fuel Systems</h3>
    
    Fuel cells and components must meet applicable NHRA/IHRA specs. In
    
    hatchback vehicles in all classes, a firewall must separate the
    
    driver's compartment from the fuel cell.
    
    
    
    <h3>SECTION 3.3 - Nitrous Oxide/pressurized bottles</h3>
    
    Bottles must be stamped 1800-psi minimum. Bottles must be mounted
    
    Directly to the body or chassis utilizing steel brackets and all
    
    mounting points. All nitrous bottles mounted in the driver's
    
    compartment must be vented to the outside.
    
    
    
    <h3>SECTION 3.4 - Throttle</h3>
    
    Every competing vehicle must have a foot throttle incorporating some
    
    Sort of positive action return spring attached directly to the throttle
    
    arm/body/carburetors. Must be manually operated by driver's foot.
    
    Cable throttle systems allowed so long as no brazed or welded fittings
    
    exist on steel cables.
    
    
    
    <h3>SECTION 3.5 - Transmissions</h3>
    
    Functional neutral safety switch is required. May be limited as per
    
    Class requirements. Shifter must have a reverse lock out.
    
    
    
    <h3>SECTION 3.6 - Driveline</h3>
    
    Open drivelines passing any part of the driver's body must be
    
    Completely enclosed with a plate of 1/8\" minimum thickness securely
    
    mounted to the frame or frame structure.
    
    
    
    <h3>SECTION 3.7 - Parachutes</h3>
    
    Required on all cars exceeding 150 mph. Parachute tether must be
    
    Mounted to the chassis by a minimum V? Grade 8 bolt or equivalent.
    
    
    
    <h3>SECTION 3.8 - Headlights, Taillights and Street Equipment</h3>
    
    All vehicles in competition must have factory headlights and
    
    Tail lights and must be in working order. Vehicles with hide a way
    
    Headlights must have a working headlight behind the headlight door. A
    
    fog lamp may be substituted in place of the headlamp at tech official's
    
    discretion.
    
    
    
    <h3>SECTION 3.9 - Ballast</h3>
    
    No liquid or loose ballast permitted. Weight boxes are permitted, but
    
    No more than two are allowed to hold small items such as shot bags,
    
    lead bars, etc. so long as total ballast weight does not exceed 150
    
    lbs. The ballast or boxes must be securely mounted to the frame with at
    
    least two bolts 1/2\" in diameter.
    
    
    
    <h3>SECTION 3.10 - Floors</h3>
    
    Classes requiring factory floorboards that in their original
    
    Construction are manufactured of fiberglass, SMC, or some other
    
    breakable material, must have a metal sub-floor from the firewall to
    
    the rear of the driver's seat on the driver's side only.
    
    
    
    <h3>SECTION 3.11 - Batteries</h3>
    
    All batteries must be securely mounted. No batteries in passenger
    
    compartment. For hatchback vehicles or for those vehicles with inside
    
    material removed exposing trunk area, a firewall of .024\" thick steel
    
    or .032\" aluminum must be installed to seal battery area off from
    
    driver area. Relocated batteries must be fastened using a minimum of 2
    
    bolts, 3/8\" in diameter (No J-Bolts.) Vehicles are limited to a maximum
    
    of two automotive batteries or 150 lbs. total combined weight.
    
    
    
    <h3>SECTION 3.12 - Master Cutoff Switches</h3>
    
    Such devices are mandatory if battery is relocated to a position
    
    other than stock. Such switches must be installed at the rearmost
    
    portion of the vehicle in a location easily accessible from outside the
    
    body. The off position must be clearly identified with the word \"OFF\".
    
    NOTE: If using a push/pull type switch, the off position must be push
    
    to turn off and labeled \"PUSH OFF\".
    
    
    
    <h3>SECTION 3.13 - Wheels</h3>
    
    All lug nuts must be in place and tight. Wheel studs must project
    
    into the hex portion of the lug nut by at the least the distance of the
    
    diameter of the wheel stud. Hubcaps must be removed for competition. A
    
    maximum of four tires and wheels per vehicle, with the exception of
    
    wheelie wheels, which must be non-metallic. Wheelie bars must be fixed,
    
    no hydraulics, pneumatics, or electronics may in any way provide
    
    adjustment or movement during a run.
    
    
    
    <h2>Section 4 - PROTEST PROCEDURES, DISCIPLINARY ACTIONS AND ENFORCEMENT POLICIES</h2>
    
    
    
    <h3>SECTION 4.1 - Protest Procedure</h3>
    
    Every effort is made to properly inspect all cars for proper
    
    Compliance and equipment. From time to time, something may pass through
    
    tech undetected or a racer may have personal knowledge of illegal
    
    equipment or safety deficiencies. If you have personal knowledge of a
    
    racer using illegal equipment or not in compliance with the rules, it
    
    is your obligation to report this infraction. All protests must be
    
    filed the day prior to scheduled eliminations and can only be filed by
    
    a qualified team or members who are competing in the same class as the
    
    vehicle protested. Protests must be filed and accompanied with the
    
    corresponding fee paid in cash only. The protest fee shall be forfeited
    
    minus technical fees to the car owner should the protest be deemed
    
    without merit or the car is found to be legal. ORSCA reserves the right
    
    to reject any protest filed that it determines in its sole and absolute
    
    discretion, is deemed to be frivolous or intended to harass another
    
    competitor or is to otherwise gain some unfair competitive advantage.
    
    Complaints, tips, or other advisories outside these guidelines do not
    
    constitute valid protest and hence  shall be disregarded. If inspection
    
    finds and determines that a vehicle is not in compliance to the rules,
    
    it is ORSCA's sole discretion to take action dependent upon the
    
    infraction. This action may consist of a verbal warning to an expulsion
    
    from competition until the infraction is corrected. In the event a
    
    vehicle is found to be illegal, the driver and team will forfeit all
    
    points gathered at that event. If a driver or team is found to have
    
    willfully installed or utilized an illegal part or parts after they
    
    have completed the tech inspection, then it is at ORSCA's discretion to
    
    take disciplinary action commensurate with the offense. (This action
    
    may range from forfeiture and expulsion from an event to racing
    
    privilege suspended for up to one year from the offense).
    
    
    
    <h3>SECTION 4.2 - Decisions by Race Director</h3>
    
    Race Director may alter, amend, or waive any rule or specification
    
    for any single occurrence or for any good reason without advance notice
    
    and with no obligations to anyone or organization. The Event Director
    
    has sole and irrevocable right to determine eligibility of a racer or
    
    team, make decisions with regard to what constitutes fair competition,
    
    inappropriate or un-sportsmanlike conduct, threatening behavior or what
    
    constitutes a violation worthy of disciplinary action and what that
    
    appropriate discipline may be. Entrance into any ORSCA sanctioned event
    
    means that drivers, crewmembers, and participants agree with all rules,
    
    procedures and guidelines. Teams do not have the right to protest the
    
    rules, only to protest against those teams believed not to be in
    
    compliance. With regard to equipment or race procedures, decisions on-
    
    sight by Race Director are final. No review or appeal process the day
    
    of the race, so as to ensure finality to an event. The Race Director or
    
    Tech Director must retain final authority in disqualifying parts,
    
    racers, equipment for violation of the rules, failure to comply with
    
    directions, or for any technical or behavioral infraction.
    
    
    
    <h3>SECTION 4.3 - Participant Conduct</h3>
    
    Any participant who, at the sole discretion of ORSCA, 1) verbally
    
    abuses/threatens any other person, 2) uses vulgar or derogatory
    
    language, 3) engages in un-sportsmanlike conduct, 4) creates a
    
    condition that is hostile, unfair, unsafe, or is out of order, shall be
    
    subject to immediate removal from the event and further disciplinary
    
    action. ORSCA reserves final judgment as to what type of behavior,
    
    conduct or language shall be deemed hostile, unfair, unsafe, or with
    
    issues of un-sportsmanlike conduct and what constitutes threats or
    
    abuse. ORSCA decisions are final without appeal or further discussion.
    
    Race questions must be directed to the ORSCA Race Director who are on
    
    sight. Protest discussions or other dialogue will only take place with
    
    a maximum of two team members present and both teams must be in
    
    uniform. These discussions will be held in a private room or forum and
    
    will not be open to large groups or public. Protests will not be
    
    honored or examined in any way on the day of final eliminations.
    
    
    
    <h3>SECTION 4.4 - Confidentiality</h3>
    
    For primary tech inspection, ORSCA shall inspect vehicles in an
    
    appropriate, technical area, to be designated at our discretion.
    
    ORSCA shall not reveal any trade or technical secrets to a competing
    
    team even if those secrets or equipment are found to be illegal.
    
    Competitors are assured that any details revealed to ORSCA Technical
    
    Director or staff, shall not be revealed to other teams for any reason.
    
    During technical inspections, ORSCA officials may limit the number of
    
    and which team personnel may be present at time of inspection.
    
    
    
    <h3>SECTION 4.5 - Implied Consent</h3>
    
    All ORSCA participants and attendees who are in any way engaged or
    
    associated with competing teams, shall recognize that their presence
    
    at an ORSCA event implies consent to search or inspect any vehicle
    
    engaged in competition, any equipment or support vehicles used. ORSCA
    
    shall at its discretion, choose to examine the inside or tow vehicles,
    
    vehicles in competition, or anywhere they deem appropriate as to ensure
    
    that all safety and classification guidelines are being strictly
    
    followed. Any team refusing immediate and unconditional access to an
    
    area after the ORSCA official requests shall result in the team's
    
    immediate removal from the event, loss of all points, and may result in
    
    suspension from competition for a period solely at ORSCA's discretion.
    
    
    
    
    
    <h3>SECTION 4.6 - Substance Abuse</h3>
    
    ORSCA is a zero tolerance organization. If any driver, team member,
    
    Or person working on or near a competitor's vehicle is found to be
    
    Consuming alcohol or found to have any measurable blood alcohol
    
    content, he/she shall be deemed under the influence and be banned from
    
    all participation in that event. ORSCA reserves the right to determine
    
    that a person in unfit for competition, without measurable blood
    
    alcohol content. No team member in uniform is allowed to consume any
    
    alcohol or be under the influence at any time during an event. All
    
    members wearing crew uniforms shall be assumed to play a key role in
    
    the preparation of the vehicle and the assurance of compliance with
    
    safety guidelines and be subject to those terms and conditions.
    
    
    
    <h3>SECTION 4.7 - Driver Change</h3>
    
    The Event Director has the option of permitting driver changes under
    
    The following conditions: 1) replacement driver must meet ORSCA
    
    Requirements and possess proper credentials, 2) original driver must be
    
    withdrawn from competition and will not be re-instated, 3) all previous
    
    qualifying times shall be voided for vehicle in competition, 4)
    
    replacement driver must re-qualify vehicle during normal qualifying
    
    schedule, 5) no replacements allowed after qualifications have ended,
    
    6) limited to one replacement per event. A replacement driver shall not
    
    drive more than one vehicle per class of competition.
    
    ";
    ?>
    Here is what I can tell you:

    I use textpad and it colors some stuff. It's got everything a light blue up until this line:

    Code:
    Completely enclosed with a plate of 1/8\" minimum thickness securely
    which is in section 3.6 and it turns black after the ".

    If I remove everything from the <h1> tag to the " at the end, it fixes the problem. If I try and isolate the problem further by deleting sections, it doesn't fix it. I've tried deleting from the beginning through section 1, through section 2, through section 3, even down to section 3.5 and still no fix. Deleting the entire section 3 doesn't fix it either. I don't see any problems, so maybe it's something I don't know about or just don't see.


    edit: oh! my stylesheet:
    Code:
    html {min-width:999px;}
    body {
    min-width:999px;    margin: 0px;
        padding: 0px;
        background: #000000 url(http://berryequipment.net/orsca/images/repeatbg2.jpg) repeat-y 50% 0;
    }
    #container {
        text-align: center;
        width: 100%;
        background: url(http://berryequipment.net/orsca/images/mainbg.jpg) no-repeat 50% 108px;
    }
    #top {
        text-align: center;
        min-width: 999px;
        height: 108px;
        background: #000 url(http://berryequipment.net/orsca/images/topbg.jpg);
    }
    #main-container {
        position: relative;
        width: 1001px;
        min-height: 784px;
        margin-left: auto;
        margin-right: auto;
        text-align: left;
    }
    #main-nav {
        position: relative;
        margin-top: 48px;
        margin-left: 12px;
        width: 982px;
        height:58px;
        background-color: #434222;
    }
    
    
    
    #news
    {
      float: left;
      display: block;
      width: 94px;
      height: 58px;
      background: url("../images/nav/news.jpg") no-repeat 0 0;
    }
    #news:hover
    { 
      background-position: 0 -58px;
    }
    #news span
    {
      display: none;
    }
    
    #forums
    {
      float: left;
      display: block;
      width: 79px;
      height: 58px;
      background: url("../images/nav/forums.jpg") no-repeat 0 0;
    }
    #forums:hover
    { 
      background-position: 0 -58px;
    }
    #forums span
    {
      display: none;
    }
    
    #classifieds
    {
      float: left;
      display: block;
      width: 106px;
      height: 58px;
      background: url("../images/nav/classifieds.jpg") no-repeat 0 0;
    }
    #classifieds:hover
    { 
      background-position: 0 -58px;
    }
    #classifieds span
    {
      display: none;
    }
    
    #raceschedule
    {
      float: left;
      display: block;
      width: 127px;
      height: 58px;
      background: url("../images/nav/raceschedule.jpg") no-repeat 0 0;
    }
    #raceschedule:hover
    { 
      background-position: 0 -58px;
    }
    #raceschedule span
    {
      display: none;
    }
    
    #rulebooks
    {
      float: left;
      display: block;
      width: 105px;
      height: 58px;
      background: url("../images/nav/rulebooks.jpg") no-repeat 0 0;
    }
    #rulebooks:hover
    { 
      background-position: 0 -58px;
    }
    #rulebooks span
    {
      display: none;
    }
    
    #standings
    {
      float: left;
      display: block;
      width: 96px;
      height: 58px;
      background: url("../images/nav/standings.jpg") no-repeat 0 0;
    }
    #standings:hover
    { 
      background-position: 0 -58px;
    }
    #standings span
    {
      display: none;
    }
    
    #records
    {
      float: left;
      display: block;
      width: 86px;
      height: 58px;
      background: url("../images/nav/records.jpg") no-repeat 0 0;
    }
    #records:hover
    { 
      background-position: 0 -58px;
    }
    #records span
    {
      display: none;
    }
    
    #photogallery
    {
      float: left;
      display: block;
      width: 125px;
      height: 58px;
      background: url("../images/nav/photogallery.jpg") no-repeat 0 0;
    }
    #photogallery:hover
    { 
      background-position: 0 -58px;
    }
    #photogallery span
    {
      display: none;
    }
    
    #racerprofile
    {
      float: left;
      display: block;
      width: 164px;
      height: 58px;
      background: url("../images/nav/racerprofile.jpg") no-repeat 0 0;
    }
    #racerprofile:hover
    { 
      background-position: 0 -58px;
    }
    #racerprofile span
    {
      display: none;
    }
    
    
    
    #main-content-holder {
        position: relative;
        margin-top: 0px;
        width: 758px;
        background:url(../images/repeatbg.jpg) repeat-y 0 0;
    }
    #content { 
        color: #FFF;
        width: 758px;
        text-align: left;
        background: url(../images/contentbgtop.jpg) no-repeat;
        min-height: 678px;
    }
    #home_content1 {
        color: #FFF;
        width: 758px;
        height: 391px;
        background: url(../images/home_contentbg1.jpg);
    }
    #home_content2 {
        width: 758px;
        height: 305px;
        background: url(../images/home_contentbg2.jpg);
    }
    #sponsors {
        margin-top: 55px;
        text-align: center;
        width: 758px;
        height: 225px;
    }
    #main-classes {
        position: absolute;
        top: 150px;
        left: 797px;
        width: 203px;
        height: 626px;
    }
    
    #calholder {
    width: 758px;
    text-align: center;
    }
    
    #calendar {
    width: 455px;
    text-align: left;
    margin-left: auto;
    margin-right: auto;
    }
    
    #month {
    margin-left: 40px;
    font: 2em Trebuchet MS, sans-serif; line-height: 1.25; color: #FFF;
    display: block;
    }
    
    .weekday {
    color: #FFF;
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #FFF;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    
    .weekend {
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #800000;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    
    .eventday1 {
    background: url(../images/event1.jpg);
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #FFF;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    .eventday2 {
    background: url(../images/event2.jpg);
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #FFF;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    .eventday3 {
    background: url(../images/event3.jpg);
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #FFF;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    .eventday4 {
    background: url(../images/event4.jpg);
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #FFF;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    .eventday5 {
    background: url(../images/event5.jpg);
    margin-left: 20px;
    text-align: center;
    font: 1.125em Lucida Sans Unicode, sans-serif; color: #FFF;
    float: left;
    width: 45px;
    height: 45px;
    line-height: 45px;
    }
    
    .chooser {
    float: right;
    margin-right: 5px;
    margin-top: 5px;
    }
    
    
    
    
    
    
    
    
    #rules {
    margin-top: 0px;
    margin-left: 200px;
    width: 500px;
    }
    
    
    .wireframemenu{
    border: 1px solid #282828;
    background-color: #202020;
    border-bottom-width: 0;
    width: 170px;
    position: absolute;
    }
    
    * html .wireframemenu{ /*IE only rule. Original menu width minus all left/right paddings */
    width: 164px;
    }
    
    .wireframemenu ul{
    padding: 0;
    margin: 0;
    list-style-type: none;
    }
    
    .wireframemenu a{
    font: bold 13px Verdana;
    padding: 4px 3px;
    display: block;
    width: 100%; /*Define width for IE6's sake*/
    color: #FFFFFF;
    text-decoration: none;
    border-bottom: 1px solid #303030;
    }
    
    .wireframemenu a:visited{
    color: #FFFFFF;
    }
    
    html>body .wireframemenu a{ /*Non IE rule*/
    width: auto;
    }
    
    .wireframemenu a:hover{
    background-color: #181818;
    color: #FFF;
    }
    
    
    h1 {
    color: #D00000;
    }

    edit 2: This is also only in Firefox.

  2. #2
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    PHP and HTML are two very different things. Your CSS sheet never sees PHP. It only sees what you see if you look at your page in a browser and do a View Source.

    Unlike HTML (most of the time), PHP is sensitive to " and ' so (and your text editor, if it cares, is colouring for PHP), what happens if you just manually encode that double quote? It may be closing your opening " for PHP right before the opening <h1> tag.

    There are a few ways to do it but I like
    & # 8243 ; for foots like you have.

  3. #3
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Okay I have no problem trying that, though this issue seems to be odder than something like that. I changed all double quotes to the method you mentioned ″ and still no change in space. I checked and deleted the include of general.php and problem solved, put it back and the problem was back. The other pages included are structured in the same manner and aren't causing this issue. I understand that the CSS is applied to the html portion, this isn't a php issue.

    edit: Now with the double quote "fix", deleting all through 3.6 won't solve the problem.

  4. #4
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    Well, if you could post the source, we could run that same HTML with your CSS through our browsers and see where the space is actually coming from.

    Maybe the " is a red herring but it sure seemed to be part of the problem (esp if it stopped the HTML from finishing, which would leave an open h3 hanging which itself certainly could screw with the page).

    Or if there's a live page, that's also good. But I can't read PHP and browsers don't bother, so we needs teh HTML.

  5. #5
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I was just thinking of a way to do it, since the included pages make it so long. The only thing about you saying it stopping the html short, the other pages were still included and the entire file was still included, it's just a weird spacing issue with the top div.

    Heres the output:
    http://pastebin.ca/1768002

    Pastebin didn't take it all either, here's the rest where pastebin left off (a little overlap)

    Code:
    
    <a name="700index"><h1>2010 7.00 INDEX RULES  :  Last Updated : 12-30-2009</h1></a>
    
    
    
    
    
    <h3>Class Description</h3>
    Classes are run off a .400 Pro Tree. Vehicles are not required to have a current registration.
    
    <h3>Body</h3>
    Vehicles from a major manufacturer only.  Full fiberglass bodies are not allowed.
    Must  have , tail lights
    
    <h3>Electrical</h3>
    Optical sensors,  and electrical or pneumatic throttle stops are not allowed.
    
    
    <h3>Deep Staging</h3>
    Deep Staging is allowed at driver's risk. Starter will not wait for driver to deep stage.
    
    <h3>Tech</h3>
    After unloading of car, a tech card must be completed both front and back.  This tech card must be brought with the car to tech for  tech inspection. All cars must pass rules and safety inspection to race.
    
    <h3>Disqualification</h3>
    Disqualification, (the pass will not count) for any of the following: crossing the centerline, use of above mentioned bracket racing aids, improper staging procedures, failure to report to staging lanes when called, reckless driving or speeding in pit area or return road. Outlaw 7.00 Index cars will be disqualified for running under index during eliminations.
    
    
    <h3>Qualifying</h3>
    
    Outlaw 7.00 Index cars will qualify for run positions and placed on a Pro or Sportsman ladder. Lane choice is determined by previous round E.T.
    
    <h3>Uniforms</h3>
    Matching uniforms or matching shirts are required to be on the starting line or in the burn box area as a crewmember. Crewmembers must leave the starting line and burnout area after each pass.
    
    * Rules may be revised in accordance as need arrives.
    
    
    </div>
    
    <div id="staticmenu" class="wireframemenu" style="left: 15px; top: 25px">
    <ul>
    <li><a href="#general">General Rules</a></li>
    <li><a href="#automaticpromod">Automatic Promod</a></li>
    <li><a href="#outlaw10.5">Outlaw 10.5</a></li>
    <li><a href="#limitedstreet">Limited Street</a></li>
    <li><a href="#ezstreet">EZ Street</a></li>
    
    <li><a href="#modifiedstreet">Modified Street</a></li>
    <li><a href="#hotstreet">Hot Street</a></li>
    <li><a href="#500index">5.00 Index</a></li>
    <li><a href="#600index">6.00 Index</a></li>
    <li><a href="#700index">7.00 Index</a></li>
    </ul>
    </div>
    
    </div>
    
    
            </div>
    
    
            <div id="sponsors">
    <object width="698" height="183">
    <param name="movie" value="images/sponsors.swf">
    <embed src="images/sponsors.swf" width="698" height="183">
    </embed>
    </object>
            </div>
    
            <div id="main-classes"> <img src="http://berryequipment.net/orsca/images/autopromod.png" /> <a href="http://www.southerndieselperformance.com/" target="_blank"><img src="http://berryequipment.net/orsca/images/stp.png" border="0" /></a> </div>
    
        </div>
    </div>
    </body>
    </html>

  6. #6
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    Stupid retard pastebin, you can see code but you can't copy it without stupid # everywhere breaking everything. I don't feel like writing some regex for my editor to remove them.

    Likely, knowing me, there's a button somewhere that says "copy this code" and I just don't see it : )

    So I copied your doctype and then the stuff you had posted earlier.

    Are you seeing a space here? http://stommepoes.nl/orscatest.html

    *edit I tried to run that through the validator but all the loose text really hits it hard.

  7. #7
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    Yeah, there's an edit section, lawlz. I was able to copy that after fiddling with it...
    http://stommepoes.nl/orscatest2.html

    The only space I see at the top is a div called "top"... where's the gap you mean?

  8. #8
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The #content div is dropped down around 20px, top is FF and bottom is IE:




    Seems to be broken like this in Firefox win&osx, Chrome and Safari
    Probably say IE is the only one it's working in correctly.

  9. #9
    billycundiff{float:left;} silver trophybronze trophy RyanReese's Avatar
    Join Date
    Oct 2008
    Location
    Whiteford, Maryland, United States
    Posts
    13,746
    Mentioned
    11 Post(s)
    Tagged
    0 Thread(s)
    Hi, the <h2> inside the <div id="rules"> (the first <h2>, I don't know if there is more, I'm too lazy to see), but anyway, the <h2> inside the rules div has default margins set on it. Either set the margins to 0 for the <h2> or control everything and use a reset
    Code:
    *{margin:0;padding:0;}
    Always looking for web design/development work.
    http://www.CodeFundamentals.com

  10. #10
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    There are a lot of them, that seemed to fix it. Thing that I don't get is, I was removing part of the one file and it was fixing it, but I had more h2 tags around. Anyway, it's probably good to use that bit of code on every site's main style.

  11. #11
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    Be careful with padding: 0 though, esp if you have any forms on the site. Once gone, some browsers (Opera is one) won't let you add them back in for form controls.

  12. #12
    SitePoint Member
    Join Date
    Jan 2010
    Posts
    2
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    maybe give this a try... use the firefox plugin CSSViewer, hover over the area that you're looking at, then see the formats and styles applied. You might be able to figure it out that way, then go to your css file and make changes there. hope that works for you. - duane nason

  13. #13
    billycundiff{float:left;} silver trophybronze trophy RyanReese's Avatar
    Join Date
    Oct 2008
    Location
    Whiteford, Maryland, United States
    Posts
    13,746
    Mentioned
    11 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by aebstract View Post
    There are a lot of them, that seemed to fix it. Thing that I don't get is, I was removing part of the one file and it was fixing it, but I had more h2 tags around. Anyway, it's probably good to use that bit of code on every site's main style.
    I'd have to have a test case to know what was the case tehre
    Always looking for web design/development work.
    http://www.CodeFundamentals.com

  14. #14
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    It was any of the tags I used, H1, H2, H3.. Basically if I deleted down and an H# tag was left at the top of the content, it would space it down. If it was plain text, no issue. That's why it seemed very uncommon. Here's a question, what if I want to have a margin spacing on my h1 tag and I want my h1 tag at the top of my content div. Is there any way to do that without having the content div space down?

  15. #15
    billycundiff{float:left;} silver trophybronze trophy RyanReese's Avatar
    Join Date
    Oct 2008
    Location
    Whiteford, Maryland, United States
    Posts
    13,746
    Mentioned
    11 Post(s)
    Tagged
    0 Thread(s)
    Well you couldn't really see it in your example, but the margins were being collapsed because it ran through the parent.

    A 1px padding on the parent will fix it (or a 1px border)
    Always looking for web design/development work.
    http://www.CodeFundamentals.com

  16. #16
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    Ah, it was collapsing margins!

    When you have a container, and inside you have someone with top margins, those top margins are transferred to the container instead.

    So if you had
    <body>
    <div>
    <h1>title</h1>
    stuff...
    </div>
    etc...
    </body>
    And the h1 had a top margin to "push" it away from sitting right up against the top of the containing div, instead the h1 remains at the top of the div but the div itself looks pushed away from the top of the body.

    So if you want margins on the h1 go ahead and put the other 3 sides on there, and to push the headers away from the tops of containers, give the container instead padding-top.

    Another solution is the adding of 1px of padding which stops margin collapse entirely.

    I tend to put margins on the bottoms of my headers and if I want to push a header away from text who sits above it, I put a bottom margin on that text (text should not sit loose in an HTML page, but be wrapped in a <p> or something appropriate).

    *edit Ryan ninja'd me.

  17. #17
    SitePoint Zealot
    Join Date
    Feb 2008
    Posts
    147
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Stomme poes View Post
    Another solution is the adding of 1px of padding which stops margin collapse entirely.

    Worked like a charm!

  18. #18
    billycundiff{float:left;} silver trophybronze trophy RyanReese's Avatar
    Join Date
    Oct 2008
    Location
    Whiteford, Maryland, United States
    Posts
    13,746
    Mentioned
    11 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Stomme poes View Post
    Ah, it was collapsing margins!

    When you have a container, and inside you have someone with top margins, those top margins are transferred to the container instead.

    So if you had
    <body>
    <div>
    <h1>title</h1>
    stuff...
    </div>
    etc...
    </body>
    And the h1 had a top margin to "push" it away from sitting right up against the top of the containing div, instead the h1 remains at the top of the div but the div itself looks pushed away from the top of the body.

    So if you want margins on the h1 go ahead and put the other 3 sides on there, and to push the headers away from the tops of containers, give the container instead padding-top.

    Another solution is the adding of 1px of padding which stops margin collapse entirely.

    I tend to put margins on the bottoms of my headers and if I want to push a header away from text who sits above it, I put a bottom margin on that text (text should not sit loose in an HTML page, but be wrapped in a <p> or something appropriate).

    *edit Ryan ninja'd me.
    You probably woulda beat me but I don't explain too in depth unless they ask. I generally just do a short explanation . Not that beating someoen in posting is a big deal lol .
    Quote Originally Posted by aebstract View Post
    Worked like a charm!
    Yup
    Always looking for web design/development work.
    http://www.CodeFundamentals.com

  19. #19
    SitePoint Wizard Stomme poes's Avatar
    Join Date
    Aug 2007
    Location
    Netherlands
    Posts
    10,283
    Mentioned
    51 Post(s)
    Tagged
    2 Thread(s)
    Well, Ryan, the thing about ninjas is, you just don't see them.

    : )

    (actually, you should get a ninja for your avatar. Have you seen John Resig's?)

  20. #20
    billycundiff{float:left;} silver trophybronze trophy RyanReese's Avatar
    Join Date
    Oct 2008
    Location
    Whiteford, Maryland, United States
    Posts
    13,746
    Mentioned
    11 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Stomme poes View Post
    Well, Ryan, the thing about ninjas is, you just don't see them.

    : )

    (actually, you should get a ninja for your avatar. Have you seen John Resig's?)
    Off Topic:

    I awas actually trying to find the Road runner, because he is fast..and I found mario on the search (weird eh?) and I thought it was a good picture so I decided to keep it.

    No I havent
    Always looking for web design/development work.
    http://www.CodeFundamentals.com


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •