That pesky Full Screen alert dialog in recent versions of Reader

When I set the preferences within Acrobat to disable that horrible, pesky Full Screen alert dialog, it still appears on the end-user's Reader software, even though I turned it OFF from within Acrobat [slaps forehead].
Is there any way, by hook or by crook, by script or Acrobat Javascript, to stop this from happening?
There is no point allowing Full Screen functionality if the end-user is scared to death by a horrible dialog box that more or less guarantees - if not encourages - the user to click NO to the full screen experience [slaps forehead again].
Any help with this would be of tremendous value and will be much appreciated as this is driving me nuts.
Thanks in advance,
Jeremy Lerman

It's not a "security" issue per se, but it is a potential issue of misrepresentation - you can craft a PDF to appear as an application (adding screen furniture, etc.) and confuse a user as to what they're subsequently allowing Reader to do. It's the same reason all Javascript alert boxes in Reader/Acrobat start with a "javascript" title, so they can't pretend to be a system message.
Physically exploiting Reader to do something horrible is no longer as easy as it used to be, but it remains possible to confuse a user into allowing some data transfer, if you for example make Reader "pretend" to be your web browser. The FSW popup is also there to allow people a decision point - if the PDF could open FS mode without intervention, it annoys people running high-res monitors where Reader is only taking a portion of their workspace.

Similar Messages

Opening since update to Firefox 6, always get the message that I don't have the most recent version - have removed and reinstalled, but still persists.

I recently updated my Firefox to version 6.0. When it re-opened after installation there was a message that I didn't have the most recent version. I ran the update set-up again but got the same message. I uninstalled Firefox and reinstalled it from a fresh download but it's still happening.
I've restarted the computer several times. It doesn't seem to have helped. Any ideas?

* Download a new copy of the Firefox program: http://www.mozilla.com/firefox/all.html
* Trash the current Firefox application to do a clean (re)install.
* Install the new version that you have downloaded.
Your profile data is stored elsewhere in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder], so you won't lose your bookmarks and other personal data.

Any 3rd party utilities that fix full screen mode for multi-monitor users?

I am a multi-monitor user. As multi-monitor users know, full screen mode is basically useless since if you try to go full screen on one monitor, it causes the other monitor to go blank and become unusable (at least with most programs). Are there any 3rd party utitilities or fixes for this?
Thanks

Spaces, which is what this functionality stems from, was limited in that it used your entire setup and switched all of the screens over; space to space. I never used spaces because I always had multiple monitors and I was always working with multiple apps simultaneously that I wanted to be able to reference while working on the others.
Now they call Spaces, "mission control" and changed the appearance of it, but the functionality remained the same, each workstation comprised all of your monitors, and would switch over all of them when switching to a new "Desktop".
Fullscreen apps wrongly assumes that it can take the functionality of the afformentioned MS/Spaces and use it for one app, negating the whole idea of why someone would have multiple screens (real estate to work with other applications).
If they stop considering multiple monitors as one Workspace, they can then make it so they are asynchronous "tablets" instead of one conjoined entity.
So, you say people have been asking about this for 2 years, I've been asking for this for 5!
The issue here is, the only answer is to not use it. Making Mission Control and Fullscreen apps completely ignored by people like us, where I could be using both functions to glide around my work station and three monitors, mixing and matching which apps I want to be viewed on each separate monitor, to perform one single task; together.
It would actually reward people who wanted to utilize Thunderbolt technology and have more then one monitor.
There is no telling why apple chose to push out something that would only support the casual user, with one display, but the only direct way to let apple know that we feel limited by the OS is to send feedback. Even though it seems that we are powerless in this situation, I hope that they do consider how to make this function better.
</rant>

I cannot open youtube videos to full screen after downloading the latest version of flash. HELP

I cannot open youtube videos to full screen after updateding flash to the latest version (11. something) HELP! youtube says it is adobe's problem

To help troubleshoot we'll need the following system information:
Operating   system
Browser
Flash   Player version
When reporting issues with video or audio, it's also helpful to get your system hardware and driver details. Instructions for finding this information can be found here:
Windows
Mac
Finally, sometimes video and audio problems are caused at a lower level and not directly related to Flash Player. I recommend trying both of the links below to see how they perform. If the problem exists with both, then Flash Player is most likely not the culprit as the HTML5 video link does not use Flash Player when playing. You can verify the use of HTML5 by right clicking the HTML5 video and looking for the words "About HTML5" at the bottom of the context menu.
HTML5   video
Non-HTML5 video

