Help - Just upgraded and HTML/CSS validation is failing due to the Paginaton

HTML & CSS
1

I recently upgraded to the latest PHP Framework version and pagination is breaking the validation.

I think the “data-ci-pagination-page” is meant for JavaScript?

The statements are dynamically generated by the system so they will not be easy to remove. Is it possible to eliminate these errors, they are annoying!

<div class="my-pagination"> 

  <a href="/pix/index/2"  data-ci-pagination-page="2">
    2
  </a>&nbsp;

  <a href="/pix/index/3"  data-ci-pagination-page="3">
    3
  </a>&nbsp;

  <a href="/pix/index/4"  data-ci-pagination-page="4">
    4
  </a>&nbsp;
  
  <a href="/pix/index/5"  data-ci-pagination-page="5">
    5
  </a>&nbsp;
  
  ...
</div>
2

I validate this page and it validates.

<!doctype html>
<html>
<head>
<title>asdf</title>
<meta charset="utf8">
</head>
<body>
<div class="my-pagination"> 

  <a href="/pix/index/2"  data-ci-pagination-page="2">
    2
  </a>&nbsp;

  <a href="/pix/index/3"  data-ci-pagination-page="3">
    3
  </a>&nbsp;

  <a href="/pix/index/4"  data-ci-pagination-page="4">
    4
  </a>&nbsp;
  
  <a href="/pix/index/5"  data-ci-pagination-page="5">
    5
  </a>&nbsp;
 
</div>
</body></html>
3

check your doctype. Is it: <!doctype html> ? the data attribute is valid only in HTML5.

1 Like
4

I always use the Strict Doctype because it highlights errors. HTML 5 seems sloppy and the validator misses out on some errors and warnings.

I had vague memories when playing with Ajax that it was possible to eliminate the warnings by setting some parameters in the <head … >, unfortunately I have forgotten the exact script and it is not easy to search for something that I have forgotten.

http://www.johns-jokes.com/downloads/sp-d/ryanreese-pagination/index.php

 Line 24, Column 53: there is no attribute "data-ci-pagination-page"
    <a href="/pix/index/2"  data-ci-pagination-page="2">

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. 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 "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

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.
5

Yup, the errors indicate your doctype doesn’t support it.

The HTML5 doctype doesn’t cause the validator to miss errors. It’s simply more lenient than strict. More code is valid in HTML5 rather than strict. That doesn’t make it bad or wrong.

6

I think you might be thinking of “custom DTD”

To me it felt like it was only a way to “fool” the validator more than a real work-around.

And the W3C says “Don’t!”
http://www.w3.org/Style/customdtd.en.html

7

That’s because HTML 5 doesn’t have a doctype - it just uses the short version of the HTML 2 doctype tag as an HTML tag to tell browsers to use standards mode. You can’t use it for validation.

8

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.