From bug 335393: Someone can file yet another bug about changing "Backup" to "Back Up" This looks like just a nib change to CertificatesWindow.nib
http://dictionary.reference.com/search?q=backup i don't think we need to change this. To me "Back Up" means to go backwards, like reverse.
Keep scrolling on that page, Mike, and you'll see this: backup <operating system> ("back up" when used as a verb) Two words as a verb. None of the definitions above that are for verbs; they're all for nouns or adjectives. You can have "backup software" to make a "backup", but that software "backs up" your data. (Note you don't say it "backups" your data.) cl
you win ;) i concede.
Is this being worked on? I'm new to contributing and something this minor would be a good place to start. Can I run with this if it hasn't been assigned? - Chris
(In reply to comment #4) > Is this being worked on? I'm new to contributing and something this minor > would be a good place to start. Can I run with this if it hasn't been > assigned? Go right ahead, and welcome to the gang! cl
Thank you. It will take me some time to get my environment configured, etc, etc, so please be patient with me. :) - chris
13 years ago
Whiteboard: [good first bug]
Comment on attachment 227873 [details] [diff] [review] change "Backup" to "Back Up" in .nib file I'm glad you're interested in helping out, but we don't accept diffs for nib files. For more info, check out http://wiki.caminobrowser.org/Development:Reviewing (you want to zip the actual nib and attach it here) :)
Attachment #227873 - Flags: review?(bugzilla) → review-
Ok, I don't know about this before. Reupload.
Håkan, are we doing the right thing tab-chain wise in this nib (Security prefPane, Certificates button)? Seems to me this is just like the Bookmarks Manager, so the views should be getting a focus ring (which would lessen confusion as to why tabbing once--with a Category that has some right-pane content--doesn't focus the first item but requires a down-arrow--again, just like the BM).
This nib worked fine for me, focus-wise. The first listbox is focused (with a blue focus ring), and the listboxes (+ the action button with FKA on) are in the focus chain.
Comment on attachment 227881 [details] Reupload CertificatesWindow.nib Hi Isriya, This looks good, but it occurs to me that while we're touching this nib, we should make the window comply with our margins standards in http://wiki.caminobrowser.org/Development:Editing_Nibs Specifically, the action menu button should be 17 px below the view it's under, and the bottom of the window should be 20 px below that. Also, the initialFirstResponder should be set to the entire extended split view, and the extended split view and the action menu should each have a nextKeyView of eachother.
Attachment #227881 - Flags: review?(stridey) → review-
Actually, I didn't touch anything in the NIB, just change the string and recompile. mmm... I might accidentially hit it and move. Anyway, I'll resubmit this. Thanks for review.
Update NIB file to match Camino Development Guideline.
Comment on attachment 229613 [details] Reupload CertificatesWindow.nib again In this case I would leave initialFirstResponder unset (since that way it does the Right Thing in focusing Category first, instead of focusing the actions menu button). Also, the actions menu button should only be 17 px below the bottom of of the ExtendedOutlineView (Name, details, expires, etc). Looking better.
Attachment #229613 - Flags: review?(stridey) → review-
13 years ago
Assignee: nobody → stridey
Increases min width and does a 3px bounding-box adjustment, per IRC.
Comment on attachment 247247 [details] New CertificatesWindow.nib Nice; r=ardissone Requesting rs on these cosmetic nib-only changes (per policy).
Comment on attachment 247247 [details] New CertificatesWindow.nib (In reply to comment #12) > Specifically, the action menu button should be 17 px below the view it's under, > and the bottom of the window should be 20 px below that. No; this creates a lot of weird dead space at the bottom, and every example of similar controls I can think of looks the way it was before.
Attachment #247247 - Flags: superreview?(stuart.morgan) → superreview-
(In reply to comment #19) > (From update of attachment 247247 [details] ) > (In reply to comment #12) > > Specifically, the action menu button should be 17 px below the view it's under, > > and the bottom of the window should be 20 px below that. > > No; this creates a lot of weird dead space at the bottom, and every example of > similar controls I can think of looks the way it was before. I see nothing in the HIG that supports having a miniscule bottom margin instead of the standard Aqua margins; moreover, it looks out of place in comparison with our cookie sheets, where the button is well-placed.
(In reply to comment #20) > I see nothing in the HIG that supports having a miniscule bottom margin instead > of the standard Aqua margins; The 'G' is for Guidelines; I don't think we should slavishly following margin guidelines that are there solely for aesthetics even when it makes the overall visual appearance worse and more unbalanced. Note that we also use the current cert spacing in the Bookmark Manager. > moreover, it looks out of place in comparison with our cookie sheets, where the > button is well-placed. We also have an aqua button there, making the space much less empty. If the cert viewer were a sheet with a Done button, then I would agree.
What about putting the button back close to the table view, but leaving the 20 px between it and the edge of the window? Although the bookmark manager has dimensions that reflect our currect certificate window, the status bar buffers the edge of the window. I really think that the 20px around the edge is important.
Does comment 22
Sorry, *this* does comment 22
Attachment #247613 - Flags: review?(stuart.morgan) → superreview?(stuart.morgan)
Comment on attachment 247613 [details] Actually 20 px sr=smorgan
Attachment #247613 - Flags: superreview?(stuart.morgan) → superreview+
Checked in on 1.8branch and trunk.
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.