- Karl Dubost, Mozilla
- Mike Taylor, Google
Mike: we published a blog post @ Force Chrome major version to 100 in the User-Agent string Mike: also giving a lightning talk at BlinkOn on Nov 17th Mike: also wanting to start a Chrome Canary experiment to send v100 UA string to some % Karl: I need to write a blog post on otsukare about v100 Karl: the Firefox experiment will be done in 2 weeks from now, currently active. 50% of Nightly users send 100 UA string. Karl: So far https://github.com/webcompat/web-bugs/labels/version100 - not that many bugs. A couple of them reproduce in both Firefox and Chrome. A few of them are UA sniffing bugs, maybe if we can identify patterns of libraries it would be easier to fix. Mike: I have a goal to write a “worst case scenario” Plan B document, in case we need to do something. Mike to share next time we meet. Karl: How are people reporting issues in Chrome? Mike: We have this thing - not sure where data goes? Mike to try to find out. Mike: maybe this system info thing sends a UA string? Karl: Should we ask people in the Edge team what is their intent? And if they have experimentation plans for v100 (Blink). No concerns for Safari. (Safari 15.4). Mike: we need a few more weeks for Firefox experiment to end, for the Chrome one to ramp up (and to try to find where issues might be). Karl: it would be interesting to try another experiment for DevEdition, once this one ends.
No progress yet. Mike: still wants to document UA patterns today. Needs to find time.
There’s a conflict for Chris at this time. Karl: same time + or - 1 day would work for me. Mike: either works. Maybe we ask Chris what he prefers. Karl: I moved to Wednesday Pacific/Thursday JST