Skip to content

rm Caret Movement per Google feedback on charter poll. editing-2025.html#535

Closed
tantek wants to merge 1 commit into
gh-pagesfrom
tantek-patch-2
Closed

rm Caret Movement per Google feedback on charter poll. editing-2025.html#535
tantek wants to merge 1 commit into
gh-pagesfrom
tantek-patch-2

Conversation

@tantek
Copy link
Copy Markdown
Contributor

@tantek tantek commented May 1, 2026

Proposal to remove Caret Movement per Google's feedback from @jyasskin on charter poll.

Also agreed the spec is too immature (still stuck in a gdoc) and lacks sufficient implementer interest to be considered for a standards track deliverable in a WG.

Proposal to remove Caret Movement per Google's feedback from @jyasskin on charter poll. 
* https://www.w3.org/wbs/33280/webediting-wg-charter-2026/

Also agreed the spec is too immature (still stuck in a gdoc) and  lacks sufficient implementer interest to be considered for a standards track deliverable in a WG.
@jyasskin
Copy link
Copy Markdown
Member

jyasskin commented May 1, 2026

I didn't mean to request that it be removed, just to request it be moved to a better location.

@johanneswilm
Copy link
Copy Markdown
Contributor

johanneswilm commented May 1, 2026

I don't understand the part about "not sufficient interest" from implementers. Google is the only implementer not regularly attending our meetings, but all the other ones (Microsoft, Apple, Mozilla) were part of this decision. The maintainer is from Microsoft. Given that Microsoft and Google are working on the same browser engine, I assume that Chromium is represented by Microsoft.

@johanneswilm
Copy link
Copy Markdown
Contributor

As for your question on the review @jyasskin : The document only just started and this is an explainer text that the Microsoft editor of the spec chose to create there as it was requested to have some text. SO it's not "stuck in a Google Document". I agree though that now that they will start to really work on it, it should move to a github repository.

@johanneswilm
Copy link
Copy Markdown
Contributor

Closing as this PR seems to have been a misunderstanding.

@siusin
Copy link
Copy Markdown
Contributor

siusin commented May 1, 2026

I suggest we move the discussion to issue #529 .

@siusin siusin reopened this May 1, 2026
@johanneswilm johanneswilm reopened this May 1, 2026
@tantek
Copy link
Copy Markdown
Contributor Author

tantek commented May 2, 2026

Closing per clarifications from @jyasskin and @johanneswilm. Further discussion to #529 as suggested by @siusin. Thanks.

@tantek tantek closed this May 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants