On Fri, Dec 5, 2014 at 8:57 AM, Koji Ishii <kojiishi@gmail.com> wrote: > If you can't set the caret to a specific position by API, it's a bug > in browser. Please file bugs to browser vendors. I'd be curious to > know Blink bugs. I think it'd be great to share the bug number on this > ML unless someone thinks it's a noise. > The bug is here: https://code.google.com/p/chromium/issues/detail?id=2874 Note Julie Parent's plea for mercy way back in 2008. There has been some work on this recently but still no fix. There are many of examples like these in all browsers but most of them are ignored or given a "won't fix" because of a lack of clear direction from specs. > > What Johannes wanted is #1, but I don't think it's the right way to > go. Cursor movements is a quite complex task as Johannes pointed out, > and writing a spec to assure interoperability for that would be a > quite big task that'd take very long. Also, editors might want > different behavior depends on situation, so the spec is likely to be a > common denominator, which a good editor library would not want to use. > I think a strong spec is the right way to go. It's not just about getting all browsers to behave the same, it's also about ensuring browsers don't change their behaviors unexpectedly. With a weak spec they can do things one way one day then change to a different way on a future release. This can create unexpected problems with code that was written for the original behavior. Stability of the API is important and a strong spec helps with that. > >
Received on Friday, 5 December 2014 17:31:51 UTC