# W3c trailing slashes **URL:** \ **Category:** Bug Reports\ **Created:** [November 6, 2022, 5:16pm UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183 "2022-11-06T17:16:56Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Keenick](https://avatars.discourse-cdn.com/v4/letter/k/e68b1a/32.png) [@Keenick](https://forum.pinegrow.com/u/Keenick)\ **Post date:** [November 6, 2022, 5:16pm UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/1 "2022-11-06T17:16:56Z")
Was asked to check my pages, and using [https://validator.w3.org/](https://validator.w3.org/), I got a huge amount of info warnings as to - Trailing slash on void elements has no effect and interacts badly with unquoted attribute values. I removed all the trailing slashes in Pinegrow and upon saving the file for upload, it reapplied the slashes. A example of the warnings: meta charset=“utf-8”/\> meta http-equiv=“X-UA-Compatible” content=“IE=edge”/\> meta name=“viewport” content=“width=device-width, initial-scale=1, shrink-to-fit=no”/\> Slashes are there by design and needed? ---
**Author:** ![AllMediaLab](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/allmedialab/32/2079_2.png) [@AllMediaLab](https://forum.pinegrow.com/u/AllMediaLab)\ **Post date:** [November 6, 2022, 8:37pm UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/2 "2022-11-06T20:37:31Z")
No they are removed in the latest html and can be removed: So `meta charset=“utf-8”/>` Becomes `meta charset=“utf-8”>` This is also the case for script and style links! ---
**Author:** ![Keenick](https://avatars.discourse-cdn.com/v4/letter/k/e68b1a/32.png) [@Keenick](https://forum.pinegrow.com/u/Keenick)\ **Post date:** [November 6, 2022, 8:56pm UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/3 "2022-11-06T20:56:34Z")
Yes, that’s what I did on one of my pages, i removed them all- (like 23 total) in Pinegrow. I saved the page and Pinegrow re-inserted the slashes back. I can remove them with a text editor, but prefer to do it in Pinegrow so the changes are tracked and up to date. Is there a setting in Pinegrow to not insert them, or is it part of the program itself? ---
**Author:** ![AllMediaLab](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/allmedialab/32/2079_2.png) [@AllMediaLab](https://forum.pinegrow.com/u/AllMediaLab)\ **Post date:** [November 8, 2022, 10:02am UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/4 "2022-11-08T10:02:51Z")
I never use Pinegrow for serious webdesign only for animation with Interactions. This year there have been hardly any updates so the best is to contact Pinegrow support for this! ---
**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\ **Post date:** [November 8, 2022, 10:17am UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/5 "2022-11-08T10:17:23Z")
Well, only SIX so far for the installed version [https://pinegrow.com/release\_notes/](https://pinegrow.com/release_notes/) and NINE for the live, online version. > **[Pinegrow Live update log | Pinegrow Web Editor](https://pinegrow.com/download/pinegrow-live/pinegrow-live-update-log/)** > > The exciting story of Pinegrow Live updates. That’s all… So maybe put a post on the #feature-request topic @Keenick , but I’m pretty sure PG Admins will have seen it here. And, welcome aboard @Keenick 🙂 ---
**Author:** ![AllMediaLab](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/allmedialab/32/2079_2.png) [@AllMediaLab](https://forum.pinegrow.com/u/AllMediaLab)\ **Post date:** [November 8, 2022, 10:40am UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/6 "2022-11-08T10:40:51Z")
Yes but have a look at what the updates are! Most are not related to Pure Pinegrow updates! ---
**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\ **Post date:** [November 8, 2022, 7:20pm UTC](https://forum.pinegrow.com/t/w3c-trailing-slashes/7183/7 "2022-11-08T19:20:44Z")
@Keenick thanks for bringing this up. Starting from the next release (out next week), PG will not auto-add / to self contained elements. That said, it won’t remove / from the existing code, so that users will have a choice of using /\> or \> to close such elements.