IE Browser zoom level problem (Avoid missing Left/Top portion)

When the user set the zoom level in Internet explorer to 125 or 150, there are some missing portions (left and top) of my flash object.
Is there any way to avoid this ??? or at least forcing the display of the Left and top side
For some reason I have lost almost all the day on this with no luck so far
Thanks

Many hours later and the only fix I can do is to "hack" the scaleX/Y to force zoom to 1:0 ...this way to content is not affected by the browser zoom level.
Any better solution to prevent my flash to be incomplete (left/top) when the user use the browser zoom feature??

Similar Messages

Photoshop CS5 - zoom level problem

whenever i put my view mode in Fit on Screen mode, it is not showing any preview except the transparent background, it does not even show view in 33%, 66.7% or any fractionate zoom. view is only visible in 25% / 50% / 100% / 200% / 300% / 400% any upper.

What exactly isn't working? What system are you on? As a start, run the Creative Suite Cleaner Tool. Anything beyond that will really require more info.
Mylenium

Change Browser zoom on load

My HTML Captivate module does not display correctly if the viewers browser is not set at 100% zoom. I am looking for a way to change the browser zoom level to 100%. I am willing to manually change the JavaScript or index.html. Anyone have a process for this?

You cannot change the users browser settings like that.
For accessibility reasons I don't know why you would want to.

Why does not safari allow to keep the zoom level over the whole website? This is universal problem for all ipad browsers.

This is a big problem on sites like Tomshardware and Sweclockers and probably many more that Safari is not capable of keeping the zoom level the same over all website pages. And it makes the browsing experience on the IPAD an annoyance.
You have to constantly double tap to see the website clearly for each webpage load. There should be settings to allow to remember the zoom level
for a whole website. So you don't have to double tap on every new page of the website.
The other browsers like ICAB and Mercury are not handling this any better and seem to be limited by the webkit rendering options available.
It's instantly visible on Sweclockers and it becomes a problem on tomshardware when you click on a review link.
I have included pictures here that showcase the problem.

We are all just your fellow users here. If you intended this as a suggestion to Apple, your best bet would be to submit it at this link:
http://www.apple.com/feedback

Avoiding applet main window resizing when using browser zoom?

Hello, I haven a applet embedded into a jsp page into an APPLET tag, with a fixed height and width, same values as the JPanel has on the applet with all the elements inside of it, my problem is, that if I use the browser zoom, the JPanel respects width and height but JApplet window does not, and increases until I stop zooming the site, I'd like to avoid this, I already tried by setting these parameters on the init function on the JApplet class:
this.setSize(593, 468);
this.setMaximumSize(new Dimension(593,468));
this.setMinimumSize(new Dimension(593,468));
this.setBounds(0, 0, 593, 468);
this.setPreferredSize(new Dimension(593,468));
But it does not work, is there something like a this.setResizable(false) for the JApplet class? I understand that JApplet is a subclass of JFrame isn't? please, any idea would be highly appreciated, have a nice day!!

saman0suke wrote:
So far I have the layout as NULL,Java doesn't have a NULL. Presumably you have a null layout. Don't do that/ Learn how to use layout managers and maybe you won't have a problem with the container being resized.
db

Missing zoom level?

Having upgraded from Firefox 3 to Firefox 8 I am having trouble getting the same zoom levels as before. I used to make the text one level smaller than the default, but when I do that in Firefox 8 it is the same as when I made it two levels smaller in Firefox 3. Does anyone know if the levels have changed? Any way to get that in between zoom level again?

I can't check back to 3.6.* this is what is current and you can
change the values to something else in your about:config
toolkit.zoomManager.zoomValues default string .3,.5,.67,.8,.9,1,1.1,1.2,1.33,1.5,1.7,2,2.4,3
see
* http://kb.mozillazine.org/About:config_entries
* http://kb.mozillazine.org/Toolkit.zoomManager.zoomValues

Unresolved bug in adobe reader x with non-default windows zoom level

