-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rel=Noopener #14881
rel=Noopener #14881
Conversation
+1, but you need to be using |
yes, also TinyMCE and JCE use: target="_blank" rel="noopener noreferrer" This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14881. |
Hi Brian, Chris |
OK I thought FF had started supporting this now but I am happy to try and
reverse the order
…On 24 March 2017 at 15:08, chriswagner0815 ***@***.***> wrote:
Hi Brian,
I agree!
Chris
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14881 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPH8WlnbR4J3abtp0gCwrx7X0wAf_Auks5ro9yDgaJpZM4MoN_I>
.
--
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ <http://brian.teeman.net/>
|
what about the positiion of nofollow?
Tinymce seems to suggest it should be
nofollow noopener noreferrer
are you ok with that
…On 24 March 2017 at 15:15, Brian Teeman ***@***.***> wrote:
OK I thought FF had started supporting this now but I am happy to try and
reverse the order
On 24 March 2017 at 15:08, chriswagner0815 ***@***.***>
wrote:
> Hi Brian,
> I agree!
>
> Chris
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#14881 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABPH8WlnbR4J3abtp0gCwrx7X0wAf_Auks5ro9yDgaJpZM4MoN_I>
> .
>
--
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ <http://brian.teeman.net/>
--
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ <http://brian.teeman.net/>
|
Firefox does support it |
Brian, If you were actually asking something else, do let me know! :) |
@chriswagner0815 Nothing in this PR is for internal links. If you look at our existing code for the three links in articles you will see that they are hardcoded to nofollow @C-Lodder said noopener should be changed to noopener noreferrer" cause Firefox doesn't support So I want to check that you are asking me to change in this case the nofollow noopener to nofollow noopener noreferrer I only want to do the work once |
Deciding that lnk s which are hardcoded to nofollow should not be is beyond the scope of this pr |
Hello Brian, I also do not see speficic links in "three articles" - what specific links and articles are you talking about? So I am asking here: for what specific reason are you bringing up the nofollow-attribute and why do you want to add it and for what specific reason did you not bring up nofollow later instead of having it included in the 1st place. Chris |
https://docs.joomla.org/Help36:Content_Article_Manager_Edit#Images_and_Links
I am not adding nofollow ever anywhere |
@brianteeman Later FF versions may support |
@chriswagner0815 this PR fixes a security vulnerability. Feel free to make a separate PR for it. |
Ok. And then the other part of the question refers to where the EXISTING
nofollow should go with those two? Is the order i suggested above ok? Does
it even matter?
…On 24 Mar 2017 4:43 p.m., "Lodder" ***@***.***> wrote:
@brianteeman <https://github.com/brianteeman> rel="noopener noreferrer"
should be this.
Later FF versions may support noopener but Joomla 3.x is supposed to
support FF 13 and above.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14881 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPH8WFEyFSc60PQJZtdLCBQctFOtjzdks5ro_KWgaJpZM4MoN_I>
.
|
The attribute and attribute value order shouldn't matter |
I asked because your first post implied there was an order. Glad we cleared it up and i can finish the pr. |
Hi Charlie, I have asked Brian about this in FB and asked for guidance in understanding. You now bring up, that this does not have anything to do with the pr here, Charlie. I still do not understand the topic at hand but have been asked to share my thoughts. As long as they incorporate my ideas about the nofollow links, everything is fine and we do not have any issue. That is not to say that I now do understand why Brian brought up the incorporation of tinymce's suggestions and why it would be okay to use them. Chris |
@chriswagner0815 as both Charlie and i have said there is nothing in this pr that changes anything related to do with nofollow. Dont believe me then read the code. If you want to change that then this is not the place. |
@C-Lodder updated as requested - quite correct I forgot all about supporting and protecting users with older browsers. |
I have tested this item ✅ successfully on 0b78de0 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14881. |
I have tested this item ✅ successfully on 0b78de0 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14881. |
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/14881. |
@@ -48,20 +48,20 @@ | |||
{ | |||
case 1: | |||
// Open in a new window | |||
echo '<a href="' . htmlspecialchars($link, ENT_COMPAT, 'UTF-8') . '" target="_blank" rel="nofollow">' . | |||
echo '<a href="' . htmlspecialchars($link, ENT_COMPAT, 'UTF-8') . '" target="_blank" rel="nofollow noopener noreferrer">' . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh just notice there are 2 spaces before the rel="..."
, but can be done in a separate PR as this wasn't your doing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not anymore
Let it be stated that I still do not understand what you write about, Brian, and that I have quoted you as follows: I have requested, that you elaborate why this should be "are you ok with that" and I have not received an explanation. As responsible voice of the JOT / seo team, let it be said that I do not understand code and that, despite I have asked, did not receive and explanation in laymens terms. I also quote what I wrote before: If you were actually asking something else, do let me know! :) For that reason, hear my VETO hence I have not understood your mentioning of "nofollow" and your question why anyone should be "okay with that". |
Sorry I cant help it if you wont read the code. If you did you would realise you are not talking sense at all. Your veto is a joke |
Hello Brian, I also requested your help in understanding the issue multiple times. I am not a coder :) - so I have to rely on what you tell me. If you decide to not help, then my joke is your joke and then we all suddenly joke and then the joke becomes a conversation - and then I still am not let into it :-( So again:
Chris :) |
The code change is in the PR - you will have to read it - i am not typing it again here I already answered the question about nofollow #14881 (comment) |
Please review the PR, you don't need a coder to read what's on the "Files changed tab". You will find no additions or removals of |
Thanks @mbabker |
Ok let me just clear some stuff up here. Firstly, there should be absolutely nothing to discuss about This PR is completely different. It has nothing to do with search engines. It fixes a security vulnerability that is quite uncommon among web masters, when using Even though I think there needs to be some form of an automated approach for content, this PR does the basics for 3RD party links in the backend. So, anything regarding |
Hi Brian, hi Charlie, hi Michael, A rel="nofollow" generally means that Google will FOLLOW this link but not pass pagerank. Passing of pagerank may be what we need. You can read about the pagerank patent online https://www.google.com/patents/US6285999 (essence: page rank of linking page = (page ranking of link receiveing page) -1). This is a method of trust and power flow used in ranking and I just would like to make sure we are considering what we do. I still do not have answers to the fact (laymen's terms!) where we are doing this and why we are doing this in these cases. Do we, as mentioned above, presume, that the pages are advertorial pages where we should not pass page rank? Is that presumtion one that we, as a project, should make? Brian: 10 minutes on the phone would have helped me understand this - and I still do not have answers and explanations I need to advise on this topic. I certainly will need your number because now I have about 40 minutes discussion time for the topic and I like to be efficient. Oh, and I will buy you come cigarette packs as well ;) Charlie: see my remarks about how nofollow is handled - hope you have your knowledge enriched, what you wrote before suggests, it should have been. Please answer the according questions! Happy to read of you! |
Please log that as a separate issue then. Yes, there are existing Issues and pull requests should typically be focused on one item. That is an item separate from this change. Happy to discuss the matter, but please let's not get wires crossed on tasks. |
Adding My suggestion is to remove |
@darnux - We're not manipulating any links add by uses, such as those in articles, so tracking isn't an issue. |
@C-Lodder thank you for your reply. What about this?
It causes links in footer which open with a new tab to lose their referrer. That is a problem for affiliate sites or site networks which are using backlinks as a SEO strategy. Would be great if it was configurable in One example where In section 8
|
Hi guys, Does anyone have more information? |
If it is a specific issue for your site you can create a template override |
I raised this issue last year with the JSST but it was rejected as a non-issue and more of a browser bug than something Joomla should be doing anything about.
However as now the Google site auditing tool "lighthouse" (lighthouse report https://developers.google.com/web/tools/lighthouse/audits/noopener) will report this as both a performance and a security issue I believe there is no longer an excuse for not taking action in joomla.
It is a really simple change that will not have any visible effect on a website that uses target="_blank" for any of its menu links and the links generated by tinyMCE already do this even if you were not aware of it. This change will act to harden a Joomla website from malicious sites that trick you into creating links to their sites and has a claimed (by google) performance benefit.
Frontend Menus
Menu items that are links to External Urls with the target set to New Window aka target="_blank". There is no need to apply this to other menu links with the target set to New Window as they are to our own web site and presumably you are not going to attack your own web site.
To test this create two menu items. One an article set to open in a new window and the other an external link set to open in a new window. Only the external link menu will have a rel="noopener" attribute
Fields
We can also create links to external web site using the URL field type and this is hard coded to open in a new window with target="_blank" (that's probably wrong to hard code but it is beyond the scope of this PR)
To test this create a field of type URL for an article and then create an article that uses the field and check to see that the link is rendered with the rel="noopener" attribute
Article Links
With articles we have the option to create up to three links - Link A, Link B, Link C. This PR adds the rel="noopener" attribute to the three options new window, popup window, modal window
To test this enter a link for all three fields in an article using each of the changed options the three options new window, popup window, modal window and check to see that the link is rendered with the rel="noopener" attribute
Contact links
With contacts we have the option to complete a field called Website. This is hard coded to open in a new window with target="_blank" (that's probably wrong to hard code but it is beyond the scope of this PR)
To test this create a contact and complete the website field and check to see that the link is rendered with the rel="noopener" attribute
Com_installer
Every update site has a target="_blank" link to the external extension update site. This adds the rel="noopener" attribute to the link - note this is added to joomla.org links as well as its not possible to differentiate.
Every available update has an infourl that has a target="_blank" link to the external extension site. This adds the rel="noopener" attribute to the link.
External links to non Joomla properties
The rel="noopener" attribute has also been added to several hardcoded links within Joomla to non joomla owned properties.
External links to Joomla properties
I assumed we are not going to attack our own users sites but to prevent tools like limelight from reporting security errors I have also added the rel=noopener to the links to the joomla.org homepage that are publically visible on the admin login page