«

I`m dynamicly creating a doc for a modeless window in IE 6..

win= showModelessDialog(oArgs, window, sFeatures);
win.document.title = 'some title';

doesnt work.

Any ideas ?

oeyvind
--
http://home.online.no/~oeyvtoft/ToftWeb/

oeyvind toft wrote:
> I`m dynamicly creating a doc for a modeless window in IE 6..
>
> win= showModelessDialog(oArgs, window, sFeatures);
> win.document.title = 'some title';
[...]

It could be for a number of reasons - you haven't explained what oArgs,
window or sFeatures are.

Here is Microsoft's documentation, it includes working examples (though
I didn't test them).

<URL:http://msdn.microsoft.com/workshop/author/dhtml/reference/methods/showmodelessdialog.asp>

Needless to say, showModelessDialog is a Microsoft invention that is
not well supported in other browsers (if at all).

--
Rob

"RobG" <> skrev i melding
news:41b2587d$0$25785$...

> It could be for a number of reasons - you haven't explained what oArgs,
> window or sFeatures are.

thanks Rob

The oArgs, window and sFeatures stuff isnt importaint here.

What puzzles me is that I cant do 'win.document.title = 'some title';'

Oeyvind

--
http://home.online.no/~oeyvtoft/ToftWeb/

oeyvind toft wrote:
[...]
>
> What puzzles me is that I cant do 'win.document.title = 'some title';'
>

Ah, so you are trying to change the title element of the document in
the child window?

There is a previous thread regarding changing the title of the current
document that may be useful on 17 Sept. Search the archives for:

"How do I change the document title?"

In case you can't find it, some relevant parts are below:

Yann-Erwan Perio wrote:
> Richard Trahan wrote:
>
> [changing title of the document]
>
>> In the interest of higher education, what was wrong with my node method?
>
>
> According to the DOM/HTML specification the HTMLTitleElement inherits
> from HTMLElement, which itself inherits from the core Element interface,
> which gives it appropriate DOM methods. Since HTML defines the content
> of TITLE as PCDATA, the title should be able to have text nodes and
> change their node values.
>
> However, AFAICS, the specification does not state that the [normalized]
> text nodes inside the title should be considered as the title's value
>
> While IE has therefore decided to not create a text node, Mozilla and
> Opera have however made the decision to have a text node for the title
> value; in this regard, since changing the node's value does nothing, it
> could probably be considered as a "bug" in those browsers, but certainly
> not in regards of the reference.
>
> Apart from altering document.title, there's another standard way to
> change the title, though probably less supported: change the text
> property of the TITLE element.
>
>
<URL:http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/html.html#ID-79243169>

>



--
Rob

Thanks a lot for your help Rob.

However, I`ve deicded to use a premade html file as the modeless window
source instead of
a dynamicly created one. Saves me more trouble with this title thing...

(I`m able to set the title on the dynamicly created modeless, but it just
doesnt show up
in the title bar. And I dont know how to 'sneak' in the title via the
showModelessDialog method).

Thanks for the effort !

Oeyvind

--
http://home.online.no/~oeyvtoft/ToftWeb/

RobG <> wrote in message news:<41b2587d$0$25785$>...

> Needless to say, showModelessDialog is a Microsoft invention that is
> not well supported in other browsers (if at all).

It should be, though. Dialog boxes have been on computer screens for
twenty years!

FURTHERMORE: Modeless dialogs can be faked with a new window, but a
modeless dialog can not, except for 'confirm()', 'alert()' and
input(). The programmer can not create a general modeless dialog
except for MS browsers. When you need a modeless dialog, you
reall do NEED one.

ALL browsers should support modeless dialogs!

DAMN IT, why don't I proofread my posts?!?!?!?!?

I wrote 'modeless' when I meant 'modal'. This is what I MEANT
to say...


RobG <> wrote in message news:<41b2587d$0$25785$>...

> Needless to say, showModelessDialog is a Microsoft invention that is
> not well supported in other browsers (if at all).

It should be, though. Dialog boxes have been on computer screens for
twenty years!

FURTHERMORE: Modeless dialogs can be faked with a new window, but a
***modal*** dialog can not, except for 'confirm()', 'alert()' and
input(). The programmer can not create a general ***modal*** dialog
except for MS browsers. When you need a ***modal*** dialog, you
reall do NEED one.

ALL browsers should support ***modal*** dialogs!

Razzbar wrote:
[...]
> It should be, though. Dialog boxes have been on computer screens for
> twenty years!

Hmmm, that's a matter of philosophy. A browser is very different from
a standard application platform. Your content is being hosted in
someone else's application, so you should play by their rules. If you
want full control of the UI, write a standard application in C++ or
Java or whatever. Or write your own browser that does provide modeless
dialogs and ask users to only use your browser on your site.

> FURTHERMORE: Modeless dialogs can be faked with a new window, but a
> modeless dialog can not...

Errr, not quite sure what you mean.

> except for 'confirm()', 'alert()' and
> input().

But some sites still try to use confirm and prompt dialogs to get you to
click on the few modeless dialogs that are allowed.

> The programmer can not create a general modeless dialog
> except for MS browsers. When you need a modeless dialog, you
> reall do NEED one.

It's quite easy to program around modeless dialogs - just accept that
the user is in control. I have yet to find a situation where it was
*impossible* to design around a "required" modeless dialog.

>
> ALL browsers should support modeless dialogs!

I disagree.

--
Rob

Razzbar wrote:
> DAMN IT, why don't I proofread my posts?!?!?!?!?
>
> I wrote 'modeless' when I meant 'modal'. This is what I MEANT
> to say...
>
>
> RobG <> wrote in message news:<41b2587d$0$25785$>...
>
>
>> Needless to say, showModelessDialog is a Microsoft invention that is
>> not well supported in other browsers (if at all).
>
>
> It should be, though. Dialog boxes have been on computer screens for
> twenty years!

So have non-modal dialog boxes. Whats your point?

> FURTHERMORE: Modeless dialogs can be faked with a new window, but a
> ***modal*** dialog can not, except for 'confirm()', 'alert()' and
> input(). The programmer can not create a general ***modal*** dialog
> except for MS browsers. When you need a ***modal*** dialog, you
> reall do NEED one.

Example? And if you think you need that much control, write your own App
and stop trying to do it in a web browser.

> ALL browsers should support ***modal*** dialogs!

Why?

And, how do you suppose a modal dialog should work in tabbed browsers?

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq

RobG wrote:

> Errr, not quite sure what you mean.

That's because I was sloppy with terms. Please ignore the
post. I clarified in a later post.