For FPR32 I will be updating the internal Reader View to the current version of Readability.js, adding a preference pane UI similar to site-specific user agents, and maybe also adding the current Firefox feature allowing you to adjust the gutter margins wider or narrower. It also cuts out a lot of crap, meaning it's back to only the columnists annoying me in the L.A.
If you decide you do want to see the article as intended, just click the Reader View icon in the address bar as usual, and the article will render in "full" form links to subpages you click on from there will go back to Reader View.Īs I've said many times, I think Reader View is an important way of making sites render faster and more usefully, especially on G3 and low-end G4 systems.
Click the back button and you're back on the front page. It renders in the normal browser view, but if you click on any article, it immediately shifts to Reader View. Its article pages have a lot of irritating popup divs, so go into about:config, create a new string preference called set it to the single letter s (for subpages for all pages, use y for, um, "yes"). Since front pages may not work as well, you can specify to do this just for "subpages" or for all pages.Īn example is the Los Angeles Times, which is more or less my semi-local newspaper here in Southern California. Auto Reader View, however, allows you to tell the browser to automatically open pages from a domain in Reader View as soon as you click on any link to that domain from any page, in Reader View or not. Sticky Reader View means that when you go into Reader View, links you click on also load in Reader View, until you quit it by clicking one of the exit buttons. However, I do have a not-yet-exposed feature's plumbing done, which is another enhancement to Reader View: auto Reader View.Īuto Reader View is different from sticky Reader View, which has been the default since FPR27.
#TENFOURFOX INTEL UPDATE#
I was also planning to do a Reader View update for this release, which will need a user interface of its own, but every new UI feature requires additional locale strings and I wanted to give our localizers (led by Chris) a chance to catch up on the new strings in time for the final release on March 22. If you have a user-agent add-on already installed, you can still use it, but it may have interactions if you try to use this feature at the same time and you're on your own if you do. For sites that are unspecified, obviously the global user agent option still applies. Our implementation has no penalty if you have no site-specific user agents loaded and this remains the default. As before, having site-specific user agent strings does slightly slow the browser down, though most of the penalty is paid on the first and not so much on additional strings you enter. Instead of having to enter sites and strings manually into about:config, though you still can, you can now go to the TenFourFox preference pane, This was quietly reimplemented in FPR17 for interested users, but now that it's getting more and more necessary on more and more sites, I have made the feature a visible and supported part of the browser interface. Olga T Park contributed a backport from later Firefox versions to fix saving passwords in private browsing, and I also finished fully exposing support for site specific user agents. However, there's still new stuff in this release. I didn't get everything done here that I wanted to, though thanks to Chris T I do have a reproducing local test version of the infamous issue 621 at least I am able now to see that it's clearly a problem in the JavaScript parser generating something incorrectly, but I'm still not able to tell where the specific deficiency lies. TenFourFox Feature Parity Release 31 beta 1 is now available ( downloads, hashes, release notes).
0 kommentar(er)
