User Profile & Activity

Questica Support Member
Page
of 13
Posted: September 16, 2011 8:52 AM

Hi Handy,

Please take a closer look at  the sample I just posted.  It uses javascript to calculate the correct height and uses SetHeight() followed by wgDoResize.  The sample and movie I provided are the result of your suggested workaround.  Is there a way to get it working in IE9?

Posted: September 15, 2011 9:43 AM

Hi Handy,

There is an additional issue.  Our problem is not what you and Karl are describing.

I undertand the different rules that apply in the different rendering modes.  I am fine with the fact that the AutoHeight/AutoWidth features only work in quirks mode, and I don't mind using javascript or any other reasonable approach to get the equivalent behaviour in another doctype.  What's more, we have been able to get the WebGrid to resize with the page just the way we want through the use of javascript, months ago.

The issue is that in IE9 only the grid frame and the grid width resize correctly - the WebGrid's inner contents do not resize to the new height (other major browsers work correctly with the same page.)  So we can get the perimeter of the webgrid to correctly expand/contract when the browser window size changes, and the columns expand or contract to fill the available horizontal space, but the grid does not display any more or less rows of data, only empty space when the window gets taller, or cutting off the status bar and visible data when the window gets shorter.  Calling wgDoResize does not fix this issue.  This is the bug we thought you acknowledged above, but it sounds like we have been miscommunicating.  

I've prepared another sample, and a video, that uses the suggestions from your and Karl.  The Quirks page with  AutoHeight enabled demonstrates the desired behaviour.  The XHTML page using your javascript solution resizes in exactly the right way by using SetHeight() and wgDoResize() but the grid's inner contents don't resize with it in IE9.  Hitting the "Refresh" button in the grid footer causes the grid's inner contents to size correctly.

The video demonstrates the XHTML/Javascript resizing working correctly in Firefox and Chrome, then demonstrates the desired behaviour by showing the quirks mode page in IE9, then finally shows the XHTML/javascript resizing issue in IE9.

Hopefully this latest post will make things clear.  Thanks for continuing to work with us on this issue.

Edit: the video attachment doesn't seem to be working.  Here it is on YouTube.

 

Posted: September 15, 2011 9:33 AM

Karl,

Thanks for taking the first shot at our challenge!  I edited the sample to use your syncHeight method but it causes the browser to crash immediately in IE9, Chrome and Firefox.

Posted: September 14, 2011 9:56 AM

Handy,

You seem to keep forgetting the issue.  We've had to re-prove to you over and over for the last four months that the behaviour is a bug.  I thought we were way past this. Does this mean you will not be giving us a date that this issue will be resolved?

Please re-check our posting above from June 22, 2011 at 4:04 PM.  We painstakingly built a visual studio project with a working (IE Quirks) page and a broken page.  Your suggestion will not cause WebGrid to behave as it does in the working page from that sample.

This is not an XHTML limitation.  The function does not work in HTML Strict mode either.  It only works in IE Quirks mode.

I can't believe we've gone backwards again.  You already agreed on July 27th that the height resizing is a real issue.  On August 9th you said you will surely fix it.  You said you would try and push your developer team to come up with a fix, possibly by our September 21st deadline.  We told our managers that.

I've prepared yet another sample which is attached.  This one contains three pages:  WorkingPage.aspx demonstrates the behaviour working correctly in IE Quirks Mode.  BrokenPageXhtml.aspx shows the bug with the XHTML doctype.  BrokenPageHtmlStrict shows the bug with the HTML Strict doctype.

Please respond and tell me that you remember now that this is a real issue and whether you could possibly fix it by our September 21st deadline.

Posted: September 6, 2011 9:56 AM

Handy,

Our original deadline for this work has already passed. However, we've been able to keep this development open in hopes that you would have a solution for us. The last possible day that we will be able to use a fix is September 21, 2011.

If you can have something for us by September 21, 2011, we would greatly appreciate it.

Thanks.

Posted: September 1, 2011 10:34 AM

Tomislav,

Thanks for your response. Unfortunately your solution, like the others we have tried, only expand the frame of the WebGrid, not the content.

For example, assume there are 15 rows visible in the grid with the screen at its original height.

In quirks mode, as you expand the height of the window, the WebGrid will expand to show more than 15 rows. It will continue expanding with the screen, revealing more rows as it expands.

In XHTML and HTML Strict mode, the frame of the WebGrid expands with the height of the screen, but the content section does not. In other words, as you expand the screen, it will continue to show just 15 rows of data, but the beige WebGrid frame will expand with the screen.

We're waiting on Intersoft to provide an estimated date for a fix to this issue.

Posted: August 31, 2011 2:35 PM

Karl,

I appreciate you taking the time to write out all your thoughts.  Unfortunately we can't get the grid to function correctly in HTML Strict Mode either (quirks mode is not an option.)  And the solution you proposed using wgDoResize in XHTML mode didn't work either.  We have tried abolutely everything, hence this lengthy thread and our continued frustration.  Intersoft has agreed that there is a bug in the software and committed to fixing it, but they haven't given us a date yet.

Posted: August 30, 2011 10:18 AM

Handy,

I'm afraid my patience has finally run out. I have been trying to get a resolution on this issue since May 25th (over 3 months ago)! It seems we have finally agreed on what the issue is, and you have committed to fixing this issue. However, it has been 3 weeks since you committed to fixing the issue, and you have been unable to give me a timeline for when I can expect a resolution. This is very frustrating, and unacceptable.

I have been very reasonable and understanding up to this point, but my development team cannot accept any more delays in our schedule. Within the next few days you must provide me with a timeline of when I can expect this issue to be delayed (even a rough timeline).

Once again, I do not need the solution within the next few days, but I need an idea of how long I will have to wait for a solution.

Thanks.

Posted: August 23, 2011 4:11 PM

Handy,

I am still looking for an update as to when we can expect a fix for this issue. Please investigate and let me know when this issue will be resolved.

Thanks.

Posted: August 16, 2011 1:44 PM

Handy,

It has been a week since your last update. Do you have a better idea of when we can expect a fix for this issue?

Thanks.

All times are GMT -5. The time now is 12:04 PM.
Previous Next