- #Bugzilla Skins update
- #Bugzilla Skins skin
- #Bugzilla Skins Patch
- #Bugzilla Skins code
- #Bugzilla Skins free
> either need to make that decision yourself or delegate it to someone else. > Unfortunately that's not possible, since there's no UI module owner.
#Bugzilla Skins skin
> I'll abstain from making a call on whether the new skin is worthy of Skins are an area where people traditionally enjoy a little bit of choice however. There are many places where I agree with your assessment. > tyranny of choice can make people miserable.ĭepends on the context. More choice is often bad if meaningless or unnecessary, and the
#Bugzilla Skins update
If Byron agrees with these changes, could you update alternate_skin/ on landfill? Unless I miss something, the class name in buglist.css was wrong. I add rules for printing which were missing in the new skin. I use a lovely (?) brown color for the login name to increase the contrast with links. In the footer, labels and links now have the same size, and are 1pt smaller than the rest of the page to give the focus to the main page. Comment header now fits on a single line as already reported by myk and myself. At least 2 persons reported the contrast being fainter than in the "Classic" skin, and I agree about that. Links in the main body are darker and bluer for the same reason (better contrast). Links in the header and footer are white for better contrast. The selection class comes back, but is darker. I personally don't like links being underlined in the footer. Splinter Review Looking at the new skin again, may I suggest these changes? The reasons for these changes are: You have 3-4 days left to get it into 3.1.1, else it will be postponed till 3.1.2. The second point about data outside the light-grey area may be fixed in a separate bug if it requires too much work.
#Bugzilla Skins Patch
I would like at least the first point being addressed, about comment headers, before approving this patch for checkin. By the way, is this set of CSS still up-to-date with current 3.1 UI?
#Bugzilla Skins code
And this patch will probably forces us to remove the remaining hardcoded CSS styles within HTML templates.īe aware that taking it in the main code will force us to keep 2 skins up-to-date. A good example is See also Įverything else looks great. Also, comment 0 has its header right-aligned which looks broken compared to other, left-aligned, comment headers.Īnother thing I noticed is that if your screen is quite small, or you have a wide "Details" section at the top (while being logged in), the CC list and flags may be partially out of the light-grey area, which is not very nice. I also noticed that, and I don't want it either. > a separate line so that every comment header takes two lines instead of one. > consider usability regressions, like putting "reply" and "private" controls on
#Bugzilla Skins free
Feel free to muck around w/ global.css and attach if White was actually hard to read also, so black seemed the lesser of evils. Has its link color set to black explicitly. On the view bug page? If so, there's actually a ".nestedBox. Re: color - Are you referring to the light brown buttons in the label:after if you want the colons back at Several times), but there are only 3 "lowercase"'s in there so it's not to bad Just change it one place (and so I didn't need to redefine that button look I really wish you could do dependencies/variables in CSS so you could Re: the lowercase, I guess that's the beauty of CSS that you can just change I'll fix that if/when I submit a followup patch. I tend to not notice because my tabs match bugzilla's The form tag really needs to move inside that tmpl file, but I just did a quick This after I submitted the original patch and fixed it in our local version). Termination 10.That last patch actually has a fix for that form button in it too (I noticed Command-line 'Send Unsent Bug-mail' tool C. reports "Client does not support authentication protocol index.cgi doesn't show up unless specified in the URL A.9. Some users are constantly being forced to relogin A.8. Everybody is constantly being forced to relogin A.7. I installed a Perl module, butĬ claims it's not installed! A.4. The Apache web server is not serving Bugzilla pages A.3.
Integrating Bugzilla with Third-Party Tools A. Checking and Maintaining Database Integrity 4. Multiple Bugzilla databases with a single installation 2.5.
0 kommentar(er)
