83
edits
Compatibility/Meetings/Sync w Karl: Difference between revisions
Compatibility/Meetings/Sync w Karl (view source)
Revision as of 08:39, 21 April 2022
, 21 April 2022Added meeting minutes from 19.04.2022
OanaArbuzov (talk | contribs) (Minor updates from 05.04.2022) |
OanaArbuzov (talk | contribs) (Added meeting minutes from 19.04.2022) |
||
| Line 1: | Line 1: | ||
== April 19 2022 == | |||
=== OKR task proposal Q2 (SV) === | |||
We were thinking of adding a task to perform Exploratory testing for the top 10-20 Leading Online Marketplaces Worldwide sites | |||
* https://www.practicalecommerce.com/ecommerce-marketplaces-worldwide | |||
* https://heraldbee.com/the-biggest-marketplaces-for-e-commerce-by-country-or-region/ | |||
What is your input on this? | |||
karl: sure, that is a good idea | |||
karl: we can also check the domains and see if we have reports on them on webcompat | |||
oana: created OKR task https://github.com/mozilla/webcompat-team-okrs/issues/257 | |||
=== Product Team Task (SV) === | |||
Are there any news regarding this? | |||
karl: not yet | |||
=== Checking issues that are specific for v100, but not reproducible on versions below 100 (SV) === | |||
Since the Release version of Firefox will receive the 3 digit UA string, should we check if issues are specific for Firefox 100, but not reproducible on versions below 100 (since we will not have a build for Firefox 99 anymore after that date), by running a `mozregression` with v99 to compare the results and see if the issue is specific for v100 (not reproducible on v99 from the mozregression build)? | |||
karl: you can download an older Firefox build | |||
raul: maybe we can also change UserAgent to an older version (maybe from about:config) | |||
karl: you can change the UserAgent also from Responsive design mode. | |||
karl: you can create a profile with an older Firefox version (Mac: cd ~/Library/Application\ Support/Firefox/) | |||
=== Issues that have non-SSL (not secured) websites (SV) === | |||
As seen in: https://github.com/webcompat/web-bugs/issues/102351#issuecomment-1097275632, can we automatically close issues that have non-SSL pages (on all browsers) as `wontfix`? | |||
karl: too many domains are added there, plus porn sites - a bit spammy, they have lots of ads and finding a contact for them is hard | |||
karl: for normal sites continue moving to Needscontact and add the SSL Lab result. | |||
karl: if Chrome displays the site, Firefox doesn't display the site, both display connections not secured in "Site information" option of the toolbar - move to Needsdiagnosis and assign it to me | |||
=== Bugzilla issues that are submitted in the wrong Product, but are clearly webcompat issues (SV) === | |||
As seen in: https://bugzilla.mozilla.org/show_bug.cgi?id=1764428, the issue seems like a perfect candidate for webcompat. But because it is not in the right Product/Component in Bugzilla, can we move them if they meet the requirements to be a webcompat issue, regardless if they are previously moved/created by other team-mates from Bugzilla or the bot? | |||
karl: don't move it, you can leave a comment, add the webcompat issues (if available) to "See also", maybe ping one of us | |||
=== Checking sites that stream or offer illegal downloads (SV) === | |||
Is there a way to double-check (like a list of Google removing sites) for sites that streaming illegally? | |||
karl: no point in diagnosing them and no way/hard way to find contact | |||
== April 5 2022 == | == April 5 2022 == | ||