| 02:16 | <domfarolino> | The first two WHATWG PRs with the "impacts documentation" label! https://github.com/search?q=org%3Awhatwg+label%3A%22impacts+documentation%22 |
| 05:02 | <Alystair> | how come typing into a text area doesn't make textarea:empty false? |
| 05:03 | <Alystair> | same with the inverse, erasing contents |
| 05:04 | <Alystair> | https://jsfiddle.net/vj89o7wL/ example |
| 05:44 | <Alystair> | I'm guessing it has something to do with input nots updating value because changes aren't actually reflected in DOM |
| 06:04 | <domfarolino> | annevk: You around? |
| 06:57 | <annevk> | domfarolino: on and off |
| 07:03 | <domfarolino> | annevk: if an event handler string is evaluated in an iframe, adopted by another document, and evaluated again, does the "current settings object" that might be used by code in the handler change due to adoption? |
| 07:04 | <domfarolino> | Or would it stay "equal" to that of the document in which the handler was compiled/run? (my guess is it changes, but unsure) |
| 07:07 | <annevk> | domfarolino: current settings object is more about the code triggering the handler, no? |
| 07:08 | <annevk> | domfarolino: I don't think it should be recompiled as things stand |
| 07:08 | <annevk> | domfarolino: but I'm not a 100% on this |
| 07:10 | <domfarolino> | annevk: unsure about the “code triggering” part, what if the handler was triggered by a click for example (this question is related to https://github.com/whatwg/html/issues/3295) |
| 07:12 | <domfarolino> | Agreed though, I don't think it should be recompiled |
| 07:16 | <annevk> | domfarolino: I guess in that case I would assume the current settings object wouldn't have changed, but I'm not sure how it's defined in situations like this |
| 07:16 | <annevk> | domfarolino: Domenic and bz have a much better handle on this |
| 07:16 | <domfarolino> | annevk: Makes sense, yeah I'm sure they |
| 07:17 | <domfarolino> | they'll have some insight on this, thank you |