@ladyleet @denladeside Hope you recover soon! Thanks for sharing and calling us all to action.
@othermaciej @bradeeoh @mb2100 …so why not ask folks to add use cases to _existing_ bugs to begin with, and aggressively closing dupes as part of the process?
I was _always_ happy about the _initial_ quick reaction on my bugs (added CC:s, created Radars
@bradeeoh @mb2100 We’ve also heard this: https://t.co/pxkiUPshkS.
@bradeeoh @mb2100 “Voting†by filing a duplicate bug sounds weird from an outside point of view since it seemingly makes managing the entirety of all bugs harder, but is what we have heard from Maciej as well. https://t.co/dyVcIkuPQT
@simevidas @argyleink It’s essentially CSS Remedy: https://t.co/fnFyThtGtQ.
@paulmwatson Browser vendors simply never implemented “no-preferenceâ€.
@cshjb007 @jho_crypto It’s not yet officially published, but the article available at the staging link https://t.co/CJYmEKO1fE should answer the questions.
@mb2100 @bradeeoh For the record, this is the most recent situation where I personally encountered this: https://t.co/nOnKuFCB0g.
@EivindArvesen @othermaciej We have added more details on the `X-Client-Data` header in the privacy white paper: https://t.co/4j0LTLm2ZF.
@bradeeoh This was eye-opening for me, too. I’ve since eagerly filed feature request bugs for the things we would love the team to consider implementing: https://t.co/Nz1imOTVYC.
@bradeeoh “Scare away†as in conveying that it’s not worth to file bugs since apparently there’s no motion on one’s bug, when actually there is, just on a non-deduplicated bug from someone else.