Website:Issues

Please report all issues with the current Camino website below:

Sam's todo list

• Update blogs.cb.o with the new section menu. Promotion below News, and Downloads removed for now.
• n.cb.o - Doc pages migration
• Bug 292780 - Create /download/releases Page Listing Releases
• Bug 292777 - Release notes page needs a download link
• Bug 293093 - Main Page needs list of support languages
• The sidebar look/style needs an update. (Design by Jasper, CSS by Sam/Wevah)
• Register ce.o domain - Pending DNS
• Bug 300111 - Enhance the Camino Bugzilla FAQ page
• Remove incorrect line from 09a1 release notes: "Command + Up & Down now works the same as Page Up & Down."

Jasper's todo list

• Create l10n header graphic
• I should create some extra different sized badges.
• Create special version 1.0 badges
• Rewrite the promotion page with more specific paragraphs and more content
• Direct cb.o/pr and cb.o/press to the promotion page
• Finish the 1.0 final release note
• Add more accessabolity to the support and development pages
• Add quick menu to hiddenprefs page
• Add the download links for latest release and multi lang on the features page.
• Design the future langauge selector
• Write new text for the features section.
  • The animation text need a look and tweaks.
  • Use the sidebar for a feature list.
• Create new graphics for the features section.
  • Work myself trough the list of features. Keep it simple and clean.
• n.cb.o - Access keys for navigation (use u for underline)
• Create l10n graphic for development pages (similar to download icon on main page)

Wevah's todo list

• n.cb.o - Migrate Development pages
• Bug 300179 - Fix Search Customization Instructions

Graeme's todo list

• Create /start/ page with it's own style and browser-detection PHP.
• Migrate content from current site to new site.
• Link in Jaspers l10n header graphic.
• l10n plugin.
  • Seems to be some issues with the access privileges to the plugin.
  • Ability to add languages through preferences tab.
  • Content updates should mark localized text as requiring updates.
  • Ability to make minor edits which don't require updates to the localized text.
  • Specifying the language code in meta tag.
  • Image localization -
    Any ideas anyone?
  • Localization of other miscellaneous strings - i.e. Browser Warning
• Highlight for the active Development & Support sidebar links.
• Update plugins for the newer version of txp.
• Design CSS version of support/docs pages.

Smokey's issues and typos found

• cb.o needs an "Editorial" style guide (how words are spelled, capitalized, US vs. European comma placement, how elements of the GUI are named, etc.)

  Refer to Apple's style guide, http://developer.apple.com/documentation/UserExperience/Conceptual/APStyleGuide/AppleStyleGuide2006.pdf

  • drop-down
  • preference pane
  • search field
  • location bar
  • web page (not webpage)
  • dialog (not dialogue)
  • separate windows/dialogs in Initial Caps--kinda
    • Downloads window
    • Preferences
    • Bookmarks Manager (though not a separate window, it's a distinct custom view)
  • appnames in <strong> in instructions (not random mentions)
  • filenames in <code> blocks, e.g. <code>user.js</code>
  • Use raw Unicode characters (⌘ … “ ” ’ —) rather than entities
  • keyboard shortcuts:
    • ⌘ first, capital letter last, shift before option, no space or dash.
    • use kbd tag with title attribute (spell out command, initial caps), e.g.

      <kbd title="Command-Option-E">⌘⌥E</kbd>

  • Referring to menus, menu items, buttons, preference labels; see http://www.mindspring.com/~alqahira/moz/cbo-ui.html
  • Navigating menus and prefpanes (step-by-step order)?

• Typos and other errors found:
  • Support FAQ mis-identifies JEP in the Java FAQ (should be "Java Embedding Plugin")
  • Support FAQ is missing a "~" in the path in the "Where are my bookmarks" FAQ (should be "~/Library/Application Support/Camino")
  • Support FAQ still references "servers at Netscape" in the Talkback FAQ (middle of 3rd paragraph). Has Asa updated his original description from which this was taken?
  • Support FAQ has a typo in "Chimera" section; should be "project's"
  • Support FAQ, "About the name" section should capitalize "Spanish"
  • Support - Hidden Prefs page:
    • the user-agent override pref has to be removed from both user.js and prefs.js because it's a pref that "doesn't exist" by default, rather than a pref that overrides a default setting in an extant pref.
    • [0.9-only] Disable image loading will have to be rewritten; the analogue to the old pref is user_pref("permissions.default.images", 2); but the new pref has more flexible options and has "cousins" for javascript, frames, etc.; docs on the new options and syntax are here.
    • [0.9-only] Broken Bookmarks Checking - didn't this get ripped out on the trunk?
    • [0.9-only] Disable target="_blank" uses only user_pref("browser.link.open_newwindow", 1); in 0.9.
  • Sidebar in Development section:
    • "Report a Camino bug" should point to https://bugzilla.mozilla.org/enter_bug.cgi?format=guided&product=Camino (helper form) by default; experienced users who give good reports can figure out how to use the short form, and this gets us more useful info from everyone else.
    • "Report a Mozilla bug" points to an invalid product; should use https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Application%20Suite&format=guided (or https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&format=guided if it's intended for Core bugs) or be removed altogether.

typoes found while translatin (including suspected typoes)

• Promotion "Together they are reaching more users and potential users then we could ever reach with our limited resources." should be "than"?