Timeline for RGB to hex and hex to RGB
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2022 at 16:18 | review | Suggested edits | |||
| May 23, 2022 at 10:37 | |||||
| Jan 9, 2022 at 0:07 | history | edited | FelipeC | CC BY-SA 4.0 |
Remove arrow functions which add no value, and cleanup style to *my* style.
|
| S Nov 11, 2021 at 7:09 | history | suggested | theProCoder | CC BY-SA 4.0 |
improved formatting
|
| Nov 10, 2021 at 9:43 | review | Suggested edits | |||
| S Nov 11, 2021 at 7:09 | |||||
| Oct 5, 2020 at 10:22 | history | edited | FelipeC | CC BY-SA 4.0 |
Cleanup and update
|
| Jun 29, 2020 at 23:11 | comment | added | TurnerOC | this also worked for me, when the other examples on this page didnt. i wanted to convert RGB 100, 100, 100 to HEX, other examples on this page returned "#100100100" - whilst this example, correctly returned "#646464" | |
| Nov 15, 2017 at 15:40 | comment | added | FelipeC | Because blue would be #FF, we add 0x1000000, so it's #10000FF, and then we remove the first "1". | |
| Sep 11, 2017 at 17:43 | comment | added | hackjutsu |
A little bit confused about the rgb2hex method. Why do we add 0x1000000 to rgb, and why we need to call .slice(1) at last?
|
|
| Aug 25, 2015 at 20:59 | history | edited | FelipeC | CC BY-SA 3.0 |
Fix error
|
| Nov 4, 2013 at 10:04 | history | answered | FelipeC | CC BY-SA 3.0 |