It just occured to me that I've only been nitpicking and uttering wishes so far, and forgot to ever write a note of appreciation: Thanks, Bundyo, for working on this great app. Thanks to Tear I spend a lot more time with my N810 now, and get a lot more use out of it. While things worked before with MicroB, loading up complex pages took so long, and the browser was so unresponsive while it was loading (scrolling during load was nigh-impossible) that I actually tended to avoid a lot of browsing on the device, which runs counter to its intended purpose. Tear is what was missing from the equation there. And I also really like various elements of its UI approach, particularly the one-click bookmarking. So, again, thanks for adding a lot of value to my N810!
If Mer adopts Tear as its default browser, that'd probably be the biggest single upgrade it can include to kick Diablo's ***^W finely-shaped behind.
( Searching this thread for "zoom" gave no hint, so here goes.)
Running Tear 0.3-6 on an N810 :
Often zoom-in increases also page width, making horizontal scrolling necessary.
This trick mostly makes zoom increase only text size.
(tested only with ITT pages)
Zoom back to 100 % (or less if necessary) to make page width fit screen.
Reload page. Scroll page. Then zoom in.
This almost always works with ITT pages that are lists of threads,
but less often with pages in a thread.
I tested this both with open keyboard in full-screen mode using the +/- and menu keys,
and with closed keyboard in small-screen mode using the menu.
( I write this in microB after crashing Tear 4 times;
back-spacing the cursor in the quick reply window with the D-pad
when the cursor is at the beginning of a line
seems always to freeze Tear.
I suppose this is known and mention it just in case.)
I don't think I've asked this yet: is there a way to customize key bindings in tear to change d-pad scrolling to page-by-page, as opposed to line-by-line? (These are the instructions to do this for microb.)
Bundyo, I left several Feature Requests in the Garage: Select All; adding a text-select toggle button like in Quick Clip Viewer; and Find Text on Page.
I looked at the Bug Tracker on the Summary page and it showed zero bugs. Am I going to the right place to place Bug Reports and Feature Requests?
(Again, I can't say thanks enough for Tear. What a pleasure it is!)
