holonmatrix
Forum Replies Created
-
Forum: Plugins
In reply to: [MaxButtons - Create buttons] Can rel=”noopener” be applied to buttons?Bas Schuiling:
Thank you for your work. I can now see the noopener
being added together with nofollow when I
do page element inspection.Finally, one thing I would recommend that you consider
in the future is to not make any of the rel tags
mandatory like you did with the noopener tag; people
might be confused just like the above reader
“makikala” did.Instead, I think you should make it so the major
rel tags like nofollow, noopener, and noreferrer
are available as check boxes; along with descriptions
of the effect and consequences of each tag. This
way, your plugin users can be aware and decide
which tags are really needed for their use.I checked SEO > Titles & Metas > Post Type as you said and I found that there was no set variable template. I even tried to add %%sitedesc%% into the Post’s meta description template; but this didn’t even affect/change the feed. Hence, I wouldn’t be able to use my custom meta description into my feed.
Anyway, even if I figured a way to refresh my feed (please tell me how if you know?), I didn’t see anything from the meta template variables that would allow me to put my custom post meta descriptions into the feed.
Tell me your thoughts on this.
Forum: Plugins
In reply to: [MaxButtons - Create buttons] Can rel=”noopener” be applied to buttons?Please read these links for full understanding:
https://developers.google.com/web/tools/lighthouse/audits/noopener
https://jakearchibald.com/2016/performance-benefits-of-rel-noopener/
https://mathiasbynens.github.io/rel-noopener/In summary, these pages state that when target=”_blank” (if that’s what you’re using) opens a new tab/window, the new window can access the old window via window.opener property. If the new page has any malicious script, it can affect the old page through this. The rel=”noopener” sets window.opener to a null value and thus prevents the new window from accessing the old window by using any values originally set in window.opener.
Please continue working on resolving the issue. Also, reply if you still need additional information.