3 ms·
It seems obvious enough that parent is talking about changing the behavior of innerHTML within their own application, not for browser makers to change the imple
by cxr 10mo ago
It seems obvious enough that parent is talking about changing the behavior of innerHTML within their own application, not for browser makers to change the implementation. It's unfair to take the most uncharitable interpretation and upbraid the other commenter for being insufficiently defensive[1] when they pressed "reply".
1. <https://pchiusano.github.io/2014-10-11/defensive-writing.html https://pchiusano.github.io/2014-10-11/defensive-writing.htm...>
- masklinn 10mo ago> It seems obvious Doesn't seem obvious unless your dutch. Especially as the first things I would think obvious is: if breaking the behaviour of innerHTML is not a concern for your software why keep it at all? Delete the property or make it readonly.
- cxr 10mo ago> Doesn't seem obvious unless your dutch. I don't know what that means. > if breaking the behaviour of innerHTML is not a concern for your software why keep it at all? For the reason that they said.
- shadowgovt 10mo ago> Doesn't seem obvious unless your dutch. I believe this is a reference to the old "Zen of Python," which one gets by running `import this` in the Python REPL. """ There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch. """