Update intention for insertReplacementText to include writing suggestions

[sanketj]

whatwg/html#9065 proposes the addition of a new attribute called writingsuggestions to control UA-provided writing assistance. When suggestions provided by the UA are accepted by the user, an input event is fired and, per discussion here, insertReplacementText was determined to be the right input type. This change updates the intention of insertReplacementText to include writing suggestion insertions.

Spec PR to introduce new attribute: whatwg/html#10018

---

Preview | Diff

[marcoscaceres]

Please make sure when updating things that affect browser, browser bugs are filed. 🙏 It would have been nice to have a bug filed on WebKit when this change got made.

Can I suggest this group start using a pull request template like:
https://github.com/w3c/geolocation-api/blob/main/.github/PULL_REQUEST_TEMPLATE.md

[marcoscaceres]

Also, it would have been good to involve WebKit folks in this discussion before merging so we could have evaluated if this is the best approach (not saying it's not... just that we are now dealing with fallout of not having discussed the events related to writingsuggestions and what should actually fire and if this is even web compatible)

[johanneswilm]

@marcoscaceres Apple did participate in the discussion of this change in the Web Editing Working Group. Subsequently the Whatwg determined the final name of the attribute.
Should we additionally have included someone specific from Webkit?

[marcoscaceres]

Yeah, it would be great if we could this template in place:
https://github.com/w3c/geolocation-api/blob/main/.github/PULL_REQUEST_TEMPLATE.md

And make sure bugs are always filed when there is a normative spec change.

[johanneswilm]

@marcoscaceres I am not sure that template works well with how we work in this WG given that we talk through each issue with representatives of each browser in the case of all those documents that are not just experimental in nature before they are added.

I can bring this as well as the question of why some browser representatives have not filed bugs with their respective browsers up at the next call. It sounds like some routines there could be improved.