Browser problem or dotnet bug?

  • Thread starter Thread starter ChrisC
  • Start date Start date
C

ChrisC

I have an aspx page with a couple of controls on it and also an iframe
within it. When one of the dotnet buttons is clicked I navigate the
iframe to a different location by using the src attribute.

The problem I am experiencing is this - in windows 2000 using IE (fully
patched) when the iframe is navigated the page seems to break - it
doesnt register it as a postback and any further usage of the controls
on the form doesnt register as a postback. The page and its controls
work fine up until the point when the iframe is first navigated.

In windows XP this doesnt happen, nor in windows 2000 using firefox.

Ive been looking at this on and off for a week now and I cant find any
information on it other than the fact that MS are not able to provide
the most recent IE updates on 2000 because of the amount of work
required in reengineering the code.
 
Have I run into the typical 'its not a trivial problem to fix so noone
answer' situation?
 
What if you try a bare bone page that uses the same principle ? Does it have
the same problem ?

What if you look at the HTML code ? My understanding is that the controls
are not submitted any more ? Could it be a problem with the HTML code ?

Patrice
 
Yup, tried a barebones page - although really my production page isnt
much more than that - just a few dropdownlists with AutoPostBack
events.

The html isnt giving me any useful information unfortunately -
everything appears as i would expect it to, just on this one os/browser
combination it doesnt work.
 
I don't think I've got a Windows 2000 where I could test this...

What is the role of the IFRAME in the whole schema ? Does it just change the
source but doesn't affect in any way the container page ? Or does it have
controls on its own ? (I don't even know how it works in this case).

My understanding is that the postback doesn't happen anymore. If it happened
before, it's likely that something changed in between ;-) - for example a
scripting issue between those two frames...

As a side note and depending upon what you are trying to do a usercontrol
could be a best fit (or a workaround)...

Good luck... (IMO a bare bone sample would be needed in case someone with
Windows 2000 woudl want to repro this).

Patrice
 
The page goal is as follows - in the top half of the page we have a
couple of drop downs for the user to select criteria for report
generation and a button to generate the report with the selected
criteria. The iframe is used to display the generated Reporting
Services report output.

On the affected systems, after the report has been generated doing
things which would cause the page to postback ie changing selection on
some of the drop downs causes postback, the page still posts back but
it enters the if(!IsPostback) code. Ill get braebones stuff sorted out..
 
Back
Top