Enforcing noopener noreferrer with grunt-htmllint





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I recently was using create-react-app and noticed that the <a> tag in App.js was using the noopener noreferrer attributes. I also noticed that scattered throughout our code-base, are <a> tags which do not use the above attributes.



I wanted to, using grunt-htmllint, add a rule that would enforce the adding of these attributes but am having trouble with the value that I should add to what I think would be "tag-req-attr".



The documentation for the rule is listed here, but the usage for me is confusing. How can I set the specified <a> tag to include said rules?



I am looking for a way to enforce that the rel attribute contains both noopener and noreferrere.g.:



<a href="#" target="_blank" rel="noopener noreferrer">My Link</a>



Thanks






gruntjs static-analysis







share|improve this question

























  • You probably want the link-req-noopener option instead. So in the options object of your grunt-htmllint task you add 'link-req-noopener': true . However the description for link-rel-no-opener states: "If set, each a tag with target="_blank" must have a rel="noopener" or rel="noreferrer" attribute." - Intentional emphasis on "or", so I don't think it works with both values present.

    – RobC
    Jan 4 at 19:23




















0















I recently was using create-react-app and noticed that the <a> tag in App.js was using the noopener noreferrer attributes. I also noticed that scattered throughout our code-base, are <a> tags which do not use the above attributes.



I wanted to, using grunt-htmllint, add a rule that would enforce the adding of these attributes but am having trouble with the value that I should add to what I think would be "tag-req-attr".



The documentation for the rule is listed here, but the usage for me is confusing. How can I set the specified <a> tag to include said rules?



I am looking for a way to enforce that the rel attribute contains both noopener and noreferrere.g.:



<a href="#" target="_blank" rel="noopener noreferrer">My Link</a>



Thanks






gruntjs static-analysis







share|improve this question

























  • You probably want the link-req-noopener option instead. So in the options object of your grunt-htmllint task you add 'link-req-noopener': true . However the description for link-rel-no-opener states: "If set, each a tag with target="_blank" must have a rel="noopener" or rel="noreferrer" attribute." - Intentional emphasis on "or", so I don't think it works with both values present.

    – RobC
    Jan 4 at 19:23
















0












0








0








I recently was using create-react-app and noticed that the <a> tag in App.js was using the noopener noreferrer attributes. I also noticed that scattered throughout our code-base, are <a> tags which do not use the above attributes.



I wanted to, using grunt-htmllint, add a rule that would enforce the adding of these attributes but am having trouble with the value that I should add to what I think would be "tag-req-attr".



The documentation for the rule is listed here, but the usage for me is confusing. How can I set the specified <a> tag to include said rules?



I am looking for a way to enforce that the rel attribute contains both noopener and noreferrere.g.:



<a href="#" target="_blank" rel="noopener noreferrer">My Link</a>



Thanks






gruntjs static-analysis







share|improve this question
















I recently was using create-react-app and noticed that the <a> tag in App.js was using the noopener noreferrer attributes. I also noticed that scattered throughout our code-base, are <a> tags which do not use the above attributes.



I wanted to, using grunt-htmllint, add a rule that would enforce the adding of these attributes but am having trouble with the value that I should add to what I think would be "tag-req-attr".



The documentation for the rule is listed here, but the usage for me is confusing. How can I set the specified <a> tag to include said rules?



I am looking for a way to enforce that the rel attribute contains both noopener and noreferrere.g.:



<a href="#" target="_blank" rel="noopener noreferrer">My Link</a>



Thanks






gruntjs static-analysis




gruntjs static-analysis






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 4 at 19:06







User 5842

















asked Jan 4 at 16:00









User 5842User 5842

877925




877925













  • You probably want the link-req-noopener option instead. So in the options object of your grunt-htmllint task you add 'link-req-noopener': true . However the description for link-rel-no-opener states: "If set, each a tag with target="_blank" must have a rel="noopener" or rel="noreferrer" attribute." - Intentional emphasis on "or", so I don't think it works with both values present.

    – RobC
    Jan 4 at 19:23





















  • You probably want the link-req-noopener option instead. So in the options object of your grunt-htmllint task you add 'link-req-noopener': true . However the description for link-rel-no-opener states: "If set, each a tag with target="_blank" must have a rel="noopener" or rel="noreferrer" attribute." - Intentional emphasis on "or", so I don't think it works with both values present.

    – RobC
    Jan 4 at 19:23



















You probably want the link-req-noopener option instead. So in the options object of your grunt-htmllint task you add 'link-req-noopener': true . However the description for link-rel-no-opener states: "If set, each a tag with target="_blank" must have a rel="noopener" or rel="noreferrer" attribute." - Intentional emphasis on "or", so I don't think it works with both values present.

– RobC
Jan 4 at 19:23







You probably want the link-req-noopener option instead. So in the options object of your grunt-htmllint task you add 'link-req-noopener': true . However the description for link-rel-no-opener states: "If set, each a tag with target="_blank" must have a rel="noopener" or rel="noreferrer" attribute." - Intentional emphasis on "or", so I don't think it works with both values present.

– RobC
Jan 4 at 19:23














1 Answer
1






