Meeting minutes
Review agenda and next meeting date
<Matt_King> view agenda at https://
<Matt_King> Next meeting is on June 6.
Status of Site Updates
Mockups for same level navigation in Single Pattern and Single Practice pages
github: w3c/
Matt_King: We discussed this during the last meeting
Matt_King: We're waiting on feedback from Shawn. I'll bump this with them
Pull request reviews
Fix path to ratings star images
github: w3c/
Matt_King: I think this won't work because it assumes the content repository is the same as the build repository
howard-e: As far as I know, this will result in a different path resolution if rendered for the live site
Matt_King: I believe there's an issue related to this in the other repository
howard-e: perhaps w3c/
howard-e: I'll follow up on the issue to help the contributor understand why we're going to close this
Remove duplicate SkipTo library
github: w3c/
Matt_King: I think this PR needs some discussion, but we can't have it without Alex_Flenniken
Matt_King: I don't really want to manage any content in WAI ARIA-Practices
Matt_King: The one thing I'm not sure about: it feels inconsistent that we would include other scripts in the "head" within the content repository, but not this one
Matt_King: I'll add a comment. We might have to have Alex_Flenniken in a meeting at some point
updated skipto.js script to 5.1.6
github: w3c/
Matt_King: Is there another way to do this without requiring all the HTML source to be edited? Specifically, a way that would be straightforward to anyone using skipTo
jugglinmike: the RequireJS library was configurable via the HTML script tag which included it. We could configure skipTo with a "data-" attribute, if skipTo were updated to recognize such an attribute
Matt_King: I think we want to merge gh-2680 and then get alignment on whether or not the HTML files in ARIA-Practices with have a script tag for skipto.js or not (and if not, where the injection will be done). From there, we can simplifying this aspect of configuration
Add landmark pattern page
github: w3c/
Matt_King: Alex_Flenniken has unblocked this, and we're waiting for reviews
Matt_King: None of the people assigned are in this call today. I can reach out to them via e-mail
<jongund> https://
siri: I will take a look
Datepicker Modal Dialog: Fixed next/prev month bug and improve adherence with APG code style guide
github: w3c/
jugglinmike: I reviewed and approved the tests with Paul at Bocoup.
Matt_King: Then I think this is ready to merge
Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified
github: w3c/
Matt_King: The most recent comment is Carmen offering to triage
Matt_King: This is waiting on test review and code review by Alex_Flenniken
New Issue Action Planning
shape of mouse pointer for links and mouse buttons
Matt_King: This was reported to the mailing list; there is no issue on GitHub for it.
Matt_King: I'll find the message in the archive and convert it to a GitHub issue
Improving the presentation of example code
jugglinmike: This just came up during an internal call at Bocoup, so I haven't had time to file an issue. Given that we have a little time today, I thought I'd ask those in attendance directly
jugglinmike: We've been consider if and how contributors would be discouraged by the way sample code is displayed on the site right now
jugglinmike: We identified a bunch of opportunities for improvements, but we also wondered whether it would be acceptable to address this by integrating a third-party "code embedding" service like CodePen
jugglinmike: That would require less work than improving the current implementation, and it would also result in less code to maintain, overall. On the other hand, we could imagine use cases that would be incompatible with any third-party solution
Matt_King: This has come up a few times before. We decided not to rely on CodePen, et. al, due to usability limitations of embedded iframes
Matt_King: That said, we do include a button to review the examples in CodePen
jugglinmike: Thanks! That lets us take that option off the table
jugglinmike: We recognize that this is relatively low priority, so we'll be looking to balance between impact and development effort
jugglinmike: Though I'll say that it seems like it'd be better to generate the markup for formatted source code on the server (currently, that's done in the browser)
Matt_King: In the longer-term, I'm interested in making APG easier for W3 staff to maintain as content that more simply slots into the rest of the W3's properties.
Matt_King: For this issue specifically, I'm wondering if they have established practices for rendering source code on other sites, and if we could somehow use that