This seems to have already been brought up here about a year ago: http://forums.adobe.com/thread/776060.
I am using Windows 7 Professional 64-bit with Firefox 12.0 and Adobe Reader 10.1.3. Here is a description of the problem:
Whenever I open any PDF file in a browser (firefox or IE) using the adobe reader I am unable to select text, save the file or interact with the content in any meaningful way because the plugin does not recognise my cursor position. If I click on some text in a PDF document, the reader will immediately highlight a region of text between where I clicked and where it thinks I started clicking from (above 20% of the screen above and to the left of where I actually clicked on the page). If I roll my mouse over the region where the dashboard normally appears, the dash does appear as intended and the cursor changes in response to hover over buttons, as if everything were working, but I am unable to click on anything (clicking does nothing). If I click and hold the dashboard when it appears, it immediately jumps to another region of the page, as if it thinks I moved the mouse (20% up and to the left again). I have recently reformatted and am now using a fresh install, and the issue remains. My desktop zoom level in windows is 150%. The problem appears only inside the browser; viewing PDFs directly in Acrobat Reader X works without issue.
I can resolve the problem either of two ways:
a) Reverting back to the default windows zoom level (125%).
b) right-clicking on the Adobe Reader X icon, navigating to the compatibility tab and clicking "Disable Display Scaling on high DPI settings"
The workaround is easy but it's disappointing that adobe hasn't fixed this. Please consider that it would mostly affect individuals who are vision impaired and might not have the know-how to resolve the problem or check for solutions online, let alone post comments such as this. As far as I can tell this problem severely impaires the functionality of adobe in any browser on any non-standard zoom windows installation.

Please be sure to post your issue in the following Feature Request/Bug Report Form.

BaseMap zoom level bug?

Hi guys,
i noticed a weird behaviour of mapviewer if you construct your own base maps from geometries.
it all ends with the error:
"foi width value is wrong"
then the memory runs full and i have to kill the browser.
then i looked into my base map / tile layers and i think i found the cause of the problem:
<zoom_levels levels="5" min_scale="8.0335569E7" max_scale="5.54424757E8" min_tile_width="120.0" min_tile_height="Infinity">
<zoom_level level="0" name="level0" description="" scale="5.54424757E8" tile_width="Infinity" tile_height="Infinity"/>
<zoom_level level="1" name="level1" description="" scale="3.42065228E8" tile_width="Infinity" tile_height="Infinity"/>
<zoom_level level="2" name="level2" description="" scale="2.11045085E8" tile_width="360.0" tile_height="252.0"/>
<zoom_level level="3" name="level3" description="" scale="1.30209166E8" tile_width="180.0" tile_height="126.0"/>
<zoom_level level="4" name="level4" description="" scale="8.0335569E7" tile_width="120.0" tile_height="84.0"/>
</zoom_levels>
note the "Infinity" in the first 2 levels. I figured this is the reason because when i start the map in 2nd zoom level everything works perfectly, but as soon as i go in 2nd or first level it just freezes up leaking memory all over again.
I'm not completely sure how this happened. i created a new tile from the base map automatically creating the zoom levels and getting the min/max values from the map (load from map).
now as it works i don't really need a solution but i wanted to ask if this is known and/or intended. maybe i missed something during creation.
regards,
jR
Edited by: jR-ora on 18.03.2010 07:22

Interesting... you should file the bug if you can reproduce it more than once. Hopefully they'll fix it soon. Not uncommong for Apple software to have bugs on only certain machines. Usually related to GPUs and things that all machines don't share in common.

CS4 NOT capable of sharp displays at all zoom levels

I must have been asleep, until now, and missed the significance and importance of what follows.
In post #11 here:
http://forums.adobe.com/thread/375478?tstart=30
on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
"You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.
1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
2. Here's another Adobe TV video from Deke McClelland:
http://tv.adobe.com/#vi+f1584v1021
In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
under the heading 'GPU powered display', this text appears :
"Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
http://tv.adobe.com/#vi+f1556v1686
After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

Thanks, Andrew, for bringing this up. I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels. I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels. After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off. They look similar, if not the same.
The "new", OpenGL way of display is using bilinear interpolation.
I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation. This infers that the interpolation is bilinear.
Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ). It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things. Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below). With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated. With bilinear, those details will still be visible but with less sharpness than other details. Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't. To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts. Resolution of the monitor used may also be a factor. The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not. CRT vs LCD may also play a role in noticeability.
The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up. I do not believe this is correct. There are some integer zoom percentages that will appear less sharp than others. It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
Overall conclusion:
The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect. I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%. It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows. When I think about it, that appears to be just what Adobe is doing.
Some sample comparisons:
I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation. One is of a simple grid made up of 1 pixel wide lines. The other is of an image of a squirrel. You might find them interesting. In particular, check out the following:
Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
Notice how nearest-neighbor favors sharp edges. It isn't accurate but it's sharp.
On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions. There are differences in sharpness though at different zoom percentages for bilinear, though. I just didn't include enough samples to show that clearly here. You can see this yourself by comparing results of zooms a few percentages apart.
Well, I hope that was somewhat helpful. Comments and corrections are welcomed.

