Are you sure you need actual windows? It sounds like you can get what you need using divs like suggested in other replies will give you what you need. If using jQuery, this is all wrapped up as "dialog"s. https://jqueryui.com/dialog/ Other js libraries have similar implementations as well. A dialog can have static content, or pull in dynamic content with an Ajax request, and you can have as many open and drag-able on screen as needed.
On Sep 9, 2016 8:19 AM, "Peyton Todd" <peytont...@att.net> wrote: > Hello Everyone, > > I, too, am glad to know this list still exists, since I have a question. > To identify myself briefly, I’m a former member of the group, now retired, > so I no longer write Cold Fusion code. My question concerns a research > project that I presented to the group a few years ago, when members were > asked to describe their work regardless of its relevance to Cold Fusion. > The project is about the speech of a hearing child of deaf parents, and I’m > hoping one of you with knowledge of HTML and Javascript can help me choose > between two ways of presenting the data. > > I apologize for the great detail of this post, but I can get to my > question right away before going into all that detail: > > *Does anyone know how to make the URL disappear in a child HTML window? If > not, then is there some other simple way to get the effect I want?* > > Apparently the standard way would have been to set location=no when > specifying the parameters to the window.open command. But that doesn’t > work, and I remember reading somewhere that the W3C has decided to disable > it. Is there some other way to make the URL disappear? Or maybe an > alternate way to get a child window? (I thought of having DIVs that are set > display=block or display=none, but apparently the user would not be able to > move them around on the screen (No doubt it could be done via buttons that > reset their left and top properties, but that would not be simple to > program, and I need the ability for multiple windows to be open at the same > time, which would make it even more complicated.) > > Admittedly this has only to do with aesthetics, but I want it to be as > pretty as possible! > > To see what I have so far, please download the little folder at the > Dropbox link below, and click on “testvideotag.htm” to test it. (It works > in chrome, firefox, opera, and safari, but not in internet explorer.) > > https://www.dropbox.com/sh/x8guh0m7ll5hrr8/AAAJkZjCRKMv7XSKrL2SGF7sa?dl=0 > > The other approach I’m investigating may not tap the expertise of most > ACFUG participants, but I’ll present it in case anyone has a suggestion. It > uses PDFs, and if you want to see what it looks like you could download the > little PDF at this other Dropbox link and run it (“PDF Version.pdf”): > > https://www.dropbox.com/s/9ghu3l5fkfj2t7i/PDF%20Version.pdf?dl=0 > > The PDF version doesn’t display the ugly URL, of course, but my fear is > that Adobe will disable my PDF solution some day – a matter I’ll probably > have to check with Acrobat experts about, but in case anyone has ideas > about it please let me know. > > When I describe my PDF solution, you’ll see why I fear Adobe will disable > it: I like my interface the way it is: little icons that don’t take up > screen space the way opening video inside the page would (there will be > many hundreds of these!). And I like my audio icons the way I have them, > too. If I attach MP3 (i.e. H264) audio to an icon via the sound tool (as in > the leftmost ‘speaker’ icon in my PDF), it plays, but then the standard > Acrobat audio interfaces jumps in and takes over the icon – too small to be > operative. > > If I attach the audio it to a button-icon instead, then everything works > perfectly (as in the rightmost ‘speaker’ icon). But here’s what makes me > think Abobe would some day pull the rug out from under me: with the sound > tool, one is forced to use H.264 (a WAV file is legacy, and leads to the > ‘Do you trust this?’ warning – painful when one must open hundreds of these > little PDFs. And the legacy method is now blocked over the internet > anyway). > > But if I attach sound to a button, only WAV files seem available as a > choice. Remarkably, MP3s are not available for choosing even though they’re > in the same folder as the WAV file. So if WAV files are a security hole > when using the sound tool (forcing one to use H/264 like MP3), why would > they not be when attached to a button? And if they are, then Adobe will > discover the problem and fix it some day, thus disabling the many hundreds > of PDFs I will have prepared by then! > > I should mention that I have Acrobat 9 Pro Extended, from which no upgrade > path is available. To buy a new Acrobat Pro DC costs $449. > > Thanks so much for any help you can provide! >
