Date: Sat, 15 Jun 2019 04:08:51 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 238482] www/firefox: 67.0_3,1 print pre-formatting is HORRIBLE Message-ID: <bug-238482-21738-NnuZbGH96g@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238482-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-238482-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238482 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 257 | |44 --- Comment #13 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Ronald F. Guilmette from comment #9) Hi Ronald, I add the comment below both as a committer who seeks to improve the user experience as a high priority value, who looks at many many issues and interactions in Bugzilla, and as a member of the FreeBSD Bugmeister team to= who manages issue tracking process in the project. First, I'd like to respectfully request that you please dial down the rheto= ric when using our issue tracker (or any other public project space) in future. I/we understand (very well) that issues can be very frustrating (we report issues in other projects too), particularly if issues do not appear to be treated as importantly or in as timely a manner, as you may feel they are, = or should. Nevertheless, it is prudent in all circumstances to: a) Assume good faith b) Assume in advance there are things we as reporters don't understand or k= now in terms of the context or nuances of issues. Asking (unloaded/good) questi= ons that seek to understand instead of letting our frustrations leak is much mo= re productive. c) Attempt to remain concise, objective and unemotional in the way we communicate. In particular, this means talking about the problem 'out there' from 'the same side' in a collaborative manner, and not contextualising iss= ues in terms of me vs you,users vs maintainers or other potentially adversarial appearing ways. d) For opensource projects, understand that resolving issues is based on the currency of collaboration and positive/constructive influence. Users that understand this tend to receive much more fruitful responses to their reports/concerns, and can save themselves a lot of unnecessary frustration. We all seek to be understood, but in general, it pays to seek first to understand. On the issue of this issue, I'd like to add a few points, and one proposal: 1) On the subject of "Works As Intended", and the "It is in no sense fixed" comment. The only positive (forward moving) resolution type is "FIXED", which means, resolved by way of a specific action taken (in most cases, a commit). All others are "non fix" resolutions, which varying differences. Resolution selection done right is usually is a process of exclusion, not positive selection, and in some cases, there can be overlap, or a not quite right fi= t. Going through our resolution types, none fit more 'closely' than Works As Intended and it is/was the correct choice. This was made also made explicit with the added comment "Bitmap fonts simply don't support anti-aliasing and generally only look good at very low resolutions". Said another way "it looks bad because rendering using bitmap fonts look ba= d" At that point in the issue, there was no specific proposal for a change, wh= ich brings me to=20 2) I propose to change this issue to sounds something like "Make default rendering font not be a bitmap one" Finally, something that must be acknowledged is that font selection is a ve= ry subjective and widely scoped issue that has ramifications for software and = use cases far beyond browser printing. It is in most cases that any default is = not going to satisfy large groups, or many groups for different use cases, and = the more important issue is that font selection ability for users is a) possibl= e b) obvious to users c) easy to do --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238482-21738-NnuZbGH96g>