Open a pdf in an url with parameters #zoom=scale,left,top

In the previous versions of Adobe Reader, it was possible to open a pdf in the web browser adding some arguments : #zoom=scale,left,top.
So we could open the pdf at a specific position, with a specific zoom.
But in the last version for windows, 10, the parameters 'left' and 'top' seem to be ignored. Only the zoom value is taken into account.
There is no error message, no warning. We could write the values we want for the left and the top but nothing happens.
So, I was wondering why it doesn't work anymore ?
And to be sure, I re-installed the version 9 of Adobe and it works, but not with the 10.
(and I hope that is not a fonctionnality which wasn't re-implemented in Adobe Reader 10).
If someone has an idea...
Thanks

So, nobody has an idea ?
Juste to be more clear, I give an example :
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_open_parameters.pdf#zoom =300,200,200
Then, if you enter this url in a new tab, considering you use the adobe reader plugin to open pdf in web browser, the file will be opened with a zoom of 300, and the letf corner position will be at 200 pixels of the right, and at 200 pixels of the top.
But it doesn't work with Adobe reader 10, that's my problem...
Could someone help me with this ?
Bye

Page size keeps changing between pages based on browser zoom

I recently started designing a web page for a golf league. I designed my main page (index.html) and have it laid out all nice and neat with 9 divs (outer, wrapper, logo, social media, topnav, banner, content, rightside, footer). My main page has horizontal navigation links near the top of the page for 7 different pages (Home, Course, Events, History, Statistics, About, Contact). I created 6 blank html files for the other 6 pages and then created and applied the template from my main (Home) page to the other 6 pages.
All the pages are laid out perfectly and everything seems fine. However, when I view the web pages and use the zoom on my mouse (CTRL + Mousewheel), it only remembers the zoom level for the current page that I'm on. NOTE: FYI, I'm viewing all of these pages offline, which I assume might be the problem.
For example, if I'm on my main page and zoom in, then click the "Events" link, it switches to the Events page, but doesn't have the same zoom level. These zoom levels also seem to be saved (to my browser, not the dreamweaver code), because when I close the browser and reopen it to the web page, it remembers the previous zoom settings.
I just started building a web page a few days ago and don't have a published web page as I haven't selected a host yet, but plan to when I know how what exactly I need in terms of size. All the web pages I've been viewing are on my hard drive. Is that why the zoom is not consistent across all my pages? To clarify, if I zoom all the way in on my home page, then click "Events", the Events page won't necessarily be zoomed all the way in, it will be at the same zoom level as the last time I viewed it.
I just want to know if this issue will go away when I actually publish my page to the internet and view it on the web? If not, I'd like to tackle the problem now before I publish it because this site has to be professional since we're holding a big charity event in the fall with a major and well known charity and celebrity.
Thanks in advance for any help!

You're not using frames or framesets are you?
In which browsers are you testing your site?
My experience in Firefox, Chrome & IE9 is that Ctrl++ (zoom) remains constant until I change it.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com/

Missing left border on Word Document

I have a word document (Windows Vista) in A5 size, landscape, with a 4 sided border. The print preview shows all borders but when printing on HP L7480 Officejet Pro the left edge of the document is missing including the border. I have tried resetting margins etc. Help!

I'm guessing that at some zoom levels, table borders display OK; at others, the odd mixture of thick, thin, and no borders, varying cell-to-cell, are a bit scary because they suggest there's something very odd about the way your tables are set-up. However, your tables DO print correctly on your office/home printer.
Try Edit > Preferences > Page Display and then, in the Rendering section, untick (disable) the Enhance thin lines option.
I can't help feeling that Acrobat should be able to distinguish between a (Word) table border, a fine line in a scaled graphic, and hairlines designed to assist commercial printers. Or, until that day arrives, that this option be disabled by default. But that's just me.
You can also mitigate this effect to some extent by setting all table borders to at least 1.5 pnts, and reducing their visual weight by using color (usually a shade of blue).

Want to set a default zoom level for safari? Here's how you do it.

If you like to set a default zoom level for safari so you don't have to hit Ctrl+ (or Ctrl-) every time you start Safari and open a new tab, here's how you can do that. This should work on Safari for mac, too:
1) create a file named defaultzoom.css (or any name you like, just make sure it has a css extension.)
2) copy and paste in the following:
body {
zoom: 130%;
change 130 to whatever number suits you. >100 means zoom in, <100 means zoom out. Don't forget the % percent sign!
3) in safari, go to Preferences > Advanced. Under style sheet, select Other... and point to the file you created.
4) you may need to restart safari for the change to take effect.
Voila. Hope that helps someone.

