Difference between revisions of "Development:Planning:Internal URIs"
(add history and autocomplete) |
|||
| Line 19: | Line 19: | ||
===Set as home page=== | ===Set as home page=== | ||
| − | about:blank and about:bookmarks are the only two about: URIs that make sense as a home page. Should we do something about this? | + | *about:blank and about:bookmarks are the only two about: URIs that make sense as a home page. Should we do something about this? |
| + | *Personally, I think we should let users have whatever homepage they want. If about:plugins (or whatever) gets them off, more power to them. [[User:Froodian|Froodian]] | ||
===Bookmarking=== | ===Bookmarking=== | ||
Revision as of 15:11, 20 June 2006
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.
Set as home page
- about:blank and about:bookmarks are the only two about: URIs that make sense as a home page. Should we do something about this?
- Personally, I think we should let users have whatever homepage they want. If about:plugins (or whatever) gets them off, more power to them. Froodian
Bookmarking
I understand the perceived need to bookmark about:bookmarks, but we should probably disable the Add Page to Bookmarks menu item for all other about: URIs. On a related note, we should disabled Add Bookmark Folder when History is active.
History
about: URIs should not be added to history.
Autocomplete
There seems to be no reason to have about: URIs in the autocomplete database either.
view-source:
View Source
View Source should be disabled when viewing source of a page. Bug 159337
Save As
Save As should be enabled when viewing the source of a page. Since this is currently the case, no action is needed on our part, except to avoid regressions as we're fixing other stuff.
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.
Bookmarking
Do we want to allow people to bookmark view-source: pages? I don't see much reason why we shouldn't, but I don't see much point in it either.
History
view-source: URIs should not be added to history.
Autocomplete
There seems to be no reason to have view-source: URIs in the autocomplete database either.
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 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? They definitely shouldn't be autocompleted.
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 Bug 302601.
