Re: [w3c/editing] Valid text element declaration for rich text editing caret accessibility (Issue #481)

jabcreations left a comment (w3c/editing#481)

Greetings @johanneswilm. So I initially do my testing with ESR releases of Gecko through Waterfox as I don't have to time to test a new "browser release" every time a fly bats it's wings.

Using Waterfox 128 ESR (6.5) go to the bottom of this following page and type some text. Then press Enter and watch carefully when you type the first character. What my Rich Editor is doing is placing an interpunct as a placeholder nodeValue and the paragraph's color is set to transparent. Only after intended text is typed is the color: transparent; removed. However it doesn't always work smoothly.

[https://www.jabcreations.com/blog/version-3-5-0](https://www.jabcreations.com/blog/version-3-5-0)

I don't have any resources to spare right now though my intention is to ultimately brute-force fixing browser bugs by just paying people to fix specific bugs. The Gecko rendering engine has had the most issues, it's just very combative. Some bugs have been fixed since the days of Firefox 4 though I was banned from Bugzilla because there are a lot of delusional developers who consider broken "done" or "good enough". I prefer to acknowledge reality and when I disagree with it correct it.

I haven't paid much more attention to my Rich Editor for maybe two or three years beyond the occasional fixing of bugs from my platform's JavaScript error reporting though I consider rich editing a fundamental requirement for people to be able to accomplish their goals without having to go through a lifetime of development just to build something for others to use like you or I.

Again, I don't have the resources to spare for a while however I follow rendering engines closely (except for Blink) and perhaps we could advance things through the Interop project. You can read about it on [this Safari blog post](https://webkit.org/blog/16458/announcing-interop-2025/). The deadline for 2026 is sometime in November or early December however admissions don't "open" until a few weeks just before they close. That would be the current best-case scenario to get further attention to rich editing on the web in my opinion.

Blink has the resources of Google so I don't believe it'll be difficult to get involvement rolling for Blink. WebKit is subjective; I've had passionate people respond to bug reports for WebKit in the past so again I'd advocate for finding people at Apple passionate about the possibilities of editing. If you have an iPhone and do any moderate level of texting then you'll know there are some people somewhere to reach out to; I don't know who they are myself though.

Gecko I think will be the most difficult. The fascists took over and the last I read a woman who has a breast-pump business is now the CEO. I'm all for breast-feeding, even for babies however the fascists are simply using Mozilla to line their pockets from the revenue from Google to have their search engine be the default. So that makes Gecko very resource-constrained. Until I (or maybe someone else) can fund a developer to just go in and fix bugs I don't know if any advocating will work (from my perspective). Unfortunately Gecko (in my opinion) is the current major rendering engine that needs the most work.

I don't often communicate with folks from standards bodies like yourself though I do have some history. I'm more on the front-lines of development and building my web platform business. Once resources start to free up I'd love to put my money where my mouth (so-to-speak) though these are mostly my thoughts and perspective on where things are right now. I imagine things will be considerably better in a year or two. I hope this reply helps in some form?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/481#issuecomment-2683043552
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/481/2683043552@github.com>