Skip to content

2024‐09‐13

Bruce Bailey edited this page Sep 13, 2024 · 4 revisions

Minutes for meeting September 13th, 2024

Attendance (8): Bruce Bailey, Giacomo Petri, Gundala Nieuman, Francis Storr, Ken Franqueiro, Lori Oakley, Patrick Lauke, Scott O'Hara

Regrets: Alastair Campbell, Mike Gower. Regrets from Patrick for next week.

Announcements

Agenda

Reflow

Scott walked group through where he is with Updated Reflow understanding doc #4055 and answered many questions from TF and was provided praise and feedback.

  • A preview is available but TF is reminded that the PR status is Draft. Scott will be ready for comments when that is no longer the case.
  • Most (but not all) content from Google Doc has been pulled in. Some linearization of content has been adjusted.
  • Scott has placeholders and inline notes-to-self. The heading structure and other formatting is a work in progress. All agreed that graphical examples of not meeting requirement are important, but it's more important that they not be easily confused with illustrations of passing examples.
  • Outstanding question as to where large files should go? Intent is to replace animation with an MP4, but gif is 4 MB so file size probably won't be much worse. MP4 would allow pause, but Scott can use a collapsed warning disclosure accordion as a stop gap.
  • TF would be also be okay with publishing without animation initially. The MVP need not be perfect.
  • There was discussion about adding live code to demonstrate overflow. A video also has the advantage of showing exactly what is being illustrated. The presentation of overflow scrollbars (in a table) would be different on mobile, and would likely distract from the point being made by the video. This a feature which could be added later, but probably not as a replacement for the animated example.
  • Some concern for the length was raised. Francis noted that it's shorter than Understanding 2.4.11 and we all agreed that frequently used resource.

Review ‘For discussion’ items

Update definition for single pointer #3536 had conversation on list. We discussed on call and agreed that there was not an intent to change the scope. TF members also agreed we are okay with phrasing as-as. That said, there was interest in addressing the concern raised by Patrick offered to take another close look and maybe propose a change to one or two words. Any potential editorial will be available for the AG call Tuesday, 9/17.

Editorial suggestions for consistent links to definitions and capitalization #3038 discussed. This PR is already highlighted for the AG review call 9/17 on Tuesday. Each instance of text linking to the defined term would benefit from another review, which Bruce volunteered for. TF members have already reviewed and remain satisfied with (and grateful for) the editorial changes.

Review ‘Drafted’ items

Input Purposes for User Interface Components is an appendix, so should be marked as non-normative #3777 continuing discussion from last week. The associated PR, Mark input purposes list as non-normative #3778, is not how this change could be implemented, so that PR was closed. Kevin will have to investigate best editorial course. Issue left in Drafted column, which is certainly not correct, but seems better than the other choices!

Add F111 to 1.3.1 and 4.1.2 #4063 is straightforward, since 1.3.1 and 4.1.2 are already in the title of F111. Moved to Ready for review (by AG).

Tweak the concept of "draw" in 2.5.8 understanding for the spacing checks #4057 which closes 2.5.8 Understanding "draw" language #3895. Concern for language translation and maybe someone taking "draw" very concretely. Moved to Ready for review.

Tech timeout 20 hours or greater #4058 is a new technique pulled from a old branch. No one on call felt it was needed, but there reluctance to discard the work. Bruce pinged Glenda Sims, who created the branch. Left in Drafted.

Other discussion

Time permitting, items of interest to participants, including open discussions.

Discussed stale branches (per email noted at top of call), and considered idea of deleting anything older than some number of years? There could well be old issues that are quite valid. Any date selected would be arbitrary. Preference on call is to keep working through the backlog.

TPAC is in a couple weeks, please check the schedule and your availability. Initial expectation is that TF will have call as usual.