Pop up modal browser window inside another browser

[Jimmy]

Is it possible to open a pop-up browser window (modal-style) inside
another browser?

e.g.
// assuming something is calling this function inside the html as some
event got triggered
function doSomethingInDiffWindow() {
// do something
// open up a pop-up modal window
// continue back on doing something after pop-up modal window
closed
}

Thanks,
Jimmy

[David Golightly]

On Aug 14, 2:06 pm, Jimmy <[e-mail]:

Is it possible to open a pop-up browser window (modal-style) inside
another browser?

e.g.
// assuming something is calling this function inside the html as some
event got triggered
function doSomethingInDiffWindow() {
// do something
// open up a pop-up modal window
// continue back on doing something after pop-up modal window
closed

}

Thanks,
Jimmy

Got to get some terminology straight. "Browser" is shorthand for User
Agent, which is the "make" of a particular navigator (IE, Firefox,
Safari, etc.) Using standard client-side JS alone, there are no
straightforward techniques to get one "browser" to manipulate another.

What you probably mean (though I can't be sure) is "window", which
refers to the actual window of a particular browser. In JS, the
"window" is just another object, and your script can have references
to multiple windows (in general, as long as they're opened by a user-
triggered action in your script - most UAs now block script-triggered
popup windows).

So instead of using window.open, you want a window inside of a
window. Which means <iframe>. Making it modal is no mean task, but
you might investigate Lightbox http://www.huddletogether.com/projects/lightbox/
for relevant techniques. The code is there, I leave it for you to
inspect it.

-David

[TheBagbournes]

Jimmy wrote:

Is it possible to open a pop-up browser window (modal-style) inside
another browser?

e.g.
// assuming something is calling this function inside the html as some
event got triggered
function doSomethingInDiffWindow() {
// do something
// open up a pop-up modal window
// continue back on doing something after pop-up modal window
closed

http://www.extjs.com/deploy/ext/exam...g/msg-box.html

or http://www.extjs.com/deploy/ext/exam...log/hello.html (which is in fact modal:false, but would be modal if modal:true were actually used)

[Thomas 'PointedEars' Lahn]

David Golightly wrote:

Got to get some terminology straight.

Yes, please. Eventually.

"Browser" is shorthand for User Agent,

It isn't. Web browsers are a *subset* of ([X]HTML) user agents, and because
they are the greatest subset, many people (especially uninitiated) refer to
Web browsers only.

http://www.w3.org/TR/html401/conform...idx-user_agent

which is the "make" of a particular navigator (IE, Firefox, Safari, etc.)

Depending on what you mean by "make" that statement may be wrong.

Using standard client-side JS alone,

What would "standard client-side JS" be, knowing that any ECMAScript
implementation itself is proprietary by definition and different not
only by the ECMAScript standard's provision but also empirical proof?

there are no straightforward techniques to get one "browser" to
manipulate another.

Fair enough because of the "straightforward".

What you probably mean (though I can't be sure) is "window", which refers
to the actual window of a particular browser. In JS, the "window" is
just another object,

Windows (and frames) are represented in the AOM of the UA as Window
objects. These objects are host objects which clearly distinct them
from native objects; they are _not_ part of the programming language,
but implementations of APIs.

[...]
So instead of using window.open, you want a window inside of a window.
Which means <iframe>.

It could also be a `frame' element.

Making it modal is no mean task,

It is an impossible task instead.

but you might investigate Lightbox http://www.huddletogether.com/projects/lightbox/ for
relevant techniques.

Rather not.

The code is there, I leave it for you to inspect it.

I consider it bad advice to refer a newbie who is unable to make an educated
evaluation of code which authors themselves did not know what they were
doing to that code.
PointedEars, working down his TODO list
--
"Use any version of Microsoft Frontpage to create your site. (This won't
prevent people from viewing your source, but no one will want to steal it.)"
-- from <http://www.vortex-webdesign.com/help/hidesource.htm>