How to disable Chrome element unique-id checking
is it possible to disable chrome checking of dom unique-id element in console?
but i want to disable it using javascript code.
dom unique-id error:
unique-id
add a comment |
is it possible to disable chrome checking of dom unique-id element in console?
but i want to disable it using javascript code.
dom unique-id error:
unique-id
Is there a reason you can't give the elements unique ID's?
– MyStackRunnethOver
Nov 20 '18 at 2:55
1
Also, in the future, please copy-and-paste error messages into your question as text, rather than linking to them. It makes them much easier to see, read, google, etc. :)
– MyStackRunnethOver
Nov 20 '18 at 2:55
the project is already build by other teams and they're loading all the views and using SammyJS for routing. they just show/hide the pages. the problem is some of the page has the same element that's why they put the same id in it. I just want a quick fix so that I don't have to modify all the pages and js codes affected. Is it possible to disable the chrome checking of DOM unique-id?
– unknownDevice
Nov 20 '18 at 5:53
add a comment |
is it possible to disable chrome checking of dom unique-id element in console?
but i want to disable it using javascript code.
dom unique-id error:
unique-id
is it possible to disable chrome checking of dom unique-id element in console?
but i want to disable it using javascript code.
dom unique-id error:
unique-id
unique-id
edited Nov 20 '18 at 5:38
lagom
3,55181937
3,55181937
asked Nov 20 '18 at 2:49


unknownDeviceunknownDevice
1
1
Is there a reason you can't give the elements unique ID's?
– MyStackRunnethOver
Nov 20 '18 at 2:55
1
Also, in the future, please copy-and-paste error messages into your question as text, rather than linking to them. It makes them much easier to see, read, google, etc. :)
– MyStackRunnethOver
Nov 20 '18 at 2:55
the project is already build by other teams and they're loading all the views and using SammyJS for routing. they just show/hide the pages. the problem is some of the page has the same element that's why they put the same id in it. I just want a quick fix so that I don't have to modify all the pages and js codes affected. Is it possible to disable the chrome checking of DOM unique-id?
– unknownDevice
Nov 20 '18 at 5:53
add a comment |
Is there a reason you can't give the elements unique ID's?
– MyStackRunnethOver
Nov 20 '18 at 2:55
1
Also, in the future, please copy-and-paste error messages into your question as text, rather than linking to them. It makes them much easier to see, read, google, etc. :)
– MyStackRunnethOver
Nov 20 '18 at 2:55
the project is already build by other teams and they're loading all the views and using SammyJS for routing. they just show/hide the pages. the problem is some of the page has the same element that's why they put the same id in it. I just want a quick fix so that I don't have to modify all the pages and js codes affected. Is it possible to disable the chrome checking of DOM unique-id?
– unknownDevice
Nov 20 '18 at 5:53
Is there a reason you can't give the elements unique ID's?
– MyStackRunnethOver
Nov 20 '18 at 2:55
Is there a reason you can't give the elements unique ID's?
– MyStackRunnethOver
Nov 20 '18 at 2:55
1
1
Also, in the future, please copy-and-paste error messages into your question as text, rather than linking to them. It makes them much easier to see, read, google, etc. :)
– MyStackRunnethOver
Nov 20 '18 at 2:55
Also, in the future, please copy-and-paste error messages into your question as text, rather than linking to them. It makes them much easier to see, read, google, etc. :)
– MyStackRunnethOver
Nov 20 '18 at 2:55
the project is already build by other teams and they're loading all the views and using SammyJS for routing. they just show/hide the pages. the problem is some of the page has the same element that's why they put the same id in it. I just want a quick fix so that I don't have to modify all the pages and js codes affected. Is it possible to disable the chrome checking of DOM unique-id?
– unknownDevice
Nov 20 '18 at 5:53
the project is already build by other teams and they're loading all the views and using SammyJS for routing. they just show/hide the pages. the problem is some of the page has the same element that's why they put the same id in it. I just want a quick fix so that I don't have to modify all the pages and js codes affected. Is it possible to disable the chrome checking of DOM unique-id?
– unknownDevice
Nov 20 '18 at 5:53
add a comment |
0
active
oldest
votes
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385510%2fhow-to-disable-chrome-element-unique-id-checking%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53385510%2fhow-to-disable-chrome-element-unique-id-checking%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Is there a reason you can't give the elements unique ID's?
– MyStackRunnethOver
Nov 20 '18 at 2:55
1
Also, in the future, please copy-and-paste error messages into your question as text, rather than linking to them. It makes them much easier to see, read, google, etc. :)
– MyStackRunnethOver
Nov 20 '18 at 2:55
the project is already build by other teams and they're loading all the views and using SammyJS for routing. they just show/hide the pages. the problem is some of the page has the same element that's why they put the same id in it. I just want a quick fix so that I don't have to modify all the pages and js codes affected. Is it possible to disable the chrome checking of DOM unique-id?
– unknownDevice
Nov 20 '18 at 5:53