14
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Jump to navigation
Jump to search
Compatibility/Meetings/Sync w Honza (view source)
Revision as of 13:44, 12 December 2023
, 12 December 2023Meeting minutes December 12
(November 17 2023) |
(Meeting minutes December 12) |
||
| Line 1: | Line 1: | ||
== December 12 2023 == | |||
=== Top 100 Testing and Blockers (SV) === | |||
The number of discovered issues is lower compared to when we started (most are known issues - discovered in previous runs). Also, for Google and other sites where a valid mobile number is needed, we are blocked due to our test account mobile numbers being used for other test accounts. Some blockers have been observed for Financial sites where a valid banking account is needed, or where the mobile app is needed to perform various operations (Netflix, Google relarted apps, etc) | |||
=== Upcoming Holidays and Top 100 (SV) === | |||
Just a heads-up that this month we might not finish the whole Top 100 Test Suite for Q4 - Batch 1 due to upcoming holidays and PTO | |||
Honza: Sure, please add the PTOs into the Calendar. | |||
=== Work Week in Berlin (Honza) === | |||
Honza: I'll share the DevTools folder. This is a summary for planning in 2024. Our top level goal is to improve webcompat compatibility. | |||
*'''The first part is Webdriver BiDi''' | |||
WebDriver Bidi will involve more browsers, like Chrome and Safari, as it involves a protocol for crossbrowsing operability - for Automation - and Pupetteer. That would be the first use case, for Automation. | |||
Raul: Will that involve a programming language? | |||
Honza: Pupeteer is a library for JavaScript. It is in experimental phase. We will be collecting feedback. | |||
Raul: Could QA be involved into running automated tests? | |||
Honza: Sure, lets think about that for the next year. | |||
Honza: The main goal is to build the BiDi protocol and build an ecosystem on top of it which could be used for running automated tests and debug browsers. | |||
*'''The second Part of the Work Week is the Reactive Webcompat''' | |||
Most people use the reporting tool in Nightly now. Partially this is on purpose, due to the number of reports used. We want to see the big picture: the state of WebCompat. The idea is to get more reports. This will be achieved with the new reporting tool - shipping in Firefox 121 - the plan is to cover mobile as well, not just desktop. We also need to triage the incoming reports, and since the number is high (thousands) we are looking to automate some parts. That is addressed in Reactive webcompat composed from 3 parts: Reporting tool, Triage dashboard (likely just for QA) and Knowledge Base. | |||
Based on the data collected from Firefox not being supported, we will know what actions to take, to understand the webcompatibility around Firefox. | |||
Collecting engagement data will show some clarity as well. How much time users are spending on certain sites, top sites popular in Firefox, etc. This might show us if Firefox is gaining popularity or losing popularity. For example, some sites might not be popular in Firefox, but are popular in Chrome, and we need to see why. | |||
Private browsing mode will be more looked into it. | |||
We want to understand the state of Firefox from all of this. We can then recommed the Platform teams what to work on. | |||
*'''The third part is Dev Tools''' | |||
The same goal - we want to contribute here as well. Provide tools that enable developers to debug and optimize pages to work well in Firefox with focus on performance and reliability. | |||
We want to help them to diagnose webcompat problems if they happen. Quickly and efficient. We do not want to complicate the existing system. What ever we have, should be more quick and efficient, small features that will make a bigger impact. | |||
Many issues happen on the Production version of the site. Features will help them diagnose bugs in Production version using Firefox DevTools. | |||
Baseline- all features well supported across major browsers, they belong here. | |||
We are looking to run an Audit regarding this on pages. | |||
Raul: For remote debugging, we have some feedback. | |||
Honza: Great, lets talk about it in the next meeting. | |||
Honza: Also, the profiler will be more user friendly. | |||
All of this culminate into making Firefox more compatible, and thus better. | |||
== November 17 2023 == | == November 17 2023 == | ||
| Line 70: | Line 133: | ||
=== Gathering info for the New Reporting System (Honza) | === Gathering info for the New Reporting System (Honza) === | ||