33
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Compatibility/Meetings/Sync w Honza (view source)
Revision as of 16:19, 12 December 2023
, 12 December 2023→Work Week in Berlin (Honza): 2
(Meeting minutes December 12) |
|||
| Line 13: | Line 13: | ||
=== Work Week in Berlin (Honza) === | === Work Week in Berlin (Honza) === | ||
Honza: I'll share the DevTools folder. This is a summary | Honza: I'll share the DevTools folder. This is a summary of planning in 2024. Our top-level goal is to improve webcompat compatibility. | ||
*'''The first part is Webdriver BiDi''' | *'''The first part is Webdriver BiDi''' | ||
| Line 21: | Line 21: | ||
Raul: Will that involve a programming language? | Raul: Will that involve a programming language? | ||
Honza: Pupeteer is a library for JavaScript. It is in experimental phase. We will be collecting feedback. | Honza: Pupeteer is a library for JavaScript. It is in the experimental phase. We will be collecting feedback. | ||
Raul: Could QA be involved | Raul: Could QA be involved in running and creating automated tests? | ||
Honza: Sure, | Honza: Sure, let's 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. | 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. | ||
| Line 31: | Line 31: | ||
*'''The second Part of the Work Week is the Reactive Webcompat''' | *'''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 | 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 of 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. | 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 | 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 | Private browsing mode will be looked into it. | ||
We want to understand the state of Firefox from all of this. We can then | We want to understand the state of Firefox from all of this. We can then recommend to the Platform teams what to work on. | ||
*'''The third part is Dev Tools''' | *'''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. | 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 a focus on performance and reliability. | ||
We want to help them to diagnose webcompat problems if they happen. Quickly and | We want to help them to diagnose webcompat problems if they happen. Quickly and efficiently. We do not want to complicate the existing system. Whatever we have, should be more quick and efficient, with 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. | Many issues happen on the Production version of the site. Features will help them diagnose bugs in the Production version using Firefox DevTools. | ||
Baseline- all features well supported across major browsers, they belong here. | Baseline- all features are well supported across major browsers, they belong here. | ||
We are looking to run an Audit regarding this on pages. | We are looking to run an Audit regarding this on pages. | ||
| Line 55: | Line 55: | ||
Raul: For remote debugging, we have some feedback. | Raul: For remote debugging, we have some feedback. | ||
Honza: Great, | Honza: Great, let's talk about it in the next meeting. | ||
Honza: Also, the profiler will be more user friendly | Honza: Also, the profiler will be more user-friendly. | ||
All of this culminates in making Firefox more compatible, and thus better. | |||
== November 17 2023 == | == November 17 2023 == | ||