| 10:36 | <cketti> | Many base64 implementations are strict by default and less strict when being passed flags to change the behavior. Variants of forgiving behavior: allowing line breaks (only allowing CRLF is often an option, "required" for email), allowing whitespace, allowing arbitrary non-base64 "characters", allowing invalid padding (in all variants you can imagine). As someone working on email I wish every implementation would be strict by default. That way implementations generating input requiring forgiving decoders would be found and fixed quickly. Sadly, that's not the world we live in. The next best option is to use forgiving decoders, but warn users when non-conforming input is processed. Please don't be forgiving and silent by default. |
| 18:57 | <devsnek> | what do whatwg specs say about adding non-standard methods to things |
| 19:00 | <Andreu Botella (he/they)> | what do whatwg specs say about adding non-standard methods to things |
| 19:01 | <devsnek> | "Documents must not use such extensions" does this mean the document object? |
| 19:02 | <Andreu Botella (he/they)> | I think that's a requirement for authors to not use any such extensions |
| 19:02 | <devsnek> | ahh ok |
| 19:03 | <devsnek> | thanks! |