| 10:25 | <smaug> | It is documented somewhere, I think, that the priority order is usually end users, then web devs and then implementers. But where? |
| 10:27 | <sideshowbarker> | smaug: https://www.w3.org/TR/html-design-principles/#priority-of-constituencies |
| 10:28 | <smaug> | thanks |
| 17:49 | <keithamus> | Curious if there's any issues/literature I can read about the ability to create a Range selecting part of an input/textarea's value? Right now we have to create a hidden element, copy over the computed styles and create ranges within that. |
| 21:11 | <smaug> | keithamus: selecting part of input's value? But that value isn't part of dom so it can't be selected |
| 21:15 | <smaug> | I assume you can't for some reason rely on input.selectionStart/End |
| 21:34 | <keithamus> | smaug: predominately we want to get the caret position to place popover menus (like the @ mention autocomplete). We have code to do this but an engineer recently wanted to refresh it and I wondered if there was a web platform solution, or some movement towards one. |
| 21:35 | <smaug> | And for some reason contenteditable isn't an option? |
| 21:35 | <keithamus> | A range is useful because we can getBoundingClientRect to get coords to place the popover. |
| 21:35 | <keithamus> | Yes I’d say it’s not an option. |
| 21:38 | <smaug> | (it would be so nice if github didn't take so many of browser internal shortcut keys 😉 Just trying to open devtools to see what the DOM looks like) |
| 21:39 | <smaug> | ah, it is really textarea |
| 21:43 | <smaug> | I wonder if document itself should have something like getCaretRect(). It would return something reasonable no matter where the caret is - inside some UA widget or designMode or contenteditable |
| 22:59 | <zcorpan> | zcorpan: can I get editor review and/or Mozilla approval for https://github.com/whatwg/html/pull/10291 ? Final close watcher tweak |