1. Start your debugger 2. Trigger an action 3. Skip the first 10 breakpoints you forgot to remove last time 4. Realize you forgot to set a new breakpoint 5. Abort 6. Set a new breakpoint 7. Retrigger the action
👇🏻
8. Sigh because you need to skip the 10 first breakpoints again 9. Realize you accidentally also skipped your new breakpoint 10. Retrigger the action 11. Skip and remove each of the first 10 breakpoints you forgot to remove once again 12. Stop at the right breakpoint
👇🏻
13. Stare at your screen and think 14. Realize you should have set the breakpoint earlier 15. Abort 16. Set a new breakpoint 17. Retrigger the action 18. Stare at your screen again 19. Think and cry a little 20. Take a break
👇🏻
21. Gome back and stare at your screen again 22. Decide to add log statements 23. Lose hope again 24. Take a closer look 25. Line 162 should be a + b * z and not a - b * z 26. Close the debugger and forget to remove your breakpoints 27. Fix the bug
• • •
Missing some Tweet in this thread? You can try to
force a refresh
You can force a user's browser to open a new tab when clicking on a link by adding target="_blank" to it.
But you should always add rel="noreferrer" to it!
The reason and an explanation in a short thread. ↓
When a new tab opens, the page loaded gets access to the window.opener attribute. If the site has malicious code in it, it can use the opener property to redirect your page to another malicious site that might harm the user.
1/7
Adding rel="noreferrer" prevents that the window.opener property is accessible for the site linked to and additionally skips sending a Referer HTTP header to that page with your website's URL.
2/7