15:40:44 RRSAgent has joined #editing 15:40:44 logging to https://www.w3.org/2020/06/12-editing-irc 15:47:27 johanneswilm has changed the topic to: https://lists.w3.org/Archives/Public/public-editing-tf/2020Jun/0000.html 16:05:28 agenda+ https://github.com/w3c/editing/pull/262 16:06:18 GameMaker has joined #editing 16:08:53 johanneswilm new directory structure broke links, how to fix? 16:09:03 https://github.com/w3c/editing/tree/gh-pages/docs 16:09:10 issue #262 16:12:22 bocupp: proposes directory per spec then fix the links 16:13:02 johanneswilm: in the past this was only a temporary home for docs 16:13:28 bocupp: is it a hard requirement that we need to move the docs? 16:14:12 johanneswilm: generally agree with Bo's suggestion, even if docs do graduate and move elsewhere we don't need to keep moving the docs that are here in this repo 16:16:07 johanneswilm: will take the action to rearrange and fix links 16:18:14 agenda+ https://github.com/w3c/editing/issues/252 16:21:15 bocupp: I think its by design that we don't have a way to disable all future commands - this would do it 16:22:53 whsieh: some tension between what browser wants to deliver and what editors expect 16:23:22 johanneswilm: that's right, this approach makes its possible to craft an allow-list, not just a deny-list 16:26:09 whsieh: compromise is basically that its a little harder to block all future commands because you need to write script 16:29:34 bocupp: not sure writing JS is real deterrent to keep authors from defaulting to allow-list 16:31:09 whsieh: agree point about making it easier doesn't seem compelling... there are some complexities adding second attribute contenteditable-enabled since now it can conflict with contenteditable-disabled 16:33:33 whsieh: preference for JS way to make allow-list out of contenteditable-disabled 16:34:31 johanneswilm: prefers enabled and disabled attribute b/c of symmetry, JS solution is separate preference, ce-disabled only is least favorite approach 16:35:36 present + 16:35:46 GameMaker: agree with whsieh 16:36:58 bocupp: not opposed to JS solution, let's bring it back then 16:39:32 johanneswilm: with JS solution, you can query it for available commands, note that the list should be uniform even if the actual enabled commands are influenced by configuration options set by the user to avoid fingerprinting 16:41:02 johanneswilm: no requirement that browser has all the listed commands implemented 16:42:02 johanneswilm: action then is to bring back from original ce-disabled spec (pre-MSFT changes) the JS enumeration 16:42:52 bocupp: I can take that action 16:43:39 agenda+ https://github.com/w3c/editing/issues/176 16:43:50 bocupp: I will work on landing PR while Grisha is out 16:44:32 whsieh: new topic: Undo API update 16:45:38 whsieh: web apps WG is probably ideal, but it might require recharter, so thinking WICG is right forum 16:51:39 https://github.com/w3c/editing/blob/gh-pages/CHARTER.md 16:54:37 https://www.w3.org/2019/05/webapps-charter.html 17:23:50 johanneswilm has joined #editing 17:23:59 rrsagent, bye 17:25:01 rrsagent, set world-visible 17:25:01 I'm logging. I don't understand 'set world-visible', johanneswilm. Try /msg RRSAgent help 17:25:23 rrsagent, set logs world-visible 17:25:27 rrsagent, bye 17:25:27 I see no action items