83
edits
Compatibility/Meetings/Sync w Mike: Difference between revisions
Jump to navigation
Jump to search
Compatibility/Meetings/Sync w Mike (view source)
Revision as of 13:22, 27 August 2020
, 27 August 2020Added meeting minutes from 26.08.2020
OanaArbuzov (talk | contribs) (Added meeting minutes from 29.07.2020) |
OanaArbuzov (talk | contribs) (Added meeting minutes from 26.08.2020) |
||
| Line 1: | Line 1: | ||
<big>'''August 26 2020'''</big> | |||
<big>'''OKR 2.2 Manual testing of 5 open source editor libraries (SV)'''</big> | |||
We'd like to start this OKR and do some testing on it. Could you provide more info on what should we focus our testing? Is there a list of issues that we should verify? | |||
https://github.com/mozilla/webcompat-team-okrs/issues/138 | |||
mike: the DOM team is focusing on contenteditable bugs this half https://docs.google.com/document/d/12kA5Ng11keqFdfMngEqLmEqggmXSoxa6vSKbBpuYlkw/edit | |||
mike: for example, https://github.com/microsoft/monaco-editor/issues?q=is%3Aissue+is%3Aopen+firefox -- if you search for firefox | |||
mike: do these issues still reproduce? | |||
mike: leave a comment only if it is no longer reproducible, skip bug that we don't understand, create a list with the issue that are still reproducible. | |||
mike: Test plan - what to test in an editor | |||
mike: some of these pages have a sample editor available, e.g., https://draftjs.org/ | |||
oana: https://www.w3schools.com/ has a similar test/run the code | |||
<big>'''[FYI] Needscontact verification (SV)'''</big> | |||
We finished verifying Needscontact issues: | |||
- Fixed: 179 | |||
- Invalid: 14 | |||
- Reproducible: 286 | |||
cipri: ~40% issues gone | |||
oana: a lot of the issues were related to the certificates and TLS | |||
<big>'''Moderation process enhancement (SV)'''</big> | |||
After setting the "accepted" milestone to an issue during the moderation process, the issue is automatically closed and removed from the private repo. | |||
We noticed that by setting the milestone to a batch of issues (25 issues per page) not all the issues are removed from the repo (usually 3 or 4 are still displayed) and a page refresh is needed in order to remove them. Is this the correct behavior? | |||
mike: ?????? this sounds like a Github bug. | |||
mike: related to this, https://github.com/webcompat/webcompat.com/pull/3452 | |||
mike: I added "accepted: invalid" and "accepted: incomplete" milestones | |||
mike: I'll let y'all know when it's actually ready | |||
<big>'''A11Y issue verification (SV)'''</big> | |||
We should schedule a testing session to verify all currently reported issues after fixes were merged. | |||
Let as know when to perform this task. | |||
mike: i should be done with a lot of these maybe in the next 2 weeks. | |||
oana: perhaps we'll wait until the end of the quarter to test them all in a batch. | |||
----------------------------------------------------------------------------------------------------------------------------------------------------------------- | |||
<big>'''July 29 2020'''</big> | <big>'''July 29 2020'''</big> | ||