On 3/19/21 11:05 AM, Philip Race wrote:
If this was important to him I don't understand why just a blog post and
not a bug report ..
If I had to guess, it might be because, in the age of GitHub, this is
not what people expect when they try to report a bug:
Report a Bug or Request a Feature
https://bugreport.java.com/bugreport/
There are two main problems:
1. You can't attach images.
2. You don't get credit.
I speak from experience. I spent five years frustrated with a JavaFX
font bug, but it was only when I could properly format a report and
include images that I bothered to open this issue:
Reduce color fringes in FreeType subpixel rendering
https://github.com/javafxports/openjdk-jfx/issues/229
Formatting and images shouldn't matter, but two other people tried to
report that bug using the Oracle Web form, and both were closed as "Not
an Issue." You can send images later by e-mail, eventually, but that's
not explained anywhere.
There was a brief window when the OpenJFX project accepted bug reports
on GitHub, but now it's back to the Oracle Web form. That brief window
is the reason I'm a contributor to the project now. I understand the
need for gate-keeping. We just shouldn't be too surprised when people
decide that the gate's too high.
I think Oracle could fix the two problems and keep the Web form, and we
might get more quality bug reports instead of frustrated blog posts. I
also think that it would help a lot to enable the JIRA markup[1] in the
Java Bug System as Apache NetBeans has done. As an example, I can't
imagine trying to report a bug like the following without formatting or
in-line images:
Attaching JavaFX Javadoc and Sources
https://issues.apache.org/jira/browse/NETBEANS-3296
John
[1]
https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all