active

oldest

votes


















0














According to, https://developers.google.com/web/tools/lighthouse/audits/noopener, it looks like noreferrer handles both cases: rel="noreferrer" attribute has the same effect, but also prevents the Referer header from being sent to the new page.



In that case, simply using the link-req-noopener rule should be sufficient.






share|improve this answer
























  • The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

    – RobC
    Jan 4 at 19:33












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54042333%2fenforcing-noopener-noreferrer-with-grunt-htmllint%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














According to, https://developers.google.com/web/tools/lighthouse/audits/noopener, it looks like noreferrer handles both cases: rel="noreferrer" attribute has the same effect, but also prevents the Referer header from being sent to the new page.



In that case, simply using the link-req-noopener rule should be sufficient.






share|improve this answer
























  • The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

    – RobC
    Jan 4 at 19:33
















0














According to, https://developers.google.com/web/tools/lighthouse/audits/noopener, it looks like noreferrer handles both cases: rel="noreferrer" attribute has the same effect, but also prevents the Referer header from being sent to the new page.



In that case, simply using the link-req-noopener rule should be sufficient.






share|improve this answer
























  • The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

    – RobC
    Jan 4 at 19:33














0












0








0







According to, https://developers.google.com/web/tools/lighthouse/audits/noopener, it looks like noreferrer handles both cases: rel="noreferrer" attribute has the same effect, but also prevents the Referer header from being sent to the new page.



In that case, simply using the link-req-noopener rule should be sufficient.






share|improve this answer













According to, https://developers.google.com/web/tools/lighthouse/audits/noopener, it looks like noreferrer handles both cases: rel="noreferrer" attribute has the same effect, but also prevents the Referer header from being sent to the new page.



In that case, simply using the link-req-noopener rule should be sufficient.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 4 at 19:26









User 5842User 5842

877925




877925













  • The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

    – RobC
    Jan 4 at 19:33



















  • The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

    – RobC
    Jan 4 at 19:33

















The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

– RobC
Jan 4 at 19:33





The link-req-noopener option fails if both noopener and noreferrer exist as values for the rel attribute as per the html fragment in your question.

– RobC
Jan 4 at 19:33




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54042333%2fenforcing-noopener-noreferrer-with-grunt-htmllint%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Monofisismo

Image
Monofisismo (do grego: monos - "único, singular" e physis - "natureza") é o ponto de vista cristológico que defende que, depois da união do divino e do humano na encarnação histórica, Jesus Cristo, como encarnação do Filho ou Verbo ( Logos ) de Deus, teria apenas uma única "natureza", a divina, e não uma síntese de ambas. O monofisismo é contraposto pelo diofisismo (ou "diafisismo"), que defende que Jesus preservou em si as duas naturezas. Historicamente, o monofisismo se refere primordialmente à posição dos que (especialmente no Egito e, em menor grau, na Síria) rejeitaram as decisões do Concílio de Calcedônia em 451 (o quarto concílio ecumênico). Os membros mais moderados entre eles, porém, defendem a teologia "miafisita", que se tornou a oficial para as Igrejas Ortodoxas Orientais. Muitos ortodoxos orientais, porém, rejeitam essa classificação, mesmo como um termo genérico, mas ele é amplamente utilizado na literatura históri...
Read more

Angular Downloading a file using contenturl with Basic Authentication

Image
0 I have a contentUrl when user clicks on that,file should be downloaded. If I try to browse the contentUrl in the browser it asks for Userid and password.I believe this is Basic Authentication.I dont want user to enter UserId and Password so I am passing it Authorization(Please see below code). Url looks some thing like this: http://XXX.XXX.XX.XXX:8080/flowable-rest/service/runtime/tasks/90875/attachments/90555/content let username : string = 'admin'; let pwd : string = 'test'; let headers = new Headers(); headers.set('Accept', 'text/json'); headers.append('Content-Type', 'application/json'); headers.set('Access-Control-Allow-Origin', '*'); headers.set('Access-Control-Allow-Methods','POST, GET, OPTIONS, PUT, DELETE'); head...
Read more

Olmecas

Image
Monumento 1, uma das quatro cabeças colossais encontradas em La Venta, com altura aproximada de 3 metros Olmecas é a designação do povo e da civilização que estiveram na origem da antiga cultura pré-colombiana da Mesoamérica e que se desenvolveram nas regiões tropicais do centro-sul do atual México durante o pré-clássico, próximo de onde hoje estão localizados os estados mexicanos de Veracruz e Tabasco, no Istmo de Tehuantepec, numa zona designada área nuclear olmeca. A cultura olmeca floresceu nesta região aproximadamente entre 1500 e 400 a.C., [ 1 ] e crê-se que tenha sido a civilização-mãe de todas as civilizações mesoamericanas que se desenvolveram posteriormente. [ 2 ] No entanto, desconhece-se a sua exacta filiação étnica, ainda que existam numerosas hipóteses colocadas para tentar resolver esta questão. O etnónimo olmeca foi cunhado pelos arqueólogos do século XX, e não devem confundir-se com os muito posteriores olmecas-xicalancas que ocuparam vários locais do México...
Read more