Rank: Member
Groups: Member
Joined: 6/21/2007
Posts: 12
|
In the process of doing some cross browser testing, I noticed the following issues when using the beta version of Safari for Windows (Version 3.03)...
1)I have a GridView in a CallbackPanel and I trigger the callback event on a sort of the GridView. Safari does a htmlHttpRequest rather than a XMLHttpRequest for some reason. FireFox and IE behave as expected.
2)When the issue noted above occurs, for some strange reason the ViewState of the MultiView.SelectedIndex is not include in the ViewState information sent to the server. All other ViewState information is sent (as far as I can tell). Not sure if this is a general ViewState issue outside of the callback problem. Note that on IE and Firefox the ViewState for MultiView.SelectedIndex is perserved as expected.
3)On IE and FireFox the current selected TabStrip menu item retains state across postbacks even if the controls EnableViewState property is set to False (This confused me, but accepted it as a given in my coding). To my dismay, on Safari this doesn't hold true and EnableViewState must be set to true for TabStrip Menus to work on Safari.
I was able to work around all of these issues, but I thought you might want to be aware of them in case they are issues with your controls rather than Safari.
Jim
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi Jim,
Thanks for the information. We did test our controls on Safari 1.1 and 2.0 and they works fine. Our code explicitly uses XmlHttpRequest on both Safari 1.1 and 2.0 and I am not sure how it turned into HtmlHttpRequest on Safari 3.0. We will look into it and see what we can find.
Problem #2 and problem #3 seems to be related to problem #1. We will see what we can find on #1 and then look into those.
Thanks for sharing!
|