Yes you are right!
This CSS zooming is a crude hack. I think it basically treats a web page like a pdf document where you just enlarges everything.
When you zoom manually, safari does a smarter sort of zoom where it enlarges but tries to keep widths of the elements the same size, reflowing text where needed and scrolling only when necessary.
If the web page has a fixed size that is smaller than your browser window, like this forum, css zoom works ok. But with a page like gmail, which has no width constraint, you get into trouble.
Hmm, wait, I just checked out wiki, which also uses up all available screen real estate, but does NOT have this problem.
Notice in gmail, even if you zoom way out below what should be 100%, the login is still off the screen. The font gets real small but the width of the page stays the same. The css zoom basically "sticks" and isn't completely reversible.
Bottom line: you have to decide which is more annoying: having to hit Ctrl+ for every tab you open, or running into some problematic pages.
On Windows, I use autohotkey (a kdb and mouse macro scripting program) to switch off the CSS on the fly when I need to. I think Mac has similar capability built in, right? If I were really clever, I guess I could program autohotkey to send a few ctrl+ whenever it detects a new window or tab in safari, but I'm not there yet.
Bottom bottom line: Apple needs to add this feature. It's a pretty basic accessibility feature. Doesn't Apple have like an accessibility guru/advocate?

Safari on rMBP has 200% zoom level by default when viewing standalone images.

I have a MacBook Air 13" Mid 2010 and recently purchased a MacBook Pro with Retina Display 15" Mid 2012. I have updated Safari to 6.0 on both machines, but here comes the problem when I use Safari to view a standalone image on my rMBP.
Normally when I view a standalone image on Safari, the zoom level is 100% which means I see the actual pixeles of the image. Once you open an image in a new tab or a new window, if the dimensions of the image is bigger than the window, let's say 5000x4000, the dimensions of the image will be adjusted to fit within the window. And then the cursor becomes a tiny circle with the "+" sign inside (sorry for my poor description, I hope you can get it) which is the zoom icon, by clicking the image you zoom to the actual pixels of the image which shows 100% of the image.
However this works on my MBA but it doesn't on my rMBP as the zoom level is 200% by default. The following web pages are the ones where I found to have the same problem and they have better explanations:
http://notes.jayrobinson.org/post/25599469833/the-images-above-show-safari-5-2-w ith-page-zoom-on
https://twitter.com/jayrobinson/status/214443964516937729
Sorry for the long post, but I just wonder if there is a way to fix the problem or if Apple can do it?

I've seen this reported before -- sometimes PSE needs to have the zoom set to even multiples of 25%. You can try searching Adobe's site to see if anyone has found a solution.
Ken

Can I keep firefox at a 125% zoom level? I use my HDTV as a monitor and would like the view to be larger without having to hit "ctrl +" on each web page.

I would like firefox to default to a 125% zoom level. Is ther a way I can do this through firefox or through my desktop?

The following Add-on will allow you to set whatever default %-age works best for you. After install, go to Add-ons > Extensions > Default FullZoom Level > Options, in the Options window, "Default FullZoom Level (percent)". That will set ALL pages at your choice.
*'''''Default FullZoom Level''''': https://addons.mozilla.org/en-US/firefox/addon/default-fullzoom-level/
*Support for '''''Default FullZoom Level''''': http://forums.mozillazine.org/viewtopic.php?f=48&t=659681&start=75
Also look at NoSquint
*'''''NoSquint''''': https://addons.mozilla.org/en-US/firefox/addon/nosquint/
*More info on NoSquint: http://urandom.ca/nosquint/
'''If this reply solves your problem, please click "Solved It" next to this reply when <u>signed-in</u> to the forum.'''

IE Browser zoom level problem (Avoid missing Left/Top portion)

Similar Messages

Maybe you are looking for