minutes, call 2024-04-11

[17:02] <smaug> scribe: smaug
[17:02] <smaug> topic: https://github.com/w3c/edit-context/issues/94
[17:02] * github-bot Because I don't want to spam github issues
unnecessarily, I won't comment in that github issue unless you write
"Github: <issue-url> | none" (or "Github issue: ..."/"Github topic: ...").
[17:02] --> whsieh (~whsieh@e1e31c0d.publics.cloak) has joined this channel.
[17:03] <smaug> dandclark: we did discuss about this last time
[17:04] <smaug> EditContext handles certain kinds of input, but doesn't
handle formatting kinds of cases
[17:04] <smaug> need to document better which should be handled
[17:05] <smaug> the bullet points johanneswilm listed in the issue are a
good starting point
[17:06] <smaug> insertLineBreak and such can be complicated if the
selection isn't collapsed
[17:07] <smaug> EditContext wouldn't ever fire event for the cases when the
internal state doesn't change
[17:08] <johanneswilm> q+
[17:08] <smaug> dandclark: which commands should be handled automatically
and which shouldn't?
[17:10] --> sanketj_ (~uid392014@9347813c.public.cloak) has joined this
channel.
[17:10] <smaug> johanneswilm: In many cases it would be good that browser
takes care of the command. Author is still able to decide by cancelling
beforeinput, correct?
[17:11] <dandclark> q+
[17:11] <smaug> johanneswilm: is entering linebreak complicated also in
text buffer case?
[17:11] <smaug> dandclark: yeah, beforeinput can be cancelled
[17:12] <smaug> dandclark: some of these commands rely on formatting
context, I think
[17:13] <smaug> ...which would be a clear reason why EditContext couldn't
handle those, since it has just text buffer
[17:14] <smaug> smaug: feels like this needs some more investigation
[17:15] <smaug> johanneswilm: so dandclark will work on this more, and
explain why each case should be excluded
[17:15] <smaug> dandclark: feedback from other vendors would be good
[17:17] <smaug> scribe: dandclark
[17:20] <dandclark> Topic: getTargetRanges of beforeinput differ between
browsers (should not happen in EditContext)
[17:20] <dandclark> github: https://github.com/w3c/input-events/issues/146
[17:20] * github-bot OK, I'll post this discussion to
https://github.com/w3c/input-events/issues/146 (getTargetRanges of
`beforeinput` differ between browsers (should not happen in EditContext)).
[17:20] <dandclark> smaug: Can someone look and confirm that browsers other
than Firefox have different behavior on mac vs windows?
[17:20] <dandclark> dandclark: I can, if noone else gets to this
[17:20] <dandclark> smaug: I will keep pinging Masayuki for feedback
[17:21] <dandclark> whsieh: In webkit we use the selection range for most
typing commands when editing
[17:21] <dandclark> whsieh: Not sure what getTargetRanges returns for
transpose. Should probably return both? Because replacing both characters
with swapped content
[17:22] <dandclark> johanneswilm: And they have to be next to each other
-- 
Johannes Wilm, PhD
tel +46766922220
https://www.johanneswilm.org