Timeline for locating element by id or css, which is faster?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2019 at 18:14 | answer | added | Moro | timeline score: 3 | |
| Oct 20, 2019 at 14:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 20, 2019 at 13:45 | answer | added | Niels van Reijmersdal | timeline score: 0 | |
| Sep 20, 2019 at 10:41 | answer | added | Akshay Singh Tomar | timeline score: -1 | |
| Sep 19, 2019 at 20:22 | comment | added | Michael Durrant | a developer ~wouldn't~ shouldn't add another element with the same ID. However an app developer or design/layout (UI) developer might add another element using the same class. that's what classes are for. Maybe a new section with another button with same styling is added later | |
| Sep 19, 2019 at 20:20 | comment | added | Michael Durrant | speed should be secondary to future uniquess of selector so ID should be chosen. time diff compared to overall time of test is negligble | |
| Sep 19, 2019 at 8:02 | history | edited | Bharat Mane♦ | CC BY-SA 4.0 |
formatting
|
| Sep 19, 2019 at 7:14 | answer | added | Doanh Nguyen | timeline score: -1 | |
| Sep 19, 2019 at 5:45 | review | First posts | |||
| Sep 19, 2019 at 8:02 | |||||
| Sep 19, 2019 at 5:44 | history | asked | Rahul Raj | CC BY-SA 4.0 |