By MrMattles on

Perhaps we need to ensure the code drupal core and conrtibs output valid source....or perhaps it is way past sleep time for me..... :P

Below are the results of checking this document for XML well-formedness and validity.

Error Line 177 column 274: ID "edit-form_id" already defined.
...pe="hidden" name="edit[form_id]" id="edit-form_id" value="user_login_block" .
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

✉

Info Line 35 column 46: ID "edit-form_id" first defined here.
...pe="hidden" name="edit[form_id]" id="edit-form_id" value="search_theme_form"
Error Line 184 column 725: element "wbr" undefined.
...ic theming for the taxonomy_menu module

  • You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "" element),
    by using vendor proprietary extensions such as "" or "" (this is usually fixed by using CSS to achieve the desired effect instead).
    by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case.

    • Comments

    sepeck’s picture

    sepeck commented

    Feel free to supply bug reports aagainst the proper modules.

    -Steven Peck
    ---------
    Test site, always start with a test site.
    Drupal Best Practices Guide -|- Black Mountain

    -Steven Peck
    ---------
    Test site, always start with a test site.
    Drupal Best Practices Guide

    bohtho’s picture

    bohtho commented

    Look at the top in the drupal.org theme source. It's explained why. All my drupal sites validate fine.

    elv’s picture

    elv commented

    But I guess they are theme related :
    - In the "new forum topics" column, some <wbr /> tags are used instead of <br />. It must be a typo.
    - in the stylesheet tag <link rel="stylesheet" href="/themes/bluebeach/print.css" media="print" />, the attribute type="text/css" is missing.

    I don't get the comment on the homepage though... Why would user experience be reduced?

    WeRockYourWeb.com’s picture

    WeRockYourWeb.com commented

    I get the same validation errors since having both user login and search blocks show on the same page:

    "edit-form_id" already defined. Both the "search_block_form" and "user_login_block" use the same ID ("edit-form_id"). You'd think this wouldn't be too difficult to fix (but maybe it is?). Same goes for the drupal.org main page, since the only other error is the <wbr /> typo.

    Alex
    ----------
    Contract Web Development

    sigi’s picture

    sigi commented

    Got same errors when validating, but with submit form in simplenews module.

    ola90@drupal.ru’s picture

    ola90@drupal.ru commented

    I get similar errors:
    "ID "edit-submit" already defined"
    on a page where a search form and a comment form are enabled.