Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Page 1 of 2 12 LastLast
Results 1 to 15 of 28
  1. #1
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Nav. Menu + Popup "box" all-browser-age/version friendly?

    I dont want ANYONE to have problems accessing 1. my navigation bar made in a css menu builder or 2. the css popup boxes when you mouseover the "more" buttons on the main page.

    [url]www.drpcrepair.com[]

    thanks a lot.

  • #2
    Master Coder Excavator's Avatar
    Join Date
    Dec 2006
    Location
    Alaska
    Posts
    9,667
    Thanks
    22
    Thanked 1,827 Times in 1,811 Posts
    Hello mat420,
    The first step would be making sure your code is valid. See the links about validation in my signature line.

    The next step would be identifiying any browsers or users that are having troubles. Once, or if, you find anyone that can't navigate your site then you'll be able to ask a more specific question.
    Validate often DURING development - Use it like a splelchecker | Debug during Development |Write it for FireFox, ignore IE
    Use the right DocType | Validate your markup | Validate your CSS | Why validating is good | Why tables are bad

  • #3
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    i did attempt to vcalidate code and failed, ill have to try again.

    with what i possibly plan to do wit hthis site, i cant be waiting just to 'hear' someone couldnt access my css menu, if thats what you mean though

    i need to know how browser friendly these 2 options are.
    for example no one, no matter what age browser or OS has problems seeing an html text box (i wouldnt think), might that person have trouble seeing my menu? and pop up bubbles?
    i dont know how to identify any browsers having trouble without downloading them all.
    browsershots doesnt give me the opportunity to mouseover the "more" buttons or my "services" drop down css menu.

    ill start with the links in ur signature though.

  • #4
    Master Coder Excavator's Avatar
    Join Date
    Dec 2006
    Location
    Alaska
    Posts
    9,667
    Thanks
    22
    Thanked 1,827 Times in 1,811 Posts
    Quote Originally Posted by mat420 View Post
    , i cant be waiting just to 'hear' someone couldnt access my css menu,
    Testing is part of development. That should be your responsibility, not your end users.
    It's up to you to verify your page works as intented in all your target browsers.
    Validate often DURING development - Use it like a splelchecker | Debug during Development |Write it for FireFox, ignore IE
    Use the right DocType | Validate your markup | Validate your CSS | Why validating is good | Why tables are bad

  • #5
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    tell me where to start then please? is that all i can do is verify the code works correctly and hope for the best?

    thank you vm.

  • #6
    Master Coder Excavator's Avatar
    Join Date
    Dec 2006
    Location
    Alaska
    Posts
    9,667
    Thanks
    22
    Thanked 1,827 Times in 1,811 Posts
    You should start with valid code and CSS. That is your best chance at cross browser compatibility but it is by no means any guarantee.

    After that, you will need to personally check in each browser yourself. You can address issues as they come up, correct them and re-check in all those browsers again.

    Welcome to the wonderful world of web authoring!
    Validate often DURING development - Use it like a splelchecker | Debug during Development |Write it for FireFox, ignore IE
    Use the right DocType | Validate your markup | Validate your CSS | Why validating is good | Why tables are bad

  • #7
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    see im rtying to 'validate my markup'

    Line 10, Column 16: there is no attribute "ROWS"
    <frameset rows="100%,*" border="0">

    but i dont see the word frameset in any of my code..i used notepad to check every html file

    i even checked my php and css files and the term " frameset" is nowhere.
    i dont udnerstand.

  • #8
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    validated some of my css.
    afraid to touch all of this tough and risk breaking anything.
    for example the webkit part of this...is working fine on all browsers but comes up as an error.


    URI : http://s289686823.onlinehome.us/drpcrepair/89 .thumbnail span Parse Error text-decoration: none
    118 .qmmc Property zoom doesn't exist : 1 1
    144 #qm0 div, #qm0 ul Property -webkit-border-bottom-right-radius doesn't exist : 10px 10px 10px 10px
    145 #qm0 div, #qm0 ul Property -khtml-border-radius-bottomright doesn't exist : 10px 10px
    146 #qm0 div, #qm0 ul Property -moz-border-radius-bottomright doesn't exist : 10px 10px
    147 #qm0 div, #qm0 ul Property border-bottom-right-radius doesn't exist in CSS level 2.1 but exists in : 10px 10px

  • #9
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    bumpppp please

  • #10
    Master Coder Excavator's Avatar
    Join Date
    Dec 2006
    Location
    Alaska
    Posts
    9,667
    Thanks
    22
    Thanked 1,827 Times in 1,811 Posts
    All that "doesn't exist" stuff is CSS3. In browsers that support CSS3 it will work, it'll just be ignored in browsers that don't support it.

    You'll be fine leaving those entries in your CSS.
    Validate often DURING development - Use it like a splelchecker | Debug during Development |Write it for FireFox, ignore IE
    Use the right DocType | Validate your markup | Validate your CSS | Why validating is good | Why tables are bad

  • #11
    Regular Coder
    Join Date
    Jul 2002
    Location
    Kansas, USA
    Posts
    477
    Thanks
    0
    Thanked 51 Times in 50 Posts
    The frameset is coming from the fact that you are URL cloaking - your domain name is drpcrepair.com but your page is actually located at http://s289686823.onlinehome.us/drpcrepair/. Further, the w3 validator can't parse your document at that address because it contains non-UTF-8 characters. The offending character is in your <title>:
    Code:
    <title>Dr. PC Repair � PC Repair | Web Design | PC Training & More</title>

  • #12
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    wow......
    so i addressed those issues...
    it says 193 errors...
    id appreciate if anyone can tell me how important it is that i fix these or any of these? because wow..
    thanks so much all


    http://validator.w3.org/check?uri=ht...Inline&group=0

  • #13
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    its a lot of easy fixes but holy crap 193?

  • #14
    Regular Coder
    Join Date
    Jul 2002
    Location
    Kansas, USA
    Posts
    477
    Thanks
    0
    Thanked 51 Times in 50 Posts
    Yes there are a lot of errors, but as you said most of them are very easy to fix. While it is not critical (from a browser standpoint) that these be fixed, it will help to find future errors.

    Here, I will get you started:
    Line 5, Column 61: character "&" is the first character of a delimiter but occurred as data

    <title>Dr. PC Repair - PC Repair | Web Design | PC Training & More</title>

    This message may appear in several cases:
    * You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    Code:
    <title>Dr. PC Repair - PC Repair | Web Design | PC Training &amp; More</title>
    Many of the errors are due to your using the XHTML doctype. XHTML requires lower-case tag and attribute names and self-closing "empty" tags. Additionally, you cannot use tags that do not appear in the XHTML DTD, including any proprietary or browser-specific tags. It may make less of a headache for you if you switched to the HTML 4.01 transitional doctype.

    Line 6, Column 12: there is no attribute "NAME"

    <META NAME="ROBOTS" CONTENT="INDEX, FOLLOW">

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
    Code:
    <meta name="robots" content="index, follow">
    Attribute values are not required to be lower-case, but this looks a bit nicer than:
    Code:
    <meta name="ROBOTS" content="INDEX, FOLLOW">
    Line 113, Column 64: end tag for "link" omitted, but OMITTAG NO was specified

    <link href="cssmenustyle.css" rel="stylesheet" type="text/css">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
    Code:
    <link href="cssmenustyle.css" rel="stylesheet" type="text/css" />
    You'll need to do this for all those <br> tags as well.
    Code:
    <br />
    Line 115, Column 25: required attribute "type" not specified

    <script src="cssmenu.js"></script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
    Code:
    <script src="cssmenu.js" type="text/javascript"></script>
    Type is required for HTML 4.01 and XHTML. You can leave it out for HTML 5.

    Line 382, Column 26: document type does not allow element "style" here

    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
    Great, you remembered the type attribute. Too bad XHTML doesn't allow <style> outside of the <head>.

    My recommendation is to fix a few errors and then re-run the validation. Fixing a few may clean up many of the reported errors.

    If you need help with further errors, let us know.

  • #15
    New Coder
    Join Date
    May 2008
    Posts
    31
    Thanks
    0
    Thanked 0 Times in 0 Posts
    you're thebest
    thanks a lot.


  •  
    Page 1 of 2 12 LastLast

    Posting Permissions

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