Chat Summary: 23th April 2020…

Chat Summary: 23th April 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1587675646270300

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

No CSS audit updates this week.

Color Scheming status update

I proposed having this as a recurring agenda item since it is a long term and far reaching initiative – meeting attendees were in agreement that it should be.

@kburgoine created the ticketticket Created for both bug reports and feature development on the bug tracker. “Replace wp-admin color schemes with CSS custom properties” #49930 and mentioned there hasn’t been much traction. We discussed possible next steps for the ticket. @ryelle mentioned a need to break down the need for color schemes, and @kburgoine mentioned researching and outline some potential approaches, perhaps with proof of concept Codepens and some prototypes.

@ryelle indicated that the root issue might be that we need a different approach to color schemes and that custom properties might be part of the solution, but not the whole thing. There are currently has 206 unique colors in wp-adminadmin (and super admin), and the current implementation of color schemes requires any overriding of default colors to be just as specific. To summarize this message, standardizing colors and switching them all to custom properties would remove the need for color scheme authors to write new CSS to override the default colors. So, specificity resulting from the current color scheme handling is an issue. @isabel_brison suggested that a ticket to track the current issues with color schemes would be useful.

@netsassprodsr asked about IE support, and @isabel_brison mentioned that we would need some sort of flagging / indication to users what color schemes are IE friendly.

I outlined a couple of next steps for the color scheme ticket based on the conversation:
1. research/list some problems that are caused due to the current color scheme implementation
2. research/list some approaches for colors schemes in the ticket

@ryelle offered to take on #1 and to create a ticket for it if one doesn’t already exist.

Open Floor

@isabel_brison has created a label in the Gutenberg repo for CSS issues – very cool! This will hopefully be helpful for folks who want to contribute to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ with their CSS skills.

That was all for this week! @isabel_brison will be filling in for me and facilitating the next CSS chat on 30 April.

#summary, #core-css

CSS Chat Agenda: 23nd April…

CSSCSS Cascading Style Sheets. Chat Agenda: 23nd April 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, April 23, 2020, 5:00 PM EDT.

This meeting will be held in the #core-css channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • CSS audit status update
  • Color Scheming status update
  • Open floor

#agenda, #core-css

Chat Summary: 16th April 2020…

Chat Summary: 16th April 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1587071014211100

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

