8 replies

1. Zach Leatherman 3 min later

   the primary purpose of breaking changes is to remind developers that they shouldn’t get too comfortable

   1. amos 4 min later

      @zachleat "I have altered the deal" etc. etc.

   2. Private reply 7 min later
      1. Private reply 2 hr later
2. westbrook 13 min later

   @zachleat This is so timely as I am currently looking at this #playwright API change 🤦‍♂️...

   Deprecated 💔 https://playwright.dev/docs/api/class-accessibility#accessibility-snapshot

   New 🤷‍♂️ https://playwright.dev/docs/aria-snapshots

   And, the move to YAML in the output, in JS!?! 😡

   1. Nathan Knowler 15 min later

      @westbrook @zachleat Yet Another… syntax/api change

   2. Mario 4 hr later

      @westbrook @zachleat I personally like the new approach. It makes it super readable even for less technical people in a team, e.g. designers who do accessibility QA.

      1. westbrook 5 hr later

         @mariohamann @zachleat Simple patterns, almost:

         - heading "Heading text" [level=1]

         VS

         {
         role: 'heading',
         name: "Heading text"
         level: 1
         }

         More complex patterns, dropping data?

         - combobox "Combobox" [expanded]
         - listbox "Combobox":
         - children[]

         VS

         {
         role: 'combobox',
         name: 'Combobox',
         expanded: true,
         focused: true,
         haspopup: 'listbox'
         },
         {
         role: 'listbox',
         name: 'Combobox',
         orientation: 'vertical',
         children: []
         }

         Better that the new API is not deprecated, however.