Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Raul P.

    (@alignak)

    The validation is just a guideline, it’s telling you that it doesn’t recognize the fvm-script-delay as a javascript type, because it’s not part of the specification. It’s telling you, that there is a error so the scripts won’t run.

    But creating the error and not being part of the specification is intended. It’s required to bypass javascript execution there, and then there will be a proper script at the bottom, that runs these types later. If it was valid, the script would not be delayed.

    This is similar to what cloudflare does, as well as any other plugin that delays javascript. Being invalid, doesn’t mean it does not work. Only that it’s unexpected, according to the specification on HTML.

    https://community.cloudflare.com/t/rocketloader-causing-w3c-errors/17991/3

    If you want to delay the scripts, you have to make them invalid so the browser will ignore them. Then later, you manually execute them on interaction or some other rule.

    Thread Starter casacochecurro

    (@casacochecurro)

    Thank you Raul, I think I understand right now much better and I won’t care about it.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Validate HTML error in fvm-script-delay’ is closed to new replies.