Note that the mere presence of this header causes premailer to be skipped, i.e., even setting skip_premailer: false will cause premailer to be skipped. The reason for that is that the skip_premailer is a simple header and the value is transformed into a string, causing 'false' to become truthy.

The main thing to note here is that in the derived class, we need to be careful to repeat the protected modifier if this exposure isn’t intentional.

Also, the chances of breaking something are really high, because not even you remember how the code actually works.

Code that is per-component instance should go into a second <script> tag.

The important part I have come to notice is <script type="module"></script> make sure you add that otherwise you will get that error.

I always had to set the height of them literally almost 50% taller than the content itself to accommodate for the innards growing when the form was submitted with errors (the error messaging expanded the height). If I didn’t, the submit button would get cut off making the form un-submittable.

was due to a form that was submitted (ALWAYS SET THAT TYPE-PROPERTY ON YOUR BUTTONS!) after my onclick-event fired, but before my request had any chance to be completed.

The terminal emulator process must also handle terminal control commands, e.g., for resizing the screen.

If you are doing a regular expression check, your function should handle undefined as a potential value.

This is a dynamic value because of hybrid devices which can use a mix of mouse and touch input.

Be careful when returning an object literal in the arrow function shortcut syntax like this. Don't forget the additional parens around the object literal!

The only tricky part is that the error will come back as meta.submitError, so you need to check for both when displaying your error.

A simple rule of thumb: the name of the updated variable must appear on the left hand side of the assignment. For example this... const foo = obj.foo; foo.bar = 'baz';...won't update references to obj.foo.bar, unless you follow it up with obj = obj.

Looks like the problem is that debounce defaults to waiting for 0 ms ... which is completely useless!

When using React hooks there is no concept of onMount because the idea of only running some code on mount leads to writing non-resilient components, components that do one thing when they mount, and then don’t take prop changes into account.

Svelte right now has a lot of opportunities to have component state become out of sync with props.

Note that if you are calling reset() and not specify new initial values, you must call it with no arguments. Be careful to avoid things like promise.catch(reset) or onChange={form.reset} in React, as they will get arguments passed to them and reinitialize your form.

Keep in mind that the values in meta are dependent on you having subscribed to them with the subscription prop.

OK, so what about regular messages? Turns out they are not encrypted after all. Where Signal implements the security and privacy protocols right from the start, Telegram separates the two and offers an additional option. The problem is that not everyone is aware of the Secret Chat option and first-time users may send sensitive information in the regular chat window unknowingly.

Don't try to correct user input by blacklists: This will make the attack work: "<sc<script>ript>".gsub("<script>", "")

You are correct: by default, git log -p shows you the merge commit, but does not even attempt to show a diff for it.

Remember to call super in any subclasses that override teardown.