@isabel_brison gave an update on the screehshot testing work in (49606)[https://core.trac.wordpress.org/ticket/49606] and mentioned it proving troublesome to pass the Travis build, and that would be a secondary concern. The most useful part of the tests will be when we are actually making changes to the code and checking for breakage vs. running them on every changeset. I clarified that the workflow would be something like first, generate/update the reference screenshot to contain any changes, and second, run the tests as you develop to check for unintentional changes.

@ryelle shared a custom script for running various audits: https://github.com/ryelle/css-audit – this is a big step for ticket (49638)[https://core.trac.wordpress.org/ticket/49638] and determining the audit methodology. @ryelle‘s scripts are organized by categories like colors, selectors, and important, and each audit outputs a set of data points. The current script outputs audit results in a .txt file, and I mentioned that could certainly be updated to JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. or another format that can be displayed on WP.org or elsewhere. Very cool!

I also pointed out a few tickets mentioned by @isabel_brison on the last chat summary regarding IE 11 hacks. When looking into audit data points for IE hacks or “outdated layout practices”, these would be good to reference: https://core.trac.wordpress.org/ticket/46015, https://core.trac.wordpress.org/ticket/49696 (but if the patch for 46015 makes it through, we have no need for an audit data point!)

Open Floor

I noted a message from @kburgoine regarding experience with IE11 support and color schemes – it’s not necessarily a straightforward task! @isabel_brison mentioned that there may be existing color scheme tickets and that the global styles work in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ includes custom properties. @sabernhardt mentioned the admin color schemes repo from @ryelle and a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. started for Dark Mode. I suggested a boldly titled ticketticket Created for both bug reports and feature development on the bug tracker. “Replace wp-adminadmin (and super admin) color schemes with CSS custom properties” so that we can track the conversation, and responses were positive!

That was all for this week!

#summary #core-css

CSS Chat Agenda: 9nd April…

CSSCSS Cascading Style Sheets. Chat Agenda: 16th April 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, April 16, 2020, 5:00 PM EDT.

This meeting will be held in the #core-css channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • CSS audit status update
  • Open floor

#agenda, #core-css

# CSS Chat Summary: 9th…

Chat Summary: 9th April 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1586466056120100

I (@notlaura) facilitated the meeting. A bit delayed in posting the summary – will do better next week!

CSSCSS Cascading Style Sheets. audit updates

We reviewed the process for the audit and discussed the high-level ticketticket Created for both bug reports and feature development on the bug tracker. “Create a report outline for Audit” #49637. What should a report outline look like? Currently it exists in this Google Doc as a place to collect data and gradually organize it.

@joyously asked if the report would be an ongoing process or pinned to a specific releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. which brought up an idea and conversation around how to express the audit data. @michael-arestad suggested a publicly hosted page that runs and updates on each release. This could be immensely helpful for tracking improvements to the codebase! That hinted at another high level ticket, “Determine methodology recommendations for audit” #4963 – which may be a mixture of automated processes and manual work depending on the data we need.

How would we pull off recurring, release-based audit results? I proposed that the first steps are getting the data the first time and keeping track of how we did it, while determining how we want to present the data e.g. by edit screen or by categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., other, or all of the above.

@joyously suggested incorporated the automated audit results alongside the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 reference in the developer subdomain and .org.

To close up the audit update, I identified the following as some items that would be good starting points for contributors willing to do some manual code inspecting:

  • < IE 11 Hacks – maybe start by finding an example of a few and seeing if they are in mutliple locations
  • State of comments – what are the comment styles that are used
  • Location of outdated or brute-force layout practices (e.g. floats, positioning and pixel nudging)

Open Floor

@joyously posed the age-old question: “When does our browser support for IE11 go away?” @michael-arestad answered with “When fewer users use the browser. Tell your friends.” Wise words! We reviewed the browser support best practices and that when IE 11 is < 1% usage, we can abandon support. Current usage information can be seen here.

The conversation then turned to custom properties and replacing the adminadmin (and super admin) color schemes with custom properties which seems like a great candidate for introducting them to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. No ticket for that … yet! @michael-arestad mentioned the benefits of keeping in sync with the NPM components used in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. After the meeting, we discussed the intricacies of using the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. components in wp-admin, and if you’re interested, check out the meeting transcript here!

That was all for this week!

#summary #core-css

CSS Chat Agenda: 9nd April…

CSSCSS Cascading Style Sheets. Chat Agenda: 9nd April 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, April 9, 2020, 5:00 PM EDT.

This meeting will be held in the #core-css channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • CSS audit status update
  • Open floor

#agenda, #core-css

CSS Chat Summary: 2nd April 2020

Full meeting transcript on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.: https://wordpress.slack.com/archives/CQ7V4966Q/p1585861240051700

I (@isabel_brison) facilitated the meeting. 

CSSCSS Cascading Style Sheets. audit updates

  • @notlaura tested Parker, a stylesheet analysis tool, with results documented here.
  • @joyously suggested CSS Stats as another potential tool.
  • The a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team had a look at the audit tickets at their weekly meeting and had a few recommendations.
  • Based on a11y team feedback, we agreed to add notes to the audit on any CSS properties we find that are unhelpful for accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility).

Open Floor

@joyously requested we add a channel topic to #core-css, with the time of our weekly meeting, which we did.

@joyously asked if the audit would include editor CSS, or only wp-adminadmin (and super admin) pages. The current audit includes only wp-admin pages, but there was agreement on auditing both the editor and the default themes CSS at a later stage.

That was all for this week!

Next week @notlaura will be taking over the running of this meeting, due to daylight savings changes.

#summary

CSS Chat Agenda: 2nd April 2020

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for 2nd April, 21:00 UTC.

This meeting will be held in the #core-css channel  in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If there’s any topic you’d like to discuss, please leave a comment below!

Agenda

  • CSS audit status update
  • Open floor

#agenda, #core-css

CSS Chat Summary: 26th March 2020

Full meeting transcript on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.: https://wordpress.slack.com/archives/CQ7V4966Q/p1585256425000800

I (@isabel_brison) facilitated the meeting. 

CSSCSS Cascading Style Sheets. audit updates

  • I looked into our possibilities for visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. testing and found that jest-image-snapshot integrates very well with our existing e2e testing tools. I’m preparing a prototype branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". that I will share on the ticketticket Created for both bug reports and feature development on the bug tracker. soon.

Open Floor

@sabernhardt requested feedback on a patch for adding print styles to wp-admin. Discussion ensued, and we agreed that:

  • Currently, when printing out wp-adminadmin (and super admin), the only thing that doesn’t show is the admin bar. This is not optimal, and print styles should remove all interface features not relevant to page content.
  • The print styles should apply to all wp-admin pages that have content and/or lists.
  • Work on the initial ticket should attempt to hide all common interface elements for print
  • If much further work is needed on individual pages, we should create sub-tickets for easier tracking/review.

And that was all for this week!

#core-css, #summary

CSS Chat Agenda: 26th March 2020

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for 26th March, 21:00 UTC.

This meeting will be held in the #core-css channel  in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

If there’s any topic you’d like to discuss, please leave a comment below!

Agenda

  • CSS audit status update
  • Open floor

#agenda, #core-css