You know 3rd-party libraries inject bare ˂style˃ tags into your ˂head˃, and you‘ve surely hard-coded such tags yourself. But how about when your code needs a reliable reference to one particular “anonymous local stylesheet”? →
Not saying these errors have ever happened in reality, but if your company demands full coverage you’ll want to account for them. →
Need labels for checkboxes to look different from labels for radios and labels for selects? Here’s how that’s done. →
I thought it was invalid, too. But the WHATWG is the source of truth. →
I can’t tell you to never put JS inside a Rich Text area (in Form Editor). It definitely feels more organized. But you need to step up your exception-handling game if you do it. →
An inline <script> tag — where JS code appears directly in the HTML markup — isn’t just a cosmetic container. There’s a huge difference between having your code in one big <script> and using multiple tags. →
Here’s how to wrap up the values from a lead’s last form post into a single Textarea field. (In addition to individual fields, of course.) Having the form post in one place adds precision and flexibility to Send Alert and other cool stuff. →
Revisiting the “Poison Pill” concept from years ago, and providing a better error-thrower macro. →