On every page I get a box with a 2 and an OK button, the page behind it is grayed out and nothing works until OK is hit. I also get a box that says Suppress more alert dialogs from this page? With a check box and the OK button.

Hoping to get this to go away!This just started today, I have run all my virus/malware, etc with no luck. Uninstalled and reinstalled Firefox as well. Any help and or suggestions would be appreciated as this is highly annoying!

This issue can be caused by an extension that isn't working properly.
Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
* [[Troubleshooting extensions and themes]]
In Firefox 4 you can use one of these to start in <u>[[Safe mode]]</u>:
* Help > Restart with Add-ons Disabled
* Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)

JInternalFrame Full Screen Exclusive mode lag Windows 7?

<font size=2>Hi everyone I'm not sure if i'm posting this question in the right category so feel free to move it. I recently have been playing around with full screen exclusive mode and JInternalFrames. Now what iv'e noticed is on every platform i've tried it works fine. When clicking and dragging the JInternalFrame to a new location it is quick and responsive. However when doing this same operation in Windows 7 the JInternalFrame lags significantly behind the mouse location as i'm dragging the internal frame. I haven't had a chance to test this on any other Windows platforms such as Vista or XP but I don't think it happens on those platforms, at least I don't remember this ever happening when I had Windows Vista and it doesn't occur in Mac OS 10.6.
The following are the circumstances i've found that produce this problem:
*1. The program is set to Full Screen Exclusive mode.*
*2. You are using Windows 7 (possibly other Windows platforms)*
*3. Click and drag a JInternalFrame to a new location.*
I've tried several things to see if it fixes the problem such as setting the look and feel to cross platform but nothing helps. In fact when the LAF is set to cross platform it is even worse.
Now i'm new to Full Screen Exclusive mode so i'm guessing (hoping) this is a problem caused by an error on my part. Here is the source code, i'd appreciate it if you give it a try. My question is how do I fix this lag so that the JInternalFrame is quick and responsive to the user dragging the window and i'm also wondering if this only happens on Windows 7 so if anyone could also tell me if they experience the problem I am describing and the OS you are using that would be great. Thank you guys :)
Also any input about wether i'm setting up full screen exclusive mode correctly would be much appreciated too.</font>
package lag;
import java.awt.event.*;
import java.awt.*;
import javax.swing.*;
public class InternalFrameLag
    public static void main(String[] args) {
        SwingUtilities.invokeLater( new Runnable() {
            public void run() {
                new InternalFrameLag();
    GraphicsEnvironment env = GraphicsEnvironment.getLocalGraphicsEnvironment();
    GraphicsDevice[] devices = env.getScreenDevices();
    GraphicsDevice device;
    JFrame frame = new JFrame("Internal Frame Lag");
    JDesktopPane pane = new JDesktopPane();
    JInternalFrame internalFrame = new JInternalFrame("Internal Frame", true, true, true, true);
    JButton exit = new JButton("Exit");
    public InternalFrameLag() {
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setUndecorated(true);
        exit.addActionListener(new ActionListener() {
            public void actionPerformed(ActionEvent e) {
                System.exit(0);
        exit.setPreferredSize(new Dimension(250,23));
        internalFrame.setLayout(new FlowLayout());
        internalFrame.setBounds(100,100,500,300);
        internalFrame.add(exit);
        pane.add(internalFrame);
        frame.add(pane);
        // get device that supports full screen
        for(int i = 0; i<devices.length; i++) {
            if(devices.isFullScreenSupported()) {
device = devices[i];
break;
if(device!=null) {
device.setFullScreenWindow(frame);
internalFrame.setVisible(true);
} else {
System.exit(0);
Edit: Decided to make the font size bigger. Eyestrain is killing me.

Darryl Burke wrote:
neptune692 wrote:
<font size=2>
Edit: Decided to make the font size bigger. Eyestrain is killing me.Hopefully that will carry over to my response and I won't have to edit to add it ;)
I don't see the lag you describe. There's some flicker when moving the internal frame around rapidly (it looks as if the borders follow the content a split second later, but can't be caught in a screen capture) but that's no different when I show the internal frame in a normal (not full screen) window.
<tt>Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Darryl>java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing)</tt>
db<font size=2>Thanks for your reply and thanks for testing out my code. Could this lag be something wrong with my VM on Windows 7, cause the lag is extremely bad as in it takes a couple seconds for the internal frame to catch up with the mouse. I also just noticed that any other components in full screen exclusive mode on Windows 7 lag as well. Such as scrolling though a large amount of text, the scroll bar will lag far behind the mouse location and take a couple of seconds to catch up even when the mouse is moving fairly slow. I was hoping it was something in the code I was doing wrong but I guess not? Any suggestions on how I could fix this problem? It really makes my applications appear sluggish. For example when you click on a normal window such as in Windows Explorer and drag it to a new location the mouse stays in a fixed position on the window while you are dragging it. However with this lag the mouse appears to be "detatched" from the window and does not stay in the same location on the window while dragging. Does anyone else experience this or is this normal? I'm using Windows 7 64bit but I don't think that would make any difference. I'd also like to point out that I'm using Java 6 update 21 I don't know if that would make a difference opposed to update 17.
Thanks again.</Font>
Edited by: neptune692 on Oct 2, 2010 10:23 AM

Open .swf in full-screen browser window?

Hi there! I would appreciate if someone could help me with this:
I have a .swf that I embed in an .html file. When loaded, the html file opens up in a window with the application taking up only 50% of the window. I'd like to have the application open in a window that's full screen. Is that possible at all?
The .html file I'm using is a standard one generated by Captivate and looks like this:


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Title</title>
<script src="standard.js" type="text/javascript"></script>
</head>
<body   bgcolor="#ffffff">
<center>
    <div id="CaptivateContent"> </div>
    <script type="text/javascript">
       var so = new SWFObject("myfile.swf", "Captivate", "891", "551", "10", "#ffffff");
        so.addParam("quality", "high");
        so.addParam("name", "Captivate");
        so.addParam("id", "Captivate");
        so.addParam("wmode", "window");
        so.addParam("bgcolor","#ffffff");
        so.addParam("menu", "false");
        so.addVariable("variable1", "value1");
        so.setAttribute("redirectUrl", "http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash");
        so.write("CaptivateContent");
    </script>
    <script type="text/javascript">
        document.getElementById('Captivate').focus();
        document.Captivate.focus();
    </script>
</center>
</body>
</html>

Hi,
What do mean by browser window?
If you mean the File>Open dialog, double click on the Title bar to get it back to a smaller size.

How to Remove maximize/minimize/close top-bar in full-screen view [MAC]?

Hi.
My Q. is pretty much as the title implies.
It's a small thing, and maybe kind of trivial,
but I'd like to know how to get rid of the maximize/minimize/close top-bar in full-screen view in Adobe Reader on the Mac.
I am definitely in fullscreen view [I hit command+L], just so you know,
but I still have that top grey bar showing with the maximize/minimize/close buttons [the red, yellow, and green].
As I said, kind of a trivial concern, but I'd like to know how to hide that in full-screen mode.
I tried searching around a few places for an answer, but there is nothing too obvious.
I can't find anything in the full-screen preferences of reader either. Maybe I'm missing something...
Thanks!

Version 11.0 , so I guess that is the most recent?
I think this is an application-specific problem too, because I don't encounter this in full-screen mode with other applications.

A smarter full screen interactive

It would be great if the full screen interactive mode was smarter. It gets very tedious when within a single app/game the user is constantly switching back and forth full screen mode,
There must be a way to make it smarter and less tedious without compromising security.. I am throwing out some suggestions:
1. Provide an option to 'Always allow Interactive mode for this site' (or domain).
OR
2. Provide a checkbox option to 'Always allow Interactive mode for this session'.
OR.
3. Within a single session automatically allow the interactive mode for the current swf if the user already accepted once.
To see what I mean try it here at Lee's website:
http://leebrimelow.com/flash/fullkeys/
Go to full screen mode. Accept. Esc to leave full screen mode. Try going to Full screen mode again. Why is does it need to ask again for my permission? It already asked me once.
I added a feature request a couple of months ago and it was withdrawn.
https://bugbase.adobe.com/index.cfm?event=bug&id=3366434
I am starting this dicussion again, because I am certain that the runtime folks can improve on this..
..and a last point. For reference, Chrome solves this in a pretty elegant way. It provides a pull down menu with 2 options. 'Ask by default', 'Always allow on this site'

While we get that the full-screen notification is annoying in the context of some games, it's there for your protection (and as a response to actual real-world security incidents that happened over the years in various products, including Flash). You'll see similar behavior in other browser plug-ins and HTML full-screen content.
Imagine this grossly over-simplified scenario:
- You go to a game site supported by ads from a third-party ad network
- A malicious actor creates and injects a malicious ad into the ad network, and it shows up on your game site (again, real-world example)
- You're playing your game, and your phone rings. It's your cellphone provider and you forgot to pay the bill. They want to take a payment over the phone before they turn it off.
- You tab out of the game and fire up your bank's website to check your balance.
- The malicious ad noticies that you've gone to yourbank.com, and quickly fires up a full-screen window that looks exactly like your browser, displaying the homepage of your bank's website. (That the ad "notices" this action without some other bug in play is a stretch, but useful for illustrating the point.)
- Everything looks normal. The SSL lock icon is there, and the address and website look sane. You type in your credentials.
- Instead of going to your account info, you get a "we're sorry, but we're down for maintenance" message.
- Some kid in the Ukraine gets a new dashcam and a jet-ski.
In reality, there are layers of mitigations along the way that would make this really difficult -- but the motiviation for displaying the full-screen window in Flash is because there's no way to know 100% for sure that the full-screen content is going to be legit. It's a security-in-depth measure.
So that dialog exists basically to say "Hey, if this looks like your web browser, something is very wrong. Hit Escape to get back to reality.".
The best way to get around this would be to encourage the game publisher to also offer the game as an Adobe AIR application. It's basically a desktop version of the Flash game. This removes all of those concerns about what crazy stuff third-party sites can do, because you're operating in the context of a desktop application (where the content you encounter can generally be trusted) vs. the open web (where you should trust very little).

Trusted Full Screen Interactive

I am working on a flex based app which frequently goes into Full Screen mode. The recent Full Screen Interactive mode is awesome. But is there a way to keep the 'Allow' popup from coming up every single time it goes to Full Screen?
ps. On a completely unrelated note, having access to the traceback in the release version of the player is pretty cool!

The danger with interactive full-screen is the potential for creating convincing UI for phishing attacks. We tend to go conservative on that kind of stuff. We'd rather keep you safe and over-communicate than vice-versa.
It's an interesting feature suggestion though, and I can definitely see how it would be nice for a game you play all the time.
The best way to get traction on it would be to file a feature request (and get some votes) over at http://bugbase.adobe.com/
Thanks!

Full Screen Mode on Tablets

I'm running Photoshop CC on a Microsoft Surface Pro 3. I figured out how to activate the "Touch-friendly" 200% UI scaling, and I found the new screen mode toggle at the bottom of the tool palate. There's only one problem: if you toggle all the way into full screen mode with the palates off (the old "Tab" button toggle), there's no way to turn them back on without a keyboard. Yes, I could simply attach the Surface's keyboard cover, but that seems to defeat a big portion of the tablet-only convenience.
The warning dialog that appears just prior to toggling into full-screen mode claims the palates will be accessible from the sides of the screen (I presume they mean like the collapsed panels in LightRoom), but this is not true. Once they're off, they're completely off, and no amount of swiping from the sides brings them back.
Anyone else experience this, or is it just me?

Nevermind. I just found out that in full screen mode, the "side of the screen" only responds to the stylus, not your finger.
It would be nice if Adobe documented that somewhere

Feature Request- Save in Background in Full Screen

I work in full screen with Menu Bars 98% of the time. I also enjoy the new save in background feature.
The problem is that when in full screen I can't tell when it's saving and the status of the save. This is particularly frustrating when I'm trying to close a file. I think there needs to be an option to have it save in background but pop up a status window, or some way to see the status of the save while in full screen.

Thanks for the suggestion. However it still doesn't show the bar with the save status when I have the floating window on a second screen and photoshop in another. The bottom status bar is attached to the document not the main photoshop window. So no matter where you have photoshop, if you make a document full screen it hides that bottom bar.
I don't think of this as having my cake and eating it too either. Full screen mode with menu bars doesn't exist to minimize distractions (though some may use it for that), but rather to maximize screen real estate. I'm using it so I can pan and flick my images from spot to spot while I retouch. Since they already give us the option to have full screen with menu bars, then I just think it would be nice to have the bottom status bar show as well while in full scren mode. I've always wished I could still see that in full screen to manage efficency while working on large files, but it's never been a bother. Now that it is also where the save status is showing, I just think it would be great to be able to see it in full screen with menu bars mode. And if not, then still be able to have the Save dialog status window pop up while having background save enabled.
** i totally forgot about turning on timing and efficency in the Info panel . That would be a perfect place for them to put the saving status since they already have the other options there.

Impressions of 11.6 full screen nuisance

I think Adobe is going the wrong way with that obsession around the "Full Screen Permission Dialog". It is something disrupting, intrusive and bothering since it was first implemented. I'm sure many, many users said it should NOT appear every single time fullscreen mode is opened. Now you add it as a fat BIG box in our face?! What's happening there?
Why we don't need that dialog every time? Simple: because not being able to use full keyboard in fullscreen does not prevent the app from being used in any way. Furthermore, sometimes when we need to toggle fullscreen very often it is a great nuisance.
I'm a multi-threaded user and I toggle programs very often, I go to and out fullscreen very often. "Full Screen Permission Dialog" is a monolithic approach.
It is not a useful dialog like UAC of Win7 is, it does not mean extra security or anything. It just mean: "You can use your keyboard when on full screen". Doesn't it sounds like Captain Obvious talking?
Bug: Move mouse over the topmost pixel of the screen and another unnecessary screen is displayed saying I'm on fullscreen (Thanks Cpt. Obvious!).

Adobe shuts down for a couple weeks at the end of the year for the US holidays. We only have a skeleton crew around for mission-critical work. We're all just getting back to work and caught up on mail.
The full-screen interactive keyboard dialog exists as a mitigation to phishing sites that would otherwise be able to create convincing spoofs of the entire browser chrome, SSL lock icon, etc. This isn't as big of a concern when keyboard input is restricted to non-printing keys, but becomes a serious threat when full keyboard input is allowed.
Adding a per-URL user preference to suppress the dialog is a reasonable suggestion, although the potential for content hijacking is a little scary. Consider the scenario where an attacker pops your machine and replaces your game SWF with malicious content. If your users were instead presented with a convincing Facebook login screen, for instance, and they did not see the full-screen warning because it was suppressed, it would probably fool a lot of people.
It's definitely an improvement to the end-user experience and reasonable feedback that we've seen echoed a few times already in this forum, but we can only implement it if we can do it in a way that's safe, even in the event that the content is specifically designed to be malicious.
I'll pass your feedback along to your product management folks. I'd also recommend that you file a feature request over at http://bugbase.adobe.com/ and post a link here so that people can vote on it. Requests with large volumes of votes carry a lot of weight in terms of how we prioritize new work.
Just to set realistic expectations, because of the potential risk with a feature like this, once the work was scheduled and completed we would subject it to extensive internal testing. We'd also bring in third-party security auditors to review the final code and design, and penetration testers to exhaustively test it before we would consider shipping. This is a lengthy process, and not something that will be resolved in a few weeks.

Full-screen (spacebar) preview quality testing

[For background story, please read http://forums.adobe.com/thread/1056763 but be warned, it's very l-o-n-g!]
In brief: some people have noted that Bridge full-screen (spacebar) previews (FSPs) don't accurately reflect the sharpness of a photograph. Sometimes this can be explained by individual configuration problems, but it's clear that this is a common issue amongst people using Bridge to assess/score photograph sharpness, without having to build/examine 100% previews for every image.
[It's worth noting that one common reason why FSPs aren't very sharp is because the Bridge advanced preference "Generate Monitor-Size Previews" hasn't been ticked, as this produces a higher resolution image cache. Another cause of very fuzzy previews is random and unexplained, but can usually be solved by restarting Bridge and/or clearing the cache for the selection.]
This discussion concerns the lack of sharpness seen only in FSPs. It can be described as "a subtle but significant loss of detail and sharpness, similar to a slightly out of focus photograph"; imagine a photo with a little bit of blur filter, or a Photoshop PSD at a non-standard zoom setting. This "softening" of the image is caused by Bridge asking the graphics processor to resize the image cache to fit the display. If you select the Bridge advanced preference "Use Software Rendering", you can improve a poor FSP slightly, at the expense of speed, by bypassing the graphics processor.
The test
Visit this web page and download the last image ("2362x3543 pixel, 4.5 Mb") to your computer.
Browse to this image in Bridge, and view it full-screen by pressing Spacebar. Take a screen capture, and save it as a TIFF or PSD.
Adjust your slideshow settings (Ctrl/Cmd-Shift-L), picking "Scaled to Fill", then click on "Play". Save the screen capture, as above.
You now have two screen captures: one FSP, and one cache JPEG reference shot. Examine them side by side at 100%, or layer them in Photoshop and use the hide layer button to flick between images. Pay particular attention to the two left-hand photos, the sharpness check text, and the converging lines.
Make a note of your computer's operating system, graphics processor and driver version, as well as your largest display's pixel dimensions.
Post this information below, together with high quality (10) JPEGs of both screen captures, labelled FSP and REF, and any observations, so we can all see.

OK, it usually takes me a while to let the penny drop, especially when it comes to maths...
I also am busy with the transition of my new Mac pro but with al this here are my results. I include several screenshots but due to upload limit of 2 MB per image in here I downsized the original screenshots a lot, but hopefully it will be clear.
For full screen screenshots I have the asked FSP and REF but also the 100% preview in Bridge with space bar and click. Don't know what your file size is but using EOS 1Dx with 18 MP CR2 files (converted to DNG) it does take me about 1,5 - 2 seconds for both loupe and FSP to build a 100 % preview, and I seem to recall this was not very different behavior on my previous (6 year old) Mac Pro.
You are right (of course... :-) ) regarding the difference between FSP and REF, when studying closely there is a significant detail difference between the FSP and the REF. However, only the 100 % preview matches the original jpeg. The FSP file is on closer look not so good with details but the REF file is only slightly better, both are not correct and therefor the 100 % is still needed.
Here is the FSP screenshot:
and here the REF screenshot:
also the 100 % preview in full screen screenshot:
and finally a composed file with details from original, 100 % REF and FSP:
As said before, at first sight I can't spot significant difference between all options and the full screen (as the preview panel HQ preview) let's me spot the vast majority of unsharpness issues, hence my multiple rounds of sorting and incases of doubt the 100 % option.
So while your theory is correct I'm afraid I (still) doubt the usefulness of this all. If neither the FSP and the REF (although the latter does show a bit better result) can match the results of the original but the 100 % does it well I don't see an easy solution for improvement.
I agree with the quality from the screenshots Curt provided, but Curt also uses the embedded thumbnail instead of HQ preview option. Depending on his needs and hard ware availability it would be nice to see new results with the HQ and monitor sized previews options enabled.
regards
Omke

Don't want DW6 to open new documents in Full Screen? How can I do this?

I have read a few posts and there doesn't seem to be an answer yet. Thought I'd bring this to the forefront and see if anything new has been discovered.
When I open my first html document it always opens in Full Screen, which is huge (wide), covering everything else on my desktop (which I use in conjuction with DW). I have to find the tiny little bottom lower right corner (usually close to and almost hidden by the Dock) and drag the window to a workable size. Obviously a new html page is never the width of the full wide screen, so why does DW assume this is a workable size? We all use the Abode products because they work together with each other, which are usually open and working on your desktop as well. Someone at Adobe didn't think this out!

No Nancy, everything opens just fine, the issue is the document window opens up full-screen behind everything (all my panels are there on top). The window is obviously upworkable until I scale it to fit in the rest of my viewable space. An html page is centered in this wide-screen upon opening, effectively being partially covered with tabs and panels. The outside space that the full screen window takes up is nothing but a solid color, covering useful space where I want to see my panels, some desktop for other apps if I wish etc. So effectively I have to resize the full screen window down, to the edges of the "workable" html designated space, which is all I need to see. Not 8" of a blank, useless window on each side, covering everything else. I would assume most of us web designers are using and viewing other apps, windows etc. on their desktop at the same time. If nothing else you can't even work on the html page until you resize it i order to see the panels which cover it. In PS for instance once you size a document window the program remembers the size on your screen and position where it opened last.

That pesky Full Screen alert dialog in recent versions of Reader

Similar Messages

Maybe you are looking for