- From: cynthia <notifications@github.com>
- Date: Tue, 11 May 2021 16:32:32 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/591/839282597@github.com>
@wacky6, thank you for your patience! @atanassov and I looked at this during our F2F. Your response covers most of the questions we had - thanks a lot. > WDYT to have a hint about writing direction? In case some recognizers need this information. Note, some recognizer may disregard this hint altogether. I think having that as an extension point would be useful - if there is some sort specific of post-processing that needs to be done based on this before it hits the recognizer, it feels like this information could be useful to expose. > For LTR languages, but characters written from right to left (e.g. "hello" written in "olleh" order). It's a rare/uncommon scenario. We agree that this isn't an important scenario to handle. Our concerns on RTL was mostly about languages that are actually written left to right. > I don't think we should try to solve the mixed script problem if the underlying implementations haven't solved it. If it's an unsolved problem, I think we don't need to delve too much into this. > We don't have particular preferences on where the methods are. Are you suggesting we put the methods behind a attribute (e.g. navigator.handwritingService.doSomething())? Yes, this was one of the reasons we asked this question. We were also a bit curious on three different tabs initiating multiple recognition contexts - is anything shared? (This question is based on the navigator layering) (More comments based on the discussion with @atanassov to come in a bit.) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/591#issuecomment-839282597
Received on Tuesday, 11 May 2021 23:32:44 UTC