User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 My vision is getting worse. The first item that attracted me to Mozilla was its ability to override the webpage designer, and do significant Text Zoom. Often the first thing I do on most webpages is Text Zoom. Suggestions: a) Preference for a Default for Text Zoom size. Eg, 120 or 150 or 200% (if its someplace buried, please tell me the name, and change this to a request to move that option from prefs.js to the UI) b) When opening a link in a New Tab or New Window, Keep the previous Text Zoom size. Do not reset to 100%. It is tedious to have to keep resetting text zoom size. c) Add an optional Magnifying Glass in a rectangle around the current cursor Overall, thank you very much for your efforts! Reproducible: Always Steps to Reproduce: 1.set Text Zoom size 2.Open any link to a New Tab 3.have to set Text Zoom size again
|
||
Comment 1•14 years ago
|
||
It's not going to be made to persist until we implement full zoom. *** This bug has been marked as a duplicate of 4821 ***
see also bug 108391
wontfix (for the reasons described in bug 65571) See also bug 4821 and bug 108391. FYI: Opera has implemented the feature you request.
|
|
||
Comment 4•13 years ago
|
||
No, opera has implemented bug 4821. It is much safer for full zoom to be persistent than for text zoom to be persistent, as described in bug 65571.
"Safer"? Bug 4821 is over 5 years old. I doubt it would take much more than 5 *hours* to implement an "inherit text zoom level across tabs and windows" feature for one who knows the code. An ad-hoc solution which would be Extremely Practical. Aestethics aside: It's the User who decides whether or not to utilize the feature. If it's so important to overrule my text-zoom setting, why isn't it also reset when opening links in same window? Wouldn't that be even "safer"?
|
||
Updated•13 years ago
|
||
|
|
||
Comment 6•13 years ago
|
||
This bug is not a dupe of bug 108391 or bug 4821. This might be able to be handled, though, in tandem with bug 108391, but its definately a different issue. Bug 108391 wants to remember text sizes on a per-site basis. In Firefox, if I go to excite, decrease text size, then go to google in the same tab, then google will also have a decreased text size. This bug wants text size to be remembered between tabs in part b. Right now, the behavior when opening a page in a new tab is inconsistant with opening it in the same tab because the font size is NOT remembered when opening a new tab, while it IS remembered when opening it in a new tab. Therefore, there is an inconsistancy that should be addressed, and is as I see part b as a bug as opposed to an RFE. This could get fixed exlusively of bug 108391, but the behavior presented when opening a new tab or window wrt text size should be consistant with when opening a new page in the same tab or window by clicking a link. An example is if you are at a site, and "open link in new tab" or new window, why would you want the text zoom to change? Yet in the same breath, you'd sometimes want to be able to have different text zooms between tabs and windows. Therefore, I believe the reporter is saying when the tab first opens or a window first opens, it should inherit the text zoom of the window that you clicked "Open link in new tab" or "Open link in new window". If you just did File > New Tab or File > New window, it should use the default text zoom, which would be 100% or a preference, as mentioned in part a, which though related should be a seperate RFE (one issue per bug). I confirm that this is a problem, and I agree with the solution the reporter presented and I mentioned above (If I heard it right). The other two are RFEs that should probably be moved to seperate bugs. a: I looked in about:config, and I didn't see any preference, except for default font sizes, which can be set in preferences for Mozilla Seamonkey, but doesn't seem available in Firefox except through about:config. There are a lot of fonts to set, and I agree a default text zoom would be nice because it would handle all cases, therefore override for all types of fonts. Although this would be nice to do in parallel with inheriting the text zoom of new tabs opened through a link from the page where the link was, this would be a preference, while the other is a per-session thing which would most likely override the preference. If we also fixed 108391, we'd have the pref for default text zoom, and a per-session remember text zoom for opening a link in a new page or window (and same tab and window which it does now), and also a per-domain (or whatever is agreed upon in bug 108391) text zoom which would be a constraint on inheritance. c: The magnifying glass is already available within the source as a resource on all operating systems (for image zoom), so it would be available for this too. Are you asking for a zoom feature for accessibility? Those really should be handled by the operating system. Or are you asking for something different? Seperate RFE please.
|
|
||
Comment 7•13 years ago
|
||
To correct myself, font settings are available in Firefox within: Tools > Options > General > Fonts & Colors. Kim: I assume that text zoom changing every time you go to a new site would also not be something you'd relaly like either (bug 108391), which makes me think that resetting it to 100% when openining a link to a new site would be a bad idea. I'll mention that there.
|
|
||
Comment 8•13 years ago
|
||
*** Bug 242290 has been marked as a duplicate of this bug. ***
|
|
||
Comment 9•13 years ago
|
||
marking duplicate of wontfix bug 65571, but see bug 4821 and bug 108391. *** This bug has been marked as a duplicate of 65571 ***
|
|
||
Comment 10•13 years ago
|
||
rkaa: The problem with persistent text zoom is that text zoom breaks sites, and if it's persistent across sites the user will forget that the page is zoomed and consider the broken sites to be bugs. This has been discussed ad nauseam on bug 65571 and I'm not interested in discussing it again unless you have something new to say.
|
|
||
Comment 11•13 years ago
|
||
And whatever you do, please don't clutter up valid bugs with feature requests for other things. One issue per bug. (This bug started off with three, so it's basically invalid from the start.)
|
(Reporter) | |
Comment 12•13 years ago
|
||
In reply to.... > Additional Comment #6 From Brian 'netdragon' Bober 2004-05-02 01:28 > This bug wants text size to be remembered between tabs in part b. Right now, > the behavior when opening a page in a new tab is inconsistant with opening > it in the same tab because the font size is NOT remembered when opening a > new tab, while it IS remembered when opening it in a new tab. Therefore, > there is an inconsistancy that should be addressed, and is as I see part b > as a bug as opposed to an RFE. Yes. Thank you for this clear statement. When following a link, the current text zoom is used in the same tab, but not when starting a new tab / new window. This means my first action on a new tab is to set the text zoom size. Again and again. > Therefore, I believe the reporter is saying when the tab first opens or > a window first opens, it should inherit the text zoom of the window that > you clicked "Open link in new tab" or "Open link in new window". Yes! > If you just did File > New Tab or File > New window, it should use the > default text zoom, which would be 100% or a preference, as mentioned > in part a, Yes. Exactly. > ... which though related should be a seperate RFE (one issue per bug). To me, parts a and b are related issues to be discussed together. However, will follow what you recommend. Do I re-enter them? Does a moderator split the listing? > I confirm that this is a problem, and I agree with the solution the > reporter presented and I mentioned above (If I heard it right). Thank you. > c: The magnifying glass is already available within the source as a > resource on all operating systems (for image zoom), so it would be > available for this too. > Are you asking for a zoom feature for accessibility? yes > Those really should be handled by the operating system. Or are you > asking for something different? If the operating system does the magnification, will it suffer from the jaggies? e.g., the o/s sees only pixel bits. Whereas the browser has the source html, and can arbitrarily magnify text (and some types of graphics) as needed, in a smooth and readable fashion.
|
|
(Reporter) | |
Comment 13•13 years ago
|
||
In reply to.... > ------- Additional Comment #10 From David Baron (ignoring most email through June 2) 2004-05-02 10:42 > rkaa: The problem with persistent text zoom is that text zoom breaks sites, First and foremost, I have to be able to READ the text. If the text is not readable, nothing else matters. Period. Without text zoom, some sites are broken (to me) because they are not readable. Try an experiment: set the text zoom size down to say 25% and visit a few sites. Tell me if you care how pretty the site looks :-) or if columns line up. Persistent text zoom makes browsing much easier, avoids the tedious resetting of text zoom sizes. > ... and if it's persistent across sites the user will forget that the page > is zoomed and consider the broken sites to be bugs. a) There are other parameters, in the operating system and the browser, which if changed will "break" sites. How is this any different? The user is responsible for whatever they change. Attempts to reproduce the problem will lead to discovering the text zoom size change. b) if desired, when text zoom is set to something other than 100%, display the magnification text size somewhere as a reminder. ----------------------- > And whatever you do, please don't clutter up valid bugs with feature > requests for other things. Will try to do better, but please note that unless a particular behavior is described in the documentation, as a mere user not familiar with the internals of the code, it is sometimes hard to distinguish between bugs, features and enhancement requests. ----------------------- Thank you one and all for your efforts and hard work. It is much appreciated!
|
||
Comment 14•12 years ago
|
||
*** Bug 315308 has been marked as a duplicate of this bug. ***
Description
•