Development:Planning:Internal URIs

We need to evaluate/audit/decide/whatever how special-case URIs (e.g., about:, view-source:, etc.) should be handled by various features (i.e., View Source, Save As, etc.).

about:

View Source

View Source should be disabled for all about: URIs.

Save As

Save As should be disabled for all about: URIs.

Email Page Location

Email Page Location should be disabled for all about: URIs.

Fill Form

Fill Form should be disabled for all about: URIs.

Get Info

Get Info should probably be disabled for all about: URIs.

view-source:

View Source

View Source should be disabled when viewing source of a page.

Save As

Save As should be enabled when viewing the source of a page.

Email Page Location

Email Page Location should be disabled when viewing the source of a page.

Fill Form

Fill Form should be disabled when viewing the source of a page.

Get Info

Get Info should probably be disabled when viewing the source of a page.

Set as home page

It seems a little silly to allow a view-source: page to be set as the home page.

External (non-Camino-handled) protocols

They can currently be bookmarked. If this is OK, then we should probably not be adding them to the top 10 (see also Template:bug 302601) or history, and we may not want to keep a visit count for them. Are there other situations we should worry about with external protocols?

Other situations

• Should we be allowing users to bookmark view-source: or about: URIs?
  • If so, should we increment visit counts for them?
  • If so, should they be on the top 10 list? See also Template:bug 302601.