Making Genesis W3C Valid? Remove unnecessary TYPE attribute from menu JavaScript

[cbryantMember]

When trying to validate a Genesis Child Theme (the Genesis Sample child), the W3C Validator gives this error:

The type attribute is unnecessary for JavaScript resources.

There's plenty of help/snippets out there for removing the TYPE attribute from enqueued files. But they don't work on the Genesis Responsive Menu js that gets inserted in the footer.

Does anyone have any idea how to remove the unnecessary TYPE attribute from this JavaScript resource?

Thanks.

[Victor FontModerator]

While the script is being loaded by the Genesis Sample theme in functions.php, Genesis is simply executing the WordPress wp_enqueue_script to do so. The type attribute is inserted by WordPress, not Genesis. You're best bet for finding a solutions is to Google and look at the many recommendations out there.

---

Regards,

Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?

[Victor FontModerator]

I did my own Google search and found some code that works:

https://pastebin.com/BbiUUwbZ

---

Regards,

Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?

[cbryantMember]

Hi Victor,

Thank you for responding.
I apologize for not replying back sooner.
I think the forum notification went to spam.

Either way - I'll check out the code you found and reply again.

Thanks!

[cbryantMember]

Hi Victor,

I checked out the code you'd found online.
I actually already have that code in my theme - and it works great for enqueued js and css.

However, that code does not remove the TYPE attribute from the Genesis Responsive Menu setup script. That script is used/called (my js ignorance is showing) using wp_localize_script (not enqueue). So my hunch is that has something to do with it.

I need to move on to other issues for now.
But I'm determined to validate this Genesis theme.
So if I get a solution - I'll share here.
And hopefully, if someone else does, they will too.

All the best,

[Victor FontModerator]

The code I provided for you works for me with the responsive script. I tested it with multiple themes in my local environment and edited it for performance. Code used with wp_localize_script still requires a script to be enqueued. All wp_localize_script does is setup a script for translation. It has nothing to do with enqueuing.

Also if you look at the sample theme's functions.php. You'll see the responsive script is being enqueued right before wp_localize_script is called.

https://codex.wordpress.org/Function_Reference/wp_localize_script

---

Regards,

Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?

[Author]

Posts