Lifting out a few future features of Firefox, and Pale Moon's approach to them:
- In-line autocomplete of URLs:
Pre-emptive loading of pages based on a "guessed" completion of the URL while it's being typed: Bad Idea.This is designed to anticipate what URL is being typed into the Address Bar, pre-loading the web page in the background before the URL has been entered.
Why?: Typoes causing unwanted content to be downloaded, background loading of unnecessary content (wasting bandwidth - people on metered connections will absolutely hate this! It's also wasting CPU -- this is not efficient), and how smart can a "guess" be if you've never visited a page before? (When do you type a URL? When you go to a page you have likely bookmarked? No, usually when you go somewhere you haven't gone to before.) - The new home tab:
Pale Moon is not and does not want to be affiliated with any predefined "Apps Market" and pushing this commercial portal upon its users. Instead, the current Pale Moon Start page serves well as a balanced starting location with search capabilities and quick links, and will be maintained.Mozilla plans to use it as a portal to the upcoming Apps Market, for example. - The New Tab page with "quick dial" thumbnails:
This is wrought with potential performance problems and inefficient use:- Thumbnail creation of pages is expensive in terms of CPU usage (see: Panorama/Tab Groups), for one.
- A blank "new tab" page does not distract you from what you were intending to do with the new tab by presenting you with suggestions to other things (psychology 101)
- A blank "new tab" page allows easy drag/drop of links/URLs
- The bookmarks toolbar (enabled by default in Pale Moon) already has a "most visited" entry giving you a much faster way to select frequently used pages at a fraction of the "expense"
- Quick dial and/or new tab add-ons are already available for people preferring this (and additional) new tab functionality with more configurability
NOTE: The "quick dial" new tab page is included in Pale Moon because it has been a semi-frequent request by users to have something "Opera-like" in the browser (and Pale Moon tends to listen to its users in terms of what is desired), but it is disabled by default to not impact performance of the browser. It takes some manual changing of parameters to enable it at the moment (expect this to be made more user-friendly in the future). - Metro Firefox and Desktop Apps:
Desktop integration has never been one of Pale Moon's goals. Pale Moon is a browser application, and does not need desktop integration, hooking into metro, or providing "chrome-less full screen apps" that can easily be achieved already by going full-screen from the browser (without losing your UI entirely), and currently no less than 26 major issues listed to be resolved before it can even be implemented.Support for desktop apps, which can be installed and used independently of Firefox, even when offline. - Panel-based download manager:
This is potentially desirable but depends heavily on how exactly this hooks into the current browser code. If it is intertwined with undesired GUI changes, then the current approach will be maintained (download manager window + download status indicator in the status bar) - Completely silent background updates:
Bad idea for a number of reasons, and against Pale Moon's approach of freedom of choice: freedom of choice which browser you want to run, when you want to update and to what you want to update.
The web browser - your gateway to the internet in many cases and an essential part of most people's daily life on the PC - is a key application. Silent updates may break functionality, cause issues, etc. And you won't know if there has been an update (especially not if Mozilla goes ahead and removes the version number from a clearly visible place) causing your sudden inability to use some/all sites, or that something else is going on (malware, network problems, etc.) - Integrated PDF reader:
You are at all times better off opening foreign formats in the designated external applications (Adobe's plug-in has always been poor, I recommend to simply download and open in the standalone reader). What's next, integrate support for Openoffice Formats? Spreadsheets?
Also, the viewer built into the core will be basic, at best. No annotations, probably no field support, etc. etc.
The viewer (Adobe Reader) is already widely available and commonly installed on a lot of systems (and with plenty of free alternatives if you don't want Adobe's sizable package). It's also easy to implement cross-platform with Ghostscript. I don't see the need for the integration of a PDF reader into the core of the browser.
Moreover, incremental downloading of PDF documents has been problematic from day 1 - slow downloads, stalls, browser hangups, to name a few
Lastly: Implementing a viewing application like this in the browser core, you need to have an as fool-proof and secure implementation as possible. Since this will be part of an application that will be fully trusted on your system, and if in the core of the browser without any potential safeguards or sandboxing, any exploit of the PDF reading subsystem will be a potential high-risk problem: arbitrary code run in a trusted application with full access to the internet and possibly also an administrative-level "maintenance service" (from the silent updates) that is running is a security nightmare scenario.