Syntax error in HTML code

  • Resolved Peter-VARGA

    (@cbdfactum)


    5 years, 5 months ago

    Hi,

    you have an error in the HTML code generation. https://validator.w3.org/nu/?doc=https%3A%2F%2Fcbdfactum.com%2F#l1314c13

    Check the error:

    Error: Element style not allowed as child of element body in this context.
(Suppressing further errors from this subtree.)

From line 1315, column 7; to line 1315, column 13

pt>?</div><style>.maxbu

    And this is the line:

    <style>.maxbutton-1.maxbutton.maxbutton-cbd-categories{position:relative;
text-decoration:none;display:inline-block;vertical-align:middle;
border-color:#a9bf16;width:180px;height:30px;border-top-left-radius:22px;
border-top-right-radius:22px;border-bottom-left-radius:22px;
border-bottom-right-radius:22px;border-style:solid;border-width:2px;
background-color:rgba(169, 191, 22, 1);-webkit-box-shadow:0px 0px 2px 0px #333;
-moz-box-shadow:0px 0px 2px 0px #333;
box-shadow:0px 0px 2px 0px #333}.maxbutton-1.maxbutton.maxbutton-cbd-categories:hover{border-color:#475a23;
background-color:rgba(71, 90, 35, 1);-webkit-box-shadow:0px 0px 2px 0px #475a23;
-moz-box-shadow:0px 0px 2px 0px #475a23;
box-shadow:0px 0px 2px 0px #475a23}.maxbutton-1.maxbutton.maxbutton-cbd-categories .mb-text{color:#fff;font-size:13px;
text-align:center;font-style:normal;font-weight:normal;padding-top:7px;
padding-right:0px;padding-bottom:0px;padding-left:0px;
line-height:1em;box-sizing:border-box;display:block;background-color:unset}.maxbutton-1.maxbutton.maxbutton-cbd-categories:hover .mb-text{color:#fff}?
</style>?

    Is there a way you can fix this in one of the next updates? May be it impacts the behavior in a negative way.

    Thank you

    • This topic was modified 5 years, 5 months ago by Peter-VARGA.
    • This topic was modified 5 years, 5 months ago by Peter-VARGA.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Bas Schuiling

    (@basszje)

    Hi,

    The location of the style tag is very intentional, near the bottom of the page. Would we put it in the top of the document (head section), SEO-tools would start to complain about unneeded output so early.

    The options for the free version are in the bottom ( recommended, fastest ) or just next to the button – which would give the same error.

    That said, the PRO version has an option to load the styling output as if it was a CSS file, which would solve this problem.

    Thread Starter Peter-VARGA

    (@cbdfactum)

    Hi, sorry, but I do not agree that the free version doesn’t match an international standard as W3C is:
    https://en.wikipedia.org/wiki/World_Wide_Web_Consortium

    I think, I can even expect in the free version you put the code in that way that W3C validator doesn’t complain.

    When each plugin developer would do it your way then it would be really a mess. The other errors are from the Theme developer and they reacted already. Please no offence!

    So, is there a way you can generate in the free version a code which is validated by W3C?

    Thank you

    Plugin Author Bas Schuiling

    (@basszje)

    It’s a bit more complicated than that.

    Mozilla (MDN) considers style in body correct – https://developer.mozilla.org/en-US/docs/Web/HTML/Element/style

    From HTML 5.2 and onwards, style is allowed in body – https://www.w3.org/TR/html52/document-metadata.html#the-style-element

    Also check this discussion for more details – https://github.com/whatwg/html/issues/1605

    If there would be an easy work-around I would put it on my list, but in this case I see it as according to the international standards, but not the exact way What-WG decided to do it (to controversy).

    Thread Starter Peter-VARGA

    (@cbdfactum)

    OK, I understand.

    What about this:
    Would it be possible to change the features-policy and move it from the PRO version to the free version so it would be solved?

    Thread Starter Peter-VARGA

    (@cbdfactum)

    Any progress?

    Plugin Author Bas Schuiling

    (@basszje)

    No, we are not working on this currently.

    Thread Starter Peter-VARGA

    (@cbdfactum)

    Hi,

    I quote:
    “That said, the PRO version has an option to load the styling output as if it was a CSS file, which would solve this problem.”

    Can we agree to this procedure:
    When I purchase your PRO version and your plugin doesn’t get validated by W3C validator https://validator.w3.org/ you refund me the money?
    I would check it out immediately when I get the license so I need only 1 day.
    When your plugin gets validated then all is OK and I am another happy client.

    Looking forward.

    Plugin Author Bas Schuiling

    (@basszje)

    No problem. If you’re not happy with something and we can’t work out a solution, that not an issue.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Syntax error in HTML code’ is closed to new replies.