![]() Opening a new tab makes both buttons dim and nonfunctional (until close-reopen of a tab with history). In addition they won't change aspect between tabs: *bright* (dim)įrom then on, both buttons work in all tabs, but they will never look greyed-out even when they do nothing because we're at that end of the current tab's browsing history. Some sites are form-driven (like my bank's), and I HATE it when Mozilla insists on resubmitting the form when you hit the back button. ![]() If your theme does not show scrollbar buttons and you would like to see them. I'd like Mozilla's 'back' button to work truly like a bloody BACK button and take me to the previous page, REGARDLESS of whether it's a POST or a GET or whatever. Note: In Gecko 2.0 (Firefox 4 / Thunderbird 3.3 / SeaMonkey 2.1) through. The Mozilla backend code SeaMonkey is based on, now usually incorporates. If the tab is closed and reopened in the middle of back-forward history, both buttons will wake up active and will continue working, but at the (begin or) end of history they won't become dimmed (though of course you still can't go back from the start or forward from the end). This will act exactly like the user clicked on the Back button in their browser. "Close Tab" immediately followed by "Undo Close Tab" makes the buttons active or greyed-out as required, but if one of them (let's say "Forward") is greyed-out (because we are at that end of the browsing history) using the other one (Back) won't "ungreyout" it (Forward) and won't make it do anything when clicked. This change will align the Firefox behavior on Windows and macOS with how it works in Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |