canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
User:Standard8/Content Use Cases: Difference between revisions
Jump to navigation
Jump to search
→Requirements: Form fields not an issue
(→Requirements: Form fields not an issue) |
|||
| Line 53: | Line 53: | ||
## No back/forward/url bar by default. | ## No back/forward/url bar by default. | ||
## contentTabType to allow hooks for commands - e.g. so extensions can implement back/forward | ## contentTabType to allow hooks for commands - e.g. so extensions can implement back/forward | ||
# Form Fields should render correctly (Mac only). | # <strike>Form Fields should render correctly (Mac only)</strike> (nglayout.debug.enable_xbl_forms was set to true). | ||
# Easy to extend or exchange xul for tab contents (so that extensions can easily add features, e.g. navigation buttons. | # Easy to extend or exchange xul for tab contents (so that extensions can easily add features, e.g. navigation buttons. | ||
# Favicon support | # Favicon support | ||