Problem calling a NetWebBrowse if not yet logged in

[Nick]

I click on a menu-item that calls a popup NetWebBrowse.
The user must be logged in for that NetWebBrowse but I'm NOT logged in yet.
So I log in and get: (allways)

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<ajax-response>
<response type="element" id="loginform_div">
<div id="loginform_div" class=" nt-fix-center nt-width-300px">
<div id="loginform_alert_div" class="nt-width-99 alert ui-state-error ui-corner-all nt-hidden"/>
<form action="IndexPage" method="post" name="LoginForm_frm" id="LoginForm_frm" target="_self" onsubmit="osf(this);">
<input type="hidden" name="FormState" id="FormState" value="XDBOVREGJF"/>
<input type="hidden" name="hash" value="1111650215"/>
<div id="tab_loginform_div" class="nt-tab-outer">
<div id="tab_loginform0_div" class="nt-tab-inner nt-rounded">
<div class="ui-state-default nt-rounded-header ui-corner-all">Inloggen</div>
<table class="nt-form-table" width="300">
<tr>
<td>
etc, etc.

I know I can force login for the menu-item as well but then that menu-item is not visible anymore
until logged in and I would like it to be visible all times.

Is this a bug?

Nick

[Nick]

Probably obvious but: if I don't try to click on this menu-item before I'm logged in logging in goes fine.
Nick

[Bruce]

Hi Nick,

as you might imagine things are really busy here right now. So anything you can do to help me duplicate the effect would be appreciated. (which is a polite way of saying, post a small example and I'll take a look.)

cheers
Bruce

[Nick]

Hi Bruce,

I understand. I will see if I can make a small example.

Cheers,
Nick

[Nick]

Hi Bruce,

See attached. Just a bit modified web3 app.
You can easily test it with your web3 app too.
Just add an item to one of the menus (I choose "Home") and call a popup netwebbrowse.
Don't set the must-be-login box in the menu-item but set it on the netwebbrowse itself.
Before login click on the menu-item. It doesn't do anything of course but when you login you see the problem.

Cheers,
Nick

[attachment deleted by admin]

[Bruce]

your problem is that the browse is a popup, and the login is a popup, and when you choose the Browse option (from the menu) it tries to open the login form. Alas that particular combination - where the login is a popup and the browse is  a popup is not currently supported.

Your best option is to set the menu item as "requires login" as well, that way the user can't go down this route.

cheers
Bruce