trackbot, prepare teleconference
<agendabot> clear agenda
<scribe> scribenick: addison
<atsushi> (possible regrets for next week, just memo..)
https://www.w3.org/International/track/actions/open
action-812?
<trackbot> action-812 -- Richard Ishida to Investigate situation for accesskey including wording and tests and report back -- due 2019-07-25 -- OPEN
<trackbot> https://www.w3.org/International/track/actions/812
<xfq> https://www.w3.org/2019/09/TPAC/travel.html
action?
https://github.com/w3c/i18n-activity/projects/1
<scribe> ACTION: richard: publish tips for linking to headings and figures for wide review
<trackbot> Created ACTION-815 - Publish tips for linking to headings and figures for wide review [on Richard Ishida - due 2019-08-01].
richard: working on article on
making LTR text appear/display RTL
... such as chinese or (ancient) egyptian
... still a few little things to do
<r12a> https://github.com/w3c/i18n-activity/issues/719
richard: could us a bit of
help
... about case sensitivity
... the whatwg says "... must be case sensitive..."
... wrote exploratory test
richard: very simple but
effective test. type a value and then hit with various modifier
keys
... possible to find keys that are case *IN*sensitive in
English
... haven't done windows
... greek, different results in FF and safari
... safari case sensitive
... ff doesn't recognize uppercase
... examples in doc violate it... most shortcut keys you see
are "uppercase" but you don't press shift to get
addison: corner cases if insensitive (turkish)
david: would accents be stripped?
richard: how would uppercase e-acute work in french?
addison: what to do? file or bring in more accesskey issues?
richard: what to recommend?
addison: insensitive with health warning?
richard: waiting on addison to do
tests
... will submit after we have results
<r12a> https://github.com/w3c/i18n-activity/issues/720
richard: one code point
issue
... how many code points can you have? our question was: why
restriction?
... restrict value to single keypress instead?
... some keyboards have keys that produce multiple code points.
Burmese, Devanagari
... safari, chrome quite happily accept those keys as
accesskeys
addison: they're trying to convey
the concept rather than a tech requirement
... submit?
richard: okay
... summarize at end
<r12a> https://github.com/w3c/i18n-activity/issues/521
<xfq> New abstract: https://github.com/w3c/csswg-drafts/issues/3829#issuecomment-513590636
<scribe> New abstract reads: CSS Writing Modes Level 3 defines CSS support for various writing modes and their combinations, including left-to-right and right-to-left text ordering as well as horizontal and vertical orientations.
<atsushi> +1 to close
RESOLUTION: close 521
<r12a> https://github.com/w3c/i18n-activity/issues/157
richard: raise as a question?
<scribe> ACTION: richard: raise issue 157 with whatwg as a question
<trackbot> Created ACTION-816 - Raise issue 157 with whatwg as a question [on Richard Ishida - due 2019-08-01].
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/more whatwg issues/more accesskey issues/ Present: Bert David Fuqiao Katy Richard addison atsushi r12a xfq Found ScribeNick: addison Inferring Scribes: addison Agenda: https://lists.w3.org/Archives/Member/member-i18n-core/2019Jul/0008.html Found Date: 25 Jul 2019 People with action items: for linking publish richard tips WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]