W3C – plugin code doesn't validate

Viewing 2 replies - 1 through 2 (of 2 total)
  • Benjamin

    (@benjaminowens)

    Validation is always useful but at the same time there are multiple standards that make this difficult: NextGen users may have themes that are HTML4, XHTML, or HTML5. We’ve done our best to ensure that everything is as close to the W3 standards as possible but we also have to be practical about providing gallery displays that look nice for everybody ‘out of the box’ and that can mean including non-standard browser specific attributes (like those with the -moz and -webkit prefix).

    If proper W3 validity is a priority we do offer customization through custom templates and the NGG_SKIP_LOAD_SCRIPTS constant could let you omit our CSS entirely in favor of your own choice.

    Thread Starter vickea

    (@vickea)

    Thank you for the response Benjamin. I do understand what you’re saying and that catering for many users with varying situations is difficult at the best of times.

    LOL! No…. I have no intention of writing my own for this.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘W3C – plugin code doesn't validate’ is closed to new replies.