Timeline for Caching DOM-queries
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2015 at 2:45 | history | edited | 200_success |
edited tags
|
|
| Mar 5, 2015 at 19:36 | history | edited | Jamal | CC BY-SA 3.0 |
deleted 100 characters in body; edited title
|
| Mar 5, 2015 at 13:43 | history | edited | Tommie | CC BY-SA 3.0 |
added 14549 characters in body
|
| Mar 3, 2015 at 19:54 | answer | added | Thriggle | timeline score: 1 | |
| Mar 3, 2015 at 17:29 | comment | added | Mathieu Guindon | On a site like Stack Overflow, indeed it's better to keep it short and to-the-point. Here on Code Review, everything in your code is relevant, reviewers are always free to comment on any aspect of the code - hence it's best to just post your code as it is, and let the accompanying text tell us what your concerns are, to guide reviewers toward the type of answer you're willing to mark as accepted :) | |
| Mar 3, 2015 at 17:24 | comment | added | Tommie | The current codebase isn't that clean since it also contains a lot of temporary demo-stuff etc and is about a mile longer. I thought a slimmer version that highlights the relevant stuff was much better. | |
| Mar 3, 2015 at 17:08 | comment | added | Mathieu Guindon | Welcome to CR! It's best if you include your real code - including the real comments; everything in a code block is subject to be peer reviewed on this site. Are these comments in your actual code? If they're in just for context, it's best to leave them out and explain the context in plain text - as it stands this question is bordering the line of hypothetical/example code; good CR questions put the code front and center, not just as a pretext for a discussion on best practices or brainstorming ideas. | |
| Mar 3, 2015 at 16:23 | review | First posts | |||
| Mar 3, 2015 at 17:08 | |||||
| Mar 3, 2015 at 16:18 | history | asked | Tommie | CC BY-SA 3.0 |