Why does CSS3 use two names for the same color: aqua = cyan, magenta = fuchsia?
Why does CSS3 duplicate
#00ffff = 0,255,255 and
#FF00FF = (255, 0, 255), spotted by this user?
This duplication confuses, as each is listed separately on the aforementioned CSS3 link.
css
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
add a comment |
Why does CSS3 duplicate
#00ffff = 0,255,255 and
#FF00FF = (255, 0, 255), spotted by this user?
This duplication confuses, as each is listed separately on the aforementioned CSS3 link.
css
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
2
Typically things like this are done simply to preserve backward compatibility. Nothing more and nothing less. The reality is the is non-issue since most developers nowadays don’t use word/name-based color designations anyway. It’s all either a hex triplet or an RGB value of some kind to get colors that are more accurate to a designers vision. And even if there were no deep design concerns, I personally would just code a color as#00ffffor#ff00ffto be explicit about what color I want rendered. Heck, I don’t recall ever using name-based colors since the first website I code back in 1995.
– JakeGould
1 hour ago
add a comment |
Why does CSS3 duplicate
#00ffff = 0,255,255 and
#FF00FF = (255, 0, 255), spotted by this user?
This duplication confuses, as each is listed separately on the aforementioned CSS3 link.
css
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
Why does CSS3 duplicate
#00ffff = 0,255,255 and
#FF00FF = (255, 0, 255), spotted by this user?
This duplication confuses, as each is listed separately on the aforementioned CSS3 link.
css
css
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
asked 3 hours ago
Greek - Area 51 ProposalGreek - Area 51 Proposal
33232549
33232549
2
Typically things like this are done simply to preserve backward compatibility. Nothing more and nothing less. The reality is the is non-issue since most developers nowadays don’t use word/name-based color designations anyway. It’s all either a hex triplet or an RGB value of some kind to get colors that are more accurate to a designers vision. And even if there were no deep design concerns, I personally would just code a color as#00ffffor#ff00ffto be explicit about what color I want rendered. Heck, I don’t recall ever using name-based colors since the first website I code back in 1995.
– JakeGould
1 hour ago
add a comment |
2
Typically things like this are done simply to preserve backward compatibility. Nothing more and nothing less. The reality is the is non-issue since most developers nowadays don’t use word/name-based color designations anyway. It’s all either a hex triplet or an RGB value of some kind to get colors that are more accurate to a designers vision. And even if there were no deep design concerns, I personally would just code a color as#00ffffor#ff00ffto be explicit about what color I want rendered. Heck, I don’t recall ever using name-based colors since the first website I code back in 1995.
– JakeGould
1 hour ago
2
2
Typically things like this are done simply to preserve backward compatibility. Nothing more and nothing less. The reality is the is non-issue since most developers nowadays don’t use word/name-based color designations anyway. It’s all either a hex triplet or an RGB value of some kind to get colors that are more accurate to a designers vision. And even if there were no deep design concerns, I personally would just code a color as
#00ffff or #ff00ff to be explicit about what color I want rendered. Heck, I don’t recall ever using name-based colors since the first website I code back in 1995.– JakeGould
1 hour ago
Typically things like this are done simply to preserve backward compatibility. Nothing more and nothing less. The reality is the is non-issue since most developers nowadays don’t use word/name-based color designations anyway. It’s all either a hex triplet or an RGB value of some kind to get colors that are more accurate to a designers vision. And even if there were no deep design concerns, I personally would just code a color as
#00ffff or #ff00ff to be explicit about what color I want rendered. Heck, I don’t recall ever using name-based colors since the first website I code back in 1995.– JakeGould
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
There are a few clashing/duplicate colors listed in CSS3 because the current web colors list maintained by W3C was descended from the X11 color names file.
Windows X Systems contained a text file that had RGB values that mapped to a certain color. This text file was shipped with all X11 installations.
Mosaic and Netscape Navigator both used the X11 color names as the basis of their colors.
Once the HTML color list was defined, instead of depreciating the duplicate and clashing colors, they simply adopted them into the list. Presumably to prevent breaking older websites/browsers that used X11 colors and for the fact that X11 had defined them first.
That being said, if you use a clashing color name on a site today, it would display the W3C color instead of the X11 color.
answered 1 hour ago
DrZooDrZoo
5,71121638
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1397718%2fwhy-does-css3-use-two-names-for-the-same-color-aqua-cyan-magenta-fuchsia%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
There are a few clashing/duplicate colors listed in CSS3 because the current web colors list maintained by W3C was descended from the X11 color names file.
Windows X Systems contained a text file that had RGB values that mapped to a certain color. This text file was shipped with all X11 installations.
Mosaic and Netscape Navigator both used the X11 color names as the basis of their colors.
Once the HTML color list was defined, instead of depreciating the duplicate and clashing colors, they simply adopted them into the list. Presumably to prevent breaking older websites/browsers that used X11 colors and for the fact that X11 had defined them first.
That being said, if you use a clashing color name on a site today, it would display the W3C color instead of the X11 color.
answered 1 hour ago
DrZooDrZoo
5,71121638
add a comment |
There are a few clashing/duplicate colors listed in CSS3 because the current web colors list maintained by W3C was descended from the X11 color names file.
Windows X Systems contained a text file that had RGB values that mapped to a certain color. This text file was shipped with all X11 installations.
Mosaic and Netscape Navigator both used the X11 color names as the basis of their colors.
Once the HTML color list was defined, instead of depreciating the duplicate and clashing colors, they simply adopted them into the list. Presumably to prevent breaking older websites/browsers that used X11 colors and for the fact that X11 had defined them first.
That being said, if you use a clashing color name on a site today, it would display the W3C color instead of the X11 color.
answered 1 hour ago
DrZooDrZoo
5,71121638
add a comment |
There are a few clashing/duplicate colors listed in CSS3 because the current web colors list maintained by W3C was descended from the X11 color names file.
Windows X Systems contained a text file that had RGB values that mapped to a certain color. This text file was shipped with all X11 installations.
Mosaic and Netscape Navigator both used the X11 color names as the basis of their colors.
Once the HTML color list was defined, instead of depreciating the duplicate and clashing colors, they simply adopted them into the list. Presumably to prevent breaking older websites/browsers that used X11 colors and for the fact that X11 had defined them first.
That being said, if you use a clashing color name on a site today, it would display the W3C color instead of the X11 color.
answered 1 hour ago
DrZooDrZoo
5,71121638
There are a few clashing/duplicate colors listed in CSS3 because the current web colors list maintained by W3C was descended from the X11 color names file.
Windows X Systems contained a text file that had RGB values that mapped to a certain color. This text file was shipped with all X11 installations.
Mosaic and Netscape Navigator both used the X11 color names as the basis of their colors.
Once the HTML color list was defined, instead of depreciating the duplicate and clashing colors, they simply adopted them into the list. Presumably to prevent breaking older websites/browsers that used X11 colors and for the fact that X11 had defined them first.
That being said, if you use a clashing color name on a site today, it would display the W3C color instead of the X11 color.
answered 1 hour ago
DrZooDrZoo
5,71121638
answered 1 hour ago
DrZooDrZoo
5,71121638
answered 1 hour ago
DrZooDrZoo
5,71121638
answered 1 hour ago
DrZooDrZoo
5,71121638
5,71121638
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1397718%2fwhy-does-css3-use-two-names-for-the-same-color-aqua-cyan-magenta-fuchsia%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
2
Typically things like this are done simply to preserve backward compatibility. Nothing more and nothing less. The reality is the is non-issue since most developers nowadays don’t use word/name-based color designations anyway. It’s all either a hex triplet or an RGB value of some kind to get colors that are more accurate to a designers vision. And even if there were no deep design concerns, I personally would just code a color as
#00ffffor#ff00ffto be explicit about what color I want rendered. Heck, I don’t recall ever using name-based colors since the first website I code back in 1995.– JakeGould
1 hour ago