As people will not read anything no matter how red or bold it is,
hide the bug submission form by default. We don't want people to
submit their mundane bugs as security issues just because that's
the only option.
Instead point people to the php/doc-en repository.
It's still possible to change the bug type to "Documentation
Problem" after it has been submitted, e.g. if it turns out a bug
is really a documentation issue.
* usability: make label clickable for radio input
* set a right padding for the label
so it is obvious the label is for the left side radio select.
* clickable labels for asc/desc radio select
* right padding also for the asc/desc labels
* make the "NOT" checkbox labels clickable
With the new flexibility of resizing the package category select the appearing of the 2 selects side by side on https://bugs.php.net/report.php might look a bit odd.
This PR fixes it by align the 2 selects always to the top.
Reuses the existing CSS classes to apply the same backgorund colors as in the bug search result table rows.
I know that Chrome and Safari ignore applying a background-color to option tags of a single select. But when bugs.php.net supports also multiselect for the status select both will show the background-color in multi selects (multiple="multiple" attribute for xhtml compatible modus)
Just wanted report a bug on bugs.php.net, but letting the user scroll 460 entries (optgroups+options) in a 6 line height tiny multiselect in the bug search is torture.
Closes GH-84.
* recent bugs stat tables better float
using display:inline-block; or flex layouts provide better method than using historic the float:left approach.
* css for recent bugs stat tables
Using display:inline-block; is better than using float:left;
Fatal error: Uncaught TypeError: Argument 1 passed to App\Template\Context::e() must be of the type string, null given, called in /srv/www/htdocs/web-bugs/templates/pages/admin/database_status.php on line 64 and defined in /srv/www/htdocs/web-bugs/src/Template/Context.php:159
Derick Rethans