validator.w3.org errors

[misionisParticipant]

Hello, plugin causes two errors in https://validator.w3.org

1.
Error: Attribute asp-compact not allowed on element div at this point.
From line 2328, column 3; to line 2332, column 25
id=”1″>↩ <div class=’asp_w asp_m asp_m_1 asp_m_1_1 wpdreams_asp_sc wpdreams_asp_sc-1 ajaxsearchpro asp_main_container asp_compact’↩ data-id=”1″↩ data-name=”wyszukiwarka”↩ asp-compact=”closed” data-instance=”1″↩ id=’ajaxsearchpro1_1′>↩↩ <d
Attributes for element div:
Global attributes

2.
Error: Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.)
From line 2718, column 2865; to line 2718, column 2907
;</script><style id=’core-block-supports-inline-css’>↩.wp-b
Contexts in which element style may be used:
Where metadata content is expected.
In a noscript element that is a child of a head element.
Content model for element body:
Flow content.

This is important, because of accessibility law.

I’m not aalowed to give You admin permition and ftp access.

https://azxwkjkmxg.cfolks.pl/wp-admin
login: Subskrybent
pass: Nowastronampwik1

[Ernest MarcinkoKeymaster]

Hi,

Thank you very much for the reports.

1. I think we can fix this for the upcoming release by moving the attribute to a “data-” attribute, that should resolve it then. I have moved this issue to the issue tracker.

2. This does not seem to be related to our plugin though. The element ID core-block-supports-inline-css is not part of Ajax Search Pro, it is a generic block style coming from WordPress core, very likely Gutenberg block editor styles.

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[misionisParticipant]

Hi, thanks for You reply.

Ad. 1. It would be great
Ad. 2. Yes, thats true. It was sticking to Your script, thats why I thought It’s Yours 😀

The solution found:

add_action(‘wp_footer’, function () {
wp_dequeue_style(‘core-block-supports’);
});

Greetings!

[Ernest MarcinkoKeymaster]

You are welcome! Expect the next update around the middle of next week, including a fix for thi issue.

If you don’t mind, I will close this topic soon and mark it as resolved, feel free to open another one if you have other questions or issues.

If you like the plugin and have not rated already, feel free to leave a rating on your codecanyon downloads page, it’s greatly appreciated.

Best,
Ernest Marcinko
If you like my products, don't forget to rate them on codecanyon :)

[Author]

Posts