Skip to main content

Popup Windows: open() Parameters


Until now we've focused on the process of opening and closing the popup window. We'll now shift to the properties of the popup itself. All of the popup's properties are set in the open() command. We've used open() in every script in this tutorial.

Specifically, the properties of the popup are set in the third argument for open() which is a list of properties for the popup. Properties are set somewhat similar to the way HTML attributes are set: the name of the property followed by an equal sign followed by the value. Properties are separated by commas. Because of a widespread bug in MSIE, do not put any spaces in the list of properties. The entire list of properties goes inside quotes. So, for example, the following line of code sets widthto 400, height to 200, and turns scrollbars on.
We'll begin with the width & height properties, which are always required except in full screen mode. All other properties are optional. Here's a list of popup properties.
width & heightthe dimensions of the popup
left & topthe distance from the top and left side of the screen
toolbarif the popup should have a set of navigation buttons across the top
locationif the popup should have a location bar where the URL is displayed
directoriesif the popup should have a row across the top with buttons to popular web sites
statusif the popup should have a status bar across the bottom
menubarif the popup should have a menu
scrollbarsif the popup should have scroll bars
resizableif users can resize the popup
dependentif the popup should close when its opener window closes
full screenhow to open a full screen popup
channelmodeMSIE's channel mode
Labels:

Comments

Post a Comment

Popular posts from this blog

Regression Testing

From  http://www.softwaretestinghelp.com/regression-testing-tools-and-methods/ The selective retesting of a  software  system that has been modified to ensure that any  bugs  have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the  software . Also referred to as  verification testing , regression testing is initiated after a  programmer  has attempted to fix a recognized problem or has added  source code  to a program that may have inadvertently introduced errors. It is a  quality  control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity. What is Regression Software Testing? Regression means retesting the unchanged parts of the application. Test cases are re-execu...
Post a Comment
Read more

ThreadPoolExecutor使用

From 洞玄的博客 http://dongxuan.iteye.com/blog/901689 jdk官方文档（javadoc）是学习的最好，最权威的参考。 文章分上中下。上篇中主要介绍ThreadPoolExecutor接受任务相关的两方面入参的意义和区别，池大小参数 corePoolSize和 maximumPoolSize，BlockingQueue选型（ SynchronousQueue， LinkedBlockingQueue， ArrayBlockingQueue ）；中篇中主要聊聊与 keepAliveTime这个参数相关的话题；下片中介绍一下一些比较少用的该类的API，及他的近亲： ScheduledThreadPoolExecutor 。 如果理解错误，请直接指出。 查看JDK帮助文档，可以发现该类比较简单，继承自AbstractExecutorService，而AbstractExecutorService实现了ExecutorService接口。 ThreadPoolExecutor的完整构造方法的签名是： ThreadPoolExecutor (int corePoolSize, int maximumPoolSize, long keepAliveTime, TimeUnit  unit, BlockingQueue < Runnable > workQueue, ThreadFactory  threadFactory, RejectedExecutionHandler  handler)   先记着，后面慢慢解释。 ===============================神奇分割线================================== 其实对于ThreadPoolExecutor的构造函数网上有N多的解释的，大多讲得都很好，不过我想先换个方式， 从Executors这个类入手 。因为他的几个构造工厂构造方法名字取得令人很容易了解有什么特点。但是其实Executors类的底层实现便是ThreadPoolExecutor！ ThreadPoolEx...
Post a Comment
Read more

Spring MVC 3.2 Preview: Introducing Servlet 3, Async Support

Continuing the Spring 3.0 "simplification series" started by Keith and Chris , I would like to provide a quick overview of simplifications in scheduling and task execution enabled by Spring 3.0. I will be walking through a basic sample application that you can checkout from the spring-samples Subversion repository. It has been designed to be as simple as possible while showcasing both annotation-driven and XML-based approaches to scheduling tasks in Spring 3.0. Let's begin with the annotation-driven approach. You can run it directly via the main() method in AnnotationDemo. If you take a look, you'll see that it's nothing more than a bootstrap for a Spring ApplicationContext: public static void main(String[] args) {      new ClassPathXmlApplicationContext( "config.xml" , AnnotationDemo. class ); } The reason nothing else is necessary is that the ApplicationContext contains an "active" component, which we will...
Post a Comment
Read more