You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(96) |
Dec
(59) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(227) |
Feb
(138) |
Mar
(103) |
Apr
(126) |
May
(93) |
Jun
(54) |
Jul
(61) |
Aug
(65) |
Sep
(63) |
Oct
(56) |
Nov
(87) |
Dec
(31) |
2007 |
Jan
(37) |
Feb
(43) |
Mar
(85) |
Apr
(17) |
May
(8) |
Jun
(15) |
Jul
(1) |
Aug
(10) |
Sep
(44) |
Oct
(9) |
Nov
(8) |
Dec
(8) |
2008 |
Jan
(9) |
Feb
(3) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
|
Mar
(5) |
Apr
|
May
(1) |
Jun
(5) |
Jul
(4) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
2010 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(15) |
Jul
(3) |
Aug
(4) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(1) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: SourceForge.net <no...@so...> - 2009-06-06 09:10:19
|
Bugs item #2716658, was opened at 2009-03-27 10:03 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2716658&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Compatibility with ie8 Initial Comment: In order to make Anthem.net working with IE8 and with an <anthem:Timer>, the aspx page must have an <asp:button> and an <asp:CustomValidator> ! An other way is to add the following line after the <form> balise: <input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="" /> Bug javascript at the line: form[name] = input; //with name = "__EVENTTARGET" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-06 09:10 Message: function Anthem_SetHiddenInputValue(form, name, value) { var input = null; if (form[name]) { input = form[name]; } else { input = document.createElement("input"); input.setAttribute("name", name); input.setAttribute("type", "hidden"); } input.setAttribute("value", value); var parentElement = input.parentElement ? input.parentElement : input.parentNode; if (parentElement == null) { form.appendChild(input); form[name] = input; ///////////////////////////////////error occurs here for image button: Object doesn't support this property or method } } ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-06 08:42 Message: This error occurs on image button too in IE8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2716658&group_id=151897 |
From: SourceForge.net <no...@so...> - 2009-06-06 08:42:38
|
Bugs item #2716658, was opened at 2009-03-27 10:03 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2716658&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Compatibility with ie8 Initial Comment: In order to make Anthem.net working with IE8 and with an <anthem:Timer>, the aspx page must have an <asp:button> and an <asp:CustomValidator> ! An other way is to add the following line after the <form> balise: <input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="" /> Bug javascript at the line: form[name] = input; //with name = "__EVENTTARGET" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-06 08:42 Message: This error occurs on image button too in IE8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2716658&group_id=151897 |
From: SourceForge.net <no...@so...> - 2009-05-22 09:25:34
|
Feature Requests item #2795279, was opened at 2009-05-22 09:25 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782467&aid=2795279&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Jquery Compliant Initial Comment: Make Anthem Jquery compliant. This might also reduce alot of browser issues!! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782467&aid=2795279&group_id=151897 |
From: SourceForge.net <no...@so...> - 2009-03-30 18:27:45
|
Patches item #2722312, was opened at 2009-03-30 18:27 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=2722312&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Changed fileupload behavior to work more reliably in Safari Initial Comment: The file upload behavior has been changed to work more reliably in Safari. Previously, when you upload and it uses the IFrame to submit the form, the onload event of the iframe was firing before the response was returned from the server. Now, it uses an interval to check the response from the form every 500ms for a period no greater than 60seconds before determining that the form submit was completed. Not the most elegant solution, but works better than previously. Mustafa Shabib mus...@we... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=2722312&group_id=151897 |
From: SourceForge.net <no...@so...> - 2009-03-27 10:03:43
|
Bugs item #2716658, was opened at 2009-03-27 10:03 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2716658&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Compatibility with ie8 Initial Comment: In order to make Anthem.net working with IE8 and with an <anthem:Timer>, the aspx page must have an <asp:button> and an <asp:CustomValidator> ! An other way is to add the following line after the <form> balise: <input type="hidden" name="__EVENTTARGET" id="__EVENTTARGET" value="" /> Bug javascript at the line: form[name] = input; //with name = "__EVENTTARGET" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2716658&group_id=151897 |
From: Andy M. <af...@us...> - 2009-03-04 08:04:24
|
Update of /cvsroot/anthem-dot-net/anthem/Anthem In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv32729/Anthem Modified Files: Anthem.js Log Message: Minor changes. Index: Anthem.js =================================================================== RCS file: /cvsroot/anthem-dot-net/anthem/Anthem/Anthem.js,v retrieving revision 1.61 retrieving revision 1.62 diff -u -d -r1.61 -r1.62 --- Anthem.js 4 Mar 2009 07:38:05 -0000 1.61 +++ Anthem.js 4 Mar 2009 07:46:08 -0000 1.62 @@ -447,7 +447,7 @@ var control = document.getElementById(containerID); if (control) { control.innerHTML = result.controls[controlID]; - if (result.controls[controlID] == "") { + if (control.innerHTML == "") { control.style.display = "none"; } else { control.style.display = ""; @@ -754,7 +754,7 @@ preProcessOut ); if (preProcessResult) { - var eventType = e.type; + var eventType = e ? e.type : null; Anthem_FireEvent( eventTarget, eventArgument, @@ -777,6 +777,7 @@ updatePageAfterCallBack ); } + return false; } function AnthemListControl_OnClick( |
From: Andy M. <af...@us...> - 2009-03-04 07:40:02
|
Update of /cvsroot/anthem-dot-net/anthem/Anthem In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv32381/Anthem Modified Files: Manager.cs Log Message: Removed code that loaded Anthem.js in .NET 2.0 when the DEBUG symbol was defined. This just confuses people to no end. Index: Manager.cs =================================================================== RCS file: /cvsroot/anthem-dot-net/anthem/Anthem/Manager.cs,v retrieving revision 1.73 retrieving revision 1.74 diff -u -d -r1.73 -r1.74 --- Manager.cs 30 Jul 2007 17:55:47 -0000 1.73 +++ Manager.cs 4 Mar 2009 07:39:12 -0000 1.74 @@ -16,10 +16,8 @@ #if V2 using System.Web.Configuration; -#if !DEBUG [assembly: WebResource("Anthem.Anthem.js", "text/javascript")] #endif -#endif namespace Anthem { @@ -2082,18 +2080,7 @@ #endif #if V2 -#if DEBUG - Stream stream = typeof(Anthem.Manager).Assembly.GetManifestResourceStream("Anthem.Anthem.js"); - StreamReader sr = new StreamReader(stream); - page.ClientScript.RegisterClientScriptBlock(this.GetType(), "Anthem.js", - @"<script type=""text/javascript""> -//<![CDATA[ -" + sr.ReadToEnd() + @" -//]]> -</script>"); -#else page.ClientScript.RegisterClientScriptResource(typeof(Anthem.Manager), "Anthem.Anthem.js"); -#endif #else string baseUri = ConfigurationSettings.AppSettings["Anthem.BaseUri"]; if (baseUri != null && baseUri.Length > 0) |
From: Andy M. <af...@us...> - 2009-03-04 07:38:54
|
Update of /cvsroot/anthem-dot-net/anthem/Anthem In directory 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv32334/Anthem Modified Files: Anthem.js Log Message: Fixed Anthem_SetHiddenInputValue and Anthem_RemoveHiddenInput to be compatible with IE8. Index: Anthem.js =================================================================== RCS file: /cvsroot/anthem-dot-net/anthem/Anthem/Anthem.js,v retrieving revision 1.60 retrieving revision 1.61 diff -u -d -r1.60 -r1.61 --- Anthem.js 18 Sep 2007 15:56:57 -0000 1.60 +++ Anthem.js 4 Mar 2009 07:38:05 -0000 1.61 @@ -1,5 +1,5 @@ // Anthem.js -// Updated Sep 18, 2007 +// Updated Mar 3, 2009 // Anthem.Manager.GetScripts: false function Anthem_Encode(s){ @@ -404,7 +404,8 @@ var parentElement = input.parentElement ? input.parentElement : input.parentNode; if (parentElement == null) { form.appendChild(input); - form[name] = input; + //IE7 + try { form[name] = input; } catch (e) { } } } @@ -413,7 +414,8 @@ if (input != null && typeof(input) != "undefined") { var parentElement = input.parentElement ? input.parentElement : input.parentNode; if (parentElement != null) { - form[name] = null; + //IE7 + try { form[name] = null; } catch (e) { } parentElement.removeChild(input); } } |
From: SourceForge.net <no...@so...> - 2009-01-09 19:19:54
|
Feature Requests item #2496316, was opened at 2009-01-09 14:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782467&aid=2496316&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Stephen Holsinger (sholsinger) Assigned to: Nobody/Anonymous (nobody) Summary: Compress (Minify) Anthem.js Initial Comment: Compressing Anthem.js will be beneficial to everyone who uses anthem. It may cause some issues with developers/maintainers as they'd have to switch between minified and un-minified code when building a final release, but it is well worth the effort in the end when you can say that Anthem.js is 15 Kib vs 32 Kib. (Dojo ShrinkSafe) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782467&aid=2496316&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-09-29 13:17:41
|
Bugs item #2135999, was opened at 2008-09-29 13:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2135999&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Updating controls with Fileuploads Initial Comment: I am using the fileupload control which once an image is upload then updates a repeater to show the new image along with any existing images. As part of the repeater is a anthem:button with the following Command attributes: CommandArgument='<%# DataBinder.Eval(Container.DataItem, "FullImage") %>' CommandName="removeimage" This used to work fine in .Net 1.1 but I have now upgraded the project to .Net 2.0 and the WebForm_DoPostBackWithOptions code generated by .Net 2.0 causes problems with Anthem when using the IOFrame for the file upload. Basically the WebForm_DoPostBackWithOptions code looks like this as the reponseText in the Anthem.js onclick=\"javascript:Anthem_FireCallBackEvent(this,event,'vehicleImages$currentImages$ctl01$test','',true,'','','',true,null,null,null,true,true);return false;WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("vehicleImages$currentImages$ctl01$test", "", true, "", "", false, false))\" Notice the lack of backslashes in the function. Ideally the double quotes should be replaced with single quotes. To add to this the server side version of this response looks like this onclick=\\\"javascript:Anthem_FireCallBackEvent(this,event,'vehicleImages$currentImages$ctl01$removeImage','',true,'','','',true,null,nu ll,null,true,true);return false;WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("vehicleImages$currentImages$ctl01$removeImage", "", true, "", "", false, false))\\\" So I'd recommend that within the Anthem.Manager class a replace such as: response = response.Replace("quot;", "'"); be added to the IOFrame response. (Line 2171). My email address is jo...@wh... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=2135999&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-06-16 21:46:16
|
Bugs item #1795794, was opened at 2007-09-16 07:57 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1795794&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: CyberHawk (graemew_) Assigned to: Andy Miller (afm_44) Summary: Callback to wrong page when using Moodalbox or Lightbox Initial Comment: If you have a page with Anthem controls and they are loaded into a moodalbox or lightbox, the callbacks are sent to the page that opened the box, rather than to the page where the callback originated. Form is set to be the page that was loaded into the box. The rel attribute is also set, yet the callback still does not get executed by the correct page ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-06-16 14:46 Message: Logged In: NO dghdfghdf ---------------------------------------------------------------------- Comment By: CyberHawk (graemew_) Date: 2007-09-19 10:31 Message: Logged In: YES user_id=1891639 Originator: YES I tried your suggestion and it works perfectly. Thanks again for taking the time to look into this issue :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-09-19 09:33 Message: Logged In: YES user_id=1245761 Originator: NO As I look at this problem, I see more an more code that must be changed, often in a way that makes it more complicated. To add support for multiple forms "the right way" would lead to some breaking changes. To work around the problem in your particular case, I think you can try this: 1. Add an Anthem control to the main page (i.e. Default.aspx) to make sure the Anthem.js script is added to page. 2. Give the form in Popup.aspx a unique form id (it should probably have a unique id anyway). 3. Modify moodalbox.js so that when a popup is added to the page, it sets Anthem_FormID = the popup form id. 4. Also modify moodalbox.js so that when the popup is closed, it resets Anthem_FormID = the original form id. I'll add a feature request to SourceForge to add multiple form support into Anthem so we don't forget. ---------------------------------------------------------------------- Comment By: CyberHawk (graemew_) Date: 2007-09-18 15:32 Message: Logged In: YES user_id=1891639 Originator: YES Thanks for taking a look at this. I'll have a look as well and see what I can come up with now I know whats causing the issue. ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-09-18 14:40 Message: Logged In: YES user_id=1245761 Originator: NO Moodalbox (and Lightbox I suspect) add the popup as a second form to the page. As you probably know, ASP.NET is pretty much designed from the ground up to have one form on each page. And Anthem.NET was written using the same assumption. So, for example, the callback URL is extracted from the first (and presumably only) form action property...which is why your event handler in PopUp.aspx is not called. If retrieving the correct callback URL was the only issue, this would be pretty easy to solve. But Anthem.js makes the assumption that there is only one form throughout the code. It is going to be very tedious to update the code in Anthem.js to handle multiple forms. I'll take a more careful look over the next few days to see if I can do it without breaking the existing code...but I can not promise anything. If you have already made the changes, or are willing to make the changes to Anthem.js, please let me know. ---------------------------------------------------------------------- Comment By: CyberHawk (graemew_) Date: 2007-09-18 13:03 Message: Logged In: YES user_id=1891639 Originator: YES I have attached a test script that include the moodalbox. There is a link on the Default.aspx page which will load popup.aspx into the moodalbox. If you run the popup.aspx on its own, you will see that the callback works fine. Loaded in the modalbox, nothing happens. Thanks for looking into this issue :) File Added: moodalbox_test.zip ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-09-18 08:49 Message: Logged In: YES user_id=1245761 Originator: NO Please attach a sample page that demonstrates the problem. If possible, the page should load lightbox or moodalbox javascript from an existing server so that I do not need to install lightbox or moodalbox on my computer. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1795794&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-04-08 01:21:49
|
Bugs item #1770076, was opened at 2007-08-08 07:33 Message generated for change (Comment added) made by nbarger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1770076&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Fofr (fofr) Assigned to: Nobody/Anonymous (nobody) Summary: asp:FileUpload disables anthem features on whole site Initial Comment: when you use asp:FileUpload OR anthem:FileUpload and user click on the browse button and select some file, i will compleatly disable anthem features on the whole site. Tested on IE7 and FF 2.+. I am using Anthem 1.5.1 Same behaviour you can see in your samples of FileUpload ---------------------------------------------------------------------- Comment By: Nathan (nbarger) Date: 2008-04-07 18:20 Message: Logged In: YES user_id=2034831 Originator: NO I can confirm that it actually won't let you do any callbacks after you upload a file as well. I have some custom callbacks that it breaks ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-09-18 08:09 Message: Logged In: YES user_id=1245761 Originator: NO Please attach a self-contained sample page that demonstrates the problem. "So something is not working well. Just like i said, that same behaviour like i described you can see in 2005 examples -> FileUpload (when you select some file, and than you click on + button to show another fileDialog, there will be postback instead od callback...)" There are 2 ways to make a "callback"; using XmlHttpRequest and using an IFRAME postback. They are both "callbacks". Only the IFRAME postback method supports the <file> tag. So that is the method we use. If you can find a way to use XmlHttpRequest, please post the working solution as a patch. ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-08-08 12:24 Message: Logged In: YES user_id=1245761 Originator: NO Please attach a simple, self-contained page that demonstrates the problem. I should be able to save the page to an existing web site, load it in a browser, and be able to duplicate the problem. ---------------------------------------------------------------------- Comment By: Fofr (fofr) Date: 2007-08-08 12:01 Message: Logged In: YES user_id=1863241 Originator: YES But there is still problem if you are using textarea on the same page with FileUpload. It generates this html to my textareas: <tr><td></anthemarea> and a lot of white space ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-08-08 11:16 Message: Logged In: YES user_id=1245761 Originator: NO It's true that when a FileUpload control in on the page, all of the Anthem controls will use an IFRAME postback instead of XmlHttpRequest to make the "callback". This is required for FileUpload (and it is how all* Ajax libraries handle the <file> element). Note that even when the IFRAME postback technique is used, there is only a partial page update, just like the XmlHttpRequest technique. I don't see what you mean by "i will compleatly diable anthem features on the whole site". The link below is to a very large site with Anthem features on nearly every page. All of the pages work exactly as expected before and after using the FileUpload example, http://anthem.talloaksoftware.com/ * As far as I know. ---------------------------------------------------------------------- Comment By: Fofr (fofr) Date: 2007-08-08 10:04 Message: Logged In: YES user_id=1863241 Originator: YES This bug was reported here: http://sourceforge.net/tracker/index.php?func=detail&aid=1691075&group_id=151897&atid=782464 , but i check that fix and this fix is added in 1.5.1 but it is still not working. It puts some strange html in my textearea, that html looks like this: <tr><td></anthemarea> and a lot of white space... So something is not working well. Just like i said, that same behaviour like i described you can see in 2005 examples -> FileUpload (when you select some file, and than you click on + button to show another fileDialog, there will be postback instead od callback...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1770076&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-03-26 21:17:57
|
Bugs item #1926545, was opened at 2008-03-26 14:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1926545&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: One parameter only in invoking page method Initial Comment: I tried to follow the code in anthem.js and it checks if it is an array. I am converting this code over from asp .net ajax, I can print both values correctly on an alert. I tried doing it the way in the example also: [selectedID.value,f.elements["color"].value] I get the first parameter but not the second. The array is of length 1. var A = new Array ( 2 ); A[0] = selectedID.value; A[1] = f.elements["color"].value; if ( A instanceof Array ) { alert("ARRAY"); } Anthem_InvokePageMethod( 'SetColor', A, function (result) {} ); ( in my page ) [Anthem.Method] public void SetColor(string [] par) { const int CONTROL_ID = 0; const int COLOR = 1; // GETS HERE if (par.Length > 1) { // never gets here } } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1926545&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-03-21 15:21:38
|
Patches item #1847594, was opened at 2007-12-09 17:47 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for IE6 and hidden panels Initial Comment: I had trouble with IE6 (and below) applying line-height to an anthem:Panel with Visible="false". Anthem renders this for a hidden panel: <div id="controlId"></div> http://lists.evolt.org/archive/Week-of-Mon-20070416/189398.html suggests that the following stops the problem: <div id="controlId"><!-- --></div> To implement, add the following at line 52 of Panel.cs: else { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-21 08:21 Message: Logged In: NO If a I have a non Anthem control inside does not render it ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-21 08:21 Message: Logged In: NO If a I have a non Anthem control inside odes not render it ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-02-10 14:56 Message: Logged In: NO afm_44, I'd recommend that, yes. It sounds like you and psiegers have grander plans for the markup of hidden controls, but adding that empty comment fixed all my rendering problems. Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-28 23:38 Message: Logged In: YES user_id=1245761 Originator: NO Are you recommending this for all Anthem controls that render a <div> wrapper? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-28 21:54 Message: Logged In: NO Hi psiegers. The code has fixed the rendering bug in the following browsers: - Internet Explorer 6 - Internet Explorer 5.5 The code has been used in the following browsers with no ill effects: - Firefox 2.0 - Opera 9 - Internet Explorer 7 - Safari 3 All browsers are running on Windows XP SP 2 Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2008-01-17 08:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi Gavin, did you test this code only in IE6 or also in other browsers? PD: I'm talking about the following code (added to Panel.cs starting from line 52): else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2007-12-31 09:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi all, I agree with Manu, and think that adding a css class id is a good idea. ---------------------------------------------------------------------- Comment By: TweeZz (tweezz) Date: 2007-12-09 23:13 Message: Logged In: YES user_id=1472130 Originator: NO Hi Andy, I think the second solution you suggested is somehow 'safer'. At least for the applications I wrote using Anthem. I'm a heavy prototype user. In some cases I retrieve elements using css selectors. Sometimes a part of the selector includes the wrapper 'div'. Changing it into a 'span' would break code, maybe not only in my applications. Maybe I'm being to selfish here :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-12-09 19:38 Message: Logged In: YES user_id=1245761 Originator: NO Great tip! I suppose this applies to all of the Anthem controls that wrap the native control inside of a <div>. Since the type of element that is used does not matter to Anthem, perhaps we should always use an inline control when the native control is not visible (i.e. use <span></span> when Visible=false, and <div></div> otherwise). Or we could assign a class to the wrapper element such as <div class="anthem"> wrapped HTML </div> <div class="anthem hidden"></div> Then you could modify your stylesheet to do anything you want with Anthem controls. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-12-09 18:23 Message: Logged In: NO Correction. Code should be: else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Gavin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-03-21 15:21:20
|
Patches item #1847594, was opened at 2007-12-09 17:47 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for IE6 and hidden panels Initial Comment: I had trouble with IE6 (and below) applying line-height to an anthem:Panel with Visible="false". Anthem renders this for a hidden panel: <div id="controlId"></div> http://lists.evolt.org/archive/Week-of-Mon-20070416/189398.html suggests that the following stops the problem: <div id="controlId"><!-- --></div> To implement, add the following at line 52 of Panel.cs: else { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-21 08:21 Message: Logged In: NO If a I have a non Anthem control inside odes not render it ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-02-10 14:56 Message: Logged In: NO afm_44, I'd recommend that, yes. It sounds like you and psiegers have grander plans for the markup of hidden controls, but adding that empty comment fixed all my rendering problems. Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-28 23:38 Message: Logged In: YES user_id=1245761 Originator: NO Are you recommending this for all Anthem controls that render a <div> wrapper? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-28 21:54 Message: Logged In: NO Hi psiegers. The code has fixed the rendering bug in the following browsers: - Internet Explorer 6 - Internet Explorer 5.5 The code has been used in the following browsers with no ill effects: - Firefox 2.0 - Opera 9 - Internet Explorer 7 - Safari 3 All browsers are running on Windows XP SP 2 Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2008-01-17 08:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi Gavin, did you test this code only in IE6 or also in other browsers? PD: I'm talking about the following code (added to Panel.cs starting from line 52): else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2007-12-31 09:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi all, I agree with Manu, and think that adding a css class id is a good idea. ---------------------------------------------------------------------- Comment By: TweeZz (tweezz) Date: 2007-12-09 23:13 Message: Logged In: YES user_id=1472130 Originator: NO Hi Andy, I think the second solution you suggested is somehow 'safer'. At least for the applications I wrote using Anthem. I'm a heavy prototype user. In some cases I retrieve elements using css selectors. Sometimes a part of the selector includes the wrapper 'div'. Changing it into a 'span' would break code, maybe not only in my applications. Maybe I'm being to selfish here :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-12-09 19:38 Message: Logged In: YES user_id=1245761 Originator: NO Great tip! I suppose this applies to all of the Anthem controls that wrap the native control inside of a <div>. Since the type of element that is used does not matter to Anthem, perhaps we should always use an inline control when the native control is not visible (i.e. use <span></span> when Visible=false, and <div></div> otherwise). Or we could assign a class to the wrapper element such as <div class="anthem"> wrapped HTML </div> <div class="anthem hidden"></div> Then you could modify your stylesheet to do anything you want with Anthem controls. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-12-09 18:23 Message: Logged In: NO Correction. Code should be: else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Gavin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-02-10 23:05:31
|
Patches item #1847594, was opened at 2007-12-09 17:47 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for IE6 and hidden panels Initial Comment: I had trouble with IE6 (and below) applying line-height to an anthem:Panel with Visible="false". Anthem renders this for a hidden panel: <div id="controlId"></div> http://lists.evolt.org/archive/Week-of-Mon-20070416/189398.html suggests that the following stops the problem: <div id="controlId"><!-- --></div> To implement, add the following at line 52 of Panel.cs: else { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-02-10 14:56 Message: Logged In: NO afm_44, I'd recommend that, yes. It sounds like you and psiegers have grander plans for the markup of hidden controls, but adding that empty comment fixed all my rendering problems. Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-28 23:38 Message: Logged In: YES user_id=1245761 Originator: NO Are you recommending this for all Anthem controls that render a <div> wrapper? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-28 21:54 Message: Logged In: NO Hi psiegers. The code has fixed the rendering bug in the following browsers: - Internet Explorer 6 - Internet Explorer 5.5 The code has been used in the following browsers with no ill effects: - Firefox 2.0 - Opera 9 - Internet Explorer 7 - Safari 3 All browsers are running on Windows XP SP 2 Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2008-01-17 08:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi Gavin, did you test this code only in IE6 or also in other browsers? PD: I'm talking about the following code (added to Panel.cs starting from line 52): else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2007-12-31 09:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi all, I agree with Manu, and think that adding a css class id is a good idea. ---------------------------------------------------------------------- Comment By: TweeZz (tweezz) Date: 2007-12-09 23:13 Message: Logged In: YES user_id=1472130 Originator: NO Hi Andy, I think the second solution you suggested is somehow 'safer'. At least for the applications I wrote using Anthem. I'm a heavy prototype user. In some cases I retrieve elements using css selectors. Sometimes a part of the selector includes the wrapper 'div'. Changing it into a 'span' would break code, maybe not only in my applications. Maybe I'm being to selfish here :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-12-09 19:38 Message: Logged In: YES user_id=1245761 Originator: NO Great tip! I suppose this applies to all of the Anthem controls that wrap the native control inside of a <div>. Since the type of element that is used does not matter to Anthem, perhaps we should always use an inline control when the native control is not visible (i.e. use <span></span> when Visible=false, and <div></div> otherwise). Or we could assign a class to the wrapper element such as <div class="anthem"> wrapped HTML </div> <div class="anthem hidden"></div> Then you could modify your stylesheet to do anything you want with Anthem controls. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-12-09 18:23 Message: Logged In: NO Correction. Code should be: else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Gavin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-02-09 03:20:02
|
Bugs item #1872498, was opened at 2008-01-15 19:16 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Rejected Priority: 5 Private: No Submitted By: Wayne Hartman (chabilha) Assigned to: Andy Miller (afm_44) Summary: LinkButtons Duplicate Data On a Page Initial Comment: This is very odd bug, but one I discovered. Code will appear at the bottom. I have been trying to duplicate my own paging for a repeater (I hate having everything locked inside tables with the other auto-paging controls) have created a series of LinkButtons as my pagers. What I do is create a PagedDataSource for the actual data and then another for the page indices and display values. The code then appropriately displays the correct number of pages above my code. However, whenever I click any callback or posting capable control, it duplicates the row of link buttons I have created below it. I can change pages and the bottom row does not get updated, but the top one does. So I have a top row that pages correctly and a bottom row that does not. Just to be clear, that bottom row should not even be there. I have also attempted to try using this with POAC (plain old asp controls--sorry I couldn't resist) and the problem is not reproduced. I really wanted to do this using AJAX so that my pages weren't posting back. :( I have attached the source to this bug report. I apologize if the code is a little crazy. This was a prototype to doing some nice custom paging. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2008-02-08 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-16 14:52 Message: Logged In: YES user_id=1245761 Originator: NO Your assumption is correct for the standard Repeater. It's my favorite feature of that control. However, Anthem wraps every control in a <div> or <span> (depending on whether the underlying control is typically a block element or not). The Anthem wrapper element is used to update the content after a callback. The javascript kind of looks like this: document.getElementById(anthem_wrapper_id).innerHTML = updated_HTML; ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-16 14:39 Message: Logged In: NO Very nice. I didn't think to check the markup. I always thought that the Repeater returned literal content, not enclosing it in a <div>, but that did the trick. I also, per your suggestion changed the anthem tags to asp tags inside the repeater after I saw that moving the markup to the Header and Footer tags worked. Thanks! ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-16 07:12 Message: Logged In: YES user_id=1245761 Originator: NO One thing I notice is that you have embedded the Anthem Repeater inside of HTML as a table. The resulting HTML probably looks like this: <table> <tr> <div> <td> </div> </tr> </table> Which is not valid HTML. I suspect your browser is confused by the <div> stuck in between the <tr> and the <td>. Try putting the <table><tr> in the Repeater <HeaderTemplate> and close the table in the Repeater <FooterTemplate>. The next thing I notice is that you are embedding Anthem controls (LinkButton, Label) inside of the Anthem Repeater. As far as I can tell that is unnecessary and probably inefficient (each LinkButton and Label is updated twice: once by the Repeater and once by the itself). The Anthem Repeater implements Anthem.IContainerControl which means it will "anthemize" any base controls it finds inside. Try changing the control inside the Repeater to <asp:LinkButton> and <asp:Label>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-02-05 09:01:46
|
Bugs item #1886808, was opened at 2008-02-05 00:53 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1886808&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Textareas messing response with file uploads Initial Comment: I've found a bug in Anthem.js at line 74. The problem as I see is that you change all </textarea> for </anthemarea> when rendering if you're using IOFrame to avoid these markups messing with the response frame. The problem is you missed to put the "g" (global) option in the replace RegEx when replacing back all the </anthemarea> to </textarea> again. This behavior only occurs when you're sending a file and there is more than one <textarea></textarea> pair in the response. To fix the bug just change the RegEx in the replace call with a "g" option to allow it to change all the occurrences... Line 74 - Old code: var response = { responseText: doc.getElementById("response").value.replace(/<\/anthemarea>/, "</textarea>") }; Line 74 - New code: var response = { responseText: doc.getElementById("response").value.replace(/<\/anthemarea>/g, "</textarea>") }; --------------------------------------- Joan Vilariño joa...@gm... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1886808&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-29 07:38:13
|
Patches item #1847594, was opened at 2007-12-10 01:47 Message generated for change (Comment added) made by afm_44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for IE6 and hidden panels Initial Comment: I had trouble with IE6 (and below) applying line-height to an anthem:Panel with Visible="false". Anthem renders this for a hidden panel: <div id="controlId"></div> http://lists.evolt.org/archive/Week-of-Mon-20070416/189398.html suggests that the following stops the problem: <div id="controlId"><!-- --></div> To implement, add the following at line 52 of Panel.cs: else { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Cheers, Gavin. ---------------------------------------------------------------------- >Comment By: Andy Miller (afm_44) Date: 2008-01-29 07:38 Message: Logged In: YES user_id=1245761 Originator: NO Are you recommending this for all Anthem controls that render a <div> wrapper? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-29 05:54 Message: Logged In: NO Hi psiegers. The code has fixed the rendering bug in the following browsers: - Internet Explorer 6 - Internet Explorer 5.5 The code has been used in the following browsers with no ill effects: - Firefox 2.0 - Opera 9 - Internet Explorer 7 - Safari 3 All browsers are running on Windows XP SP 2 Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2008-01-17 16:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi Gavin, did you test this code only in IE6 or also in other browsers? PD: I'm talking about the following code (added to Panel.cs starting from line 52): else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2007-12-31 17:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi all, I agree with Manu, and think that adding a css class id is a good idea. ---------------------------------------------------------------------- Comment By: TweeZz (tweezz) Date: 2007-12-10 07:13 Message: Logged In: YES user_id=1472130 Originator: NO Hi Andy, I think the second solution you suggested is somehow 'safer'. At least for the applications I wrote using Anthem. I'm a heavy prototype user. In some cases I retrieve elements using css selectors. Sometimes a part of the selector includes the wrapper 'div'. Changing it into a 'span' would break code, maybe not only in my applications. Maybe I'm being to selfish here :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-12-10 03:38 Message: Logged In: YES user_id=1245761 Originator: NO Great tip! I suppose this applies to all of the Anthem controls that wrap the native control inside of a <div>. Since the type of element that is used does not matter to Anthem, perhaps we should always use an inline control when the native control is not visible (i.e. use <span></span> when Visible=false, and <div></div> otherwise). Or we could assign a class to the wrapper element such as <div class="anthem"> wrapped HTML </div> <div class="anthem hidden"></div> Then you could modify your stylesheet to do anything you want with Anthem controls. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-12-10 02:23 Message: Logged In: NO Correction. Code should be: else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Gavin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-29 05:54:29
|
Patches item #1847594, was opened at 2007-12-09 17:47 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for IE6 and hidden panels Initial Comment: I had trouble with IE6 (and below) applying line-height to an anthem:Panel with Visible="false". Anthem renders this for a hidden panel: <div id="controlId"></div> http://lists.evolt.org/archive/Week-of-Mon-20070416/189398.html suggests that the following stops the problem: <div id="controlId"><!-- --></div> To implement, add the following at line 52 of Panel.cs: else { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-28 21:54 Message: Logged In: NO Hi psiegers. The code has fixed the rendering bug in the following browsers: - Internet Explorer 6 - Internet Explorer 5.5 The code has been used in the following browsers with no ill effects: - Firefox 2.0 - Opera 9 - Internet Explorer 7 - Safari 3 All browsers are running on Windows XP SP 2 Cheers, Gavin. ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2008-01-17 08:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi Gavin, did you test this code only in IE6 or also in other browsers? PD: I'm talking about the following code (added to Panel.cs starting from line 52): else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2007-12-31 09:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi all, I agree with Manu, and think that adding a css class id is a good idea. ---------------------------------------------------------------------- Comment By: TweeZz (tweezz) Date: 2007-12-09 23:13 Message: Logged In: YES user_id=1472130 Originator: NO Hi Andy, I think the second solution you suggested is somehow 'safer'. At least for the applications I wrote using Anthem. I'm a heavy prototype user. In some cases I retrieve elements using css selectors. Sometimes a part of the selector includes the wrapper 'div'. Changing it into a 'span' would break code, maybe not only in my applications. Maybe I'm being to selfish here :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-12-09 19:38 Message: Logged In: YES user_id=1245761 Originator: NO Great tip! I suppose this applies to all of the Anthem controls that wrap the native control inside of a <div>. Since the type of element that is used does not matter to Anthem, perhaps we should always use an inline control when the native control is not visible (i.e. use <span></span> when Visible=false, and <div></div> otherwise). Or we could assign a class to the wrapper element such as <div class="anthem"> wrapped HTML </div> <div class="anthem hidden"></div> Then you could modify your stylesheet to do anything you want with Anthem controls. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-12-09 18:23 Message: Logged In: NO Correction. Code should be: else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Gavin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-26 01:37:42
|
Feature Requests item #1880127, was opened at 2008-01-26 01:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782467&aid=1880127&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: dynodave (omnisoftware) Assigned to: Nobody/Anonymous (nobody) Summary: Remove excessive HTML Initial Comment: To aid debugging and compact generated html, remove unuseable/excessive code. <td><a onclick="javascript:Anthem_FireCallBackEvent(this,event,'_ctl0:CPH1:GV1','Edit$0',false,'','','',true,null,null,null,true,true);return false;" href="javascript:__doPostBack('_ctl0$CPH1$GV1','Edit$0')" style="color:#333333;">Edit</a></td><td>17</td> 1. Events where Anthem_FireCallBackEvent is generated should also remove original doPostBack. Example: Creating an editable Anthem grid generates the appropriate onclick events for each editable column. That's great! So now "doPostBack" hrefs are no longer valid because onclick does the work and always returns false. With large grids, they become excessive in the html and make it more difficult to read during debugging. 2. Instead of appending ;return false; why not have the called function return false. Example: onclick="return Anthem_FireCallBackEvent(this,event,'_ctl0:CPH1:GV1','Edit$0',false,'','','',true,null,null,null,true,true);" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782467&aid=1880127&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-25 09:06:35
|
Bugs item #1872498, was opened at 2008-01-16 03:16 Message generated for change (Settings changed) made by afm_44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Rejected Priority: 5 Private: No Submitted By: Wayne Hartman (chabilha) >Assigned to: Andy Miller (afm_44) Summary: LinkButtons Duplicate Data On a Page Initial Comment: This is very odd bug, but one I discovered. Code will appear at the bottom. I have been trying to duplicate my own paging for a repeater (I hate having everything locked inside tables with the other auto-paging controls) have created a series of LinkButtons as my pagers. What I do is create a PagedDataSource for the actual data and then another for the page indices and display values. The code then appropriately displays the correct number of pages above my code. However, whenever I click any callback or posting capable control, it duplicates the row of link buttons I have created below it. I can change pages and the bottom row does not get updated, but the top one does. So I have a top row that pages correctly and a bottom row that does not. Just to be clear, that bottom row should not even be there. I have also attempted to try using this with POAC (plain old asp controls--sorry I couldn't resist) and the problem is not reproduced. I really wanted to do this using AJAX so that my pages weren't posting back. :( I have attached the source to this bug report. I apologize if the code is a little crazy. This was a prototype to doing some nice custom paging. ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-16 22:52 Message: Logged In: YES user_id=1245761 Originator: NO Your assumption is correct for the standard Repeater. It's my favorite feature of that control. However, Anthem wraps every control in a <div> or <span> (depending on whether the underlying control is typically a block element or not). The Anthem wrapper element is used to update the content after a callback. The javascript kind of looks like this: document.getElementById(anthem_wrapper_id).innerHTML = updated_HTML; ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-16 22:39 Message: Logged In: NO Very nice. I didn't think to check the markup. I always thought that the Repeater returned literal content, not enclosing it in a <div>, but that did the trick. I also, per your suggestion changed the anthem tags to asp tags inside the repeater after I saw that moving the markup to the Header and Footer tags worked. Thanks! ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-16 15:12 Message: Logged In: YES user_id=1245761 Originator: NO One thing I notice is that you have embedded the Anthem Repeater inside of HTML as a table. The resulting HTML probably looks like this: <table> <tr> <div> <td> </div> </tr> </table> Which is not valid HTML. I suspect your browser is confused by the <div> stuck in between the <tr> and the <td>. Try putting the <table><tr> in the Repeater <HeaderTemplate> and close the table in the Repeater <FooterTemplate>. The next thing I notice is that you are embedding Anthem controls (LinkButton, Label) inside of the Anthem Repeater. As far as I can tell that is unnecessary and probably inefficient (each LinkButton and Label is updated twice: once by the Repeater and once by the itself). The Anthem Repeater implements Anthem.IContainerControl which means it will "anthemize" any base controls it finds inside. Try changing the control inside the Repeater to <asp:LinkButton> and <asp:Label>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-17 16:25:41
|
Patches item #1847594, was opened at 2007-12-09 19:47 Message generated for change (Comment added) made by psiegers You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for IE6 and hidden panels Initial Comment: I had trouble with IE6 (and below) applying line-height to an anthem:Panel with Visible="false". Anthem renders this for a hidden panel: <div id="controlId"></div> http://lists.evolt.org/archive/Week-of-Mon-20070416/189398.html suggests that the following stops the problem: <div id="controlId"><!-- --></div> To implement, add the following at line 52 of Panel.cs: else { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Cheers, Gavin. ---------------------------------------------------------------------- >Comment By: Pieter Siegers (psiegers) Date: 2008-01-17 10:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi Gavin, did you test this code only in IE6 or also in other browsers? PD: I'm talking about the following code (added to Panel.cs starting from line 52): else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } ---------------------------------------------------------------------- Comment By: Pieter Siegers (psiegers) Date: 2007-12-31 11:25 Message: Logged In: YES user_id=1067768 Originator: NO Hi all, I agree with Manu, and think that adding a css class id is a good idea. ---------------------------------------------------------------------- Comment By: TweeZz (tweezz) Date: 2007-12-10 01:13 Message: Logged In: YES user_id=1472130 Originator: NO Hi Andy, I think the second solution you suggested is somehow 'safer'. At least for the applications I wrote using Anthem. I'm a heavy prototype user. In some cases I retrieve elements using css selectors. Sometimes a part of the selector includes the wrapper 'div'. Changing it into a 'span' would break code, maybe not only in my applications. Maybe I'm being to selfish here :) ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2007-12-09 21:38 Message: Logged In: YES user_id=1245761 Originator: NO Great tip! I suppose this applies to all of the Anthem controls that wrap the native control inside of a <div>. Since the type of element that is used does not matter to Anthem, perhaps we should always use an inline control when the native control is not visible (i.e. use <span></span> when Visible=false, and <div></div> otherwise). Or we could assign a class to the wrapper element such as <div class="anthem"> wrapped HTML </div> <div class="anthem hidden"></div> Then you could modify your stylesheet to do anything you want with Anthem controls. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-12-09 20:23 Message: Logged In: NO Correction. Code should be: else if (!Manager.IsCallBack) { // This is so that IE6 doesn't apply line height to an empty div writer.Write("<!-- -->"); } Gavin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782466&aid=1847594&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-16 22:52:47
|
Bugs item #1872498, was opened at 2008-01-16 03:16 Message generated for change (Comment added) made by afm_44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Wayne Hartman (chabilha) Assigned to: Nobody/Anonymous (nobody) Summary: LinkButtons Duplicate Data On a Page Initial Comment: This is very odd bug, but one I discovered. Code will appear at the bottom. I have been trying to duplicate my own paging for a repeater (I hate having everything locked inside tables with the other auto-paging controls) have created a series of LinkButtons as my pagers. What I do is create a PagedDataSource for the actual data and then another for the page indices and display values. The code then appropriately displays the correct number of pages above my code. However, whenever I click any callback or posting capable control, it duplicates the row of link buttons I have created below it. I can change pages and the bottom row does not get updated, but the top one does. So I have a top row that pages correctly and a bottom row that does not. Just to be clear, that bottom row should not even be there. I have also attempted to try using this with POAC (plain old asp controls--sorry I couldn't resist) and the problem is not reproduced. I really wanted to do this using AJAX so that my pages weren't posting back. :( I have attached the source to this bug report. I apologize if the code is a little crazy. This was a prototype to doing some nice custom paging. ---------------------------------------------------------------------- >Comment By: Andy Miller (afm_44) Date: 2008-01-16 22:52 Message: Logged In: YES user_id=1245761 Originator: NO Your assumption is correct for the standard Repeater. It's my favorite feature of that control. However, Anthem wraps every control in a <div> or <span> (depending on whether the underlying control is typically a block element or not). The Anthem wrapper element is used to update the content after a callback. The javascript kind of looks like this: document.getElementById(anthem_wrapper_id).innerHTML = updated_HTML; ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-16 22:39 Message: Logged In: NO Very nice. I didn't think to check the markup. I always thought that the Repeater returned literal content, not enclosing it in a <div>, but that did the trick. I also, per your suggestion changed the anthem tags to asp tags inside the repeater after I saw that moving the markup to the Header and Footer tags worked. Thanks! ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-16 15:12 Message: Logged In: YES user_id=1245761 Originator: NO One thing I notice is that you have embedded the Anthem Repeater inside of HTML as a table. The resulting HTML probably looks like this: <table> <tr> <div> <td> </div> </tr> </table> Which is not valid HTML. I suspect your browser is confused by the <div> stuck in between the <tr> and the <td>. Try putting the <table><tr> in the Repeater <HeaderTemplate> and close the table in the Repeater <FooterTemplate>. The next thing I notice is that you are embedding Anthem controls (LinkButton, Label) inside of the Anthem Repeater. As far as I can tell that is unnecessary and probably inefficient (each LinkButton and Label is updated twice: once by the Repeater and once by the itself). The Anthem Repeater implements Anthem.IContainerControl which means it will "anthemize" any base controls it finds inside. Try changing the control inside the Repeater to <asp:LinkButton> and <asp:Label>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 |
From: SourceForge.net <no...@so...> - 2008-01-16 22:38:59
|
Bugs item #1872498, was opened at 2008-01-15 19:16 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Wayne Hartman (chabilha) Assigned to: Nobody/Anonymous (nobody) Summary: LinkButtons Duplicate Data On a Page Initial Comment: This is very odd bug, but one I discovered. Code will appear at the bottom. I have been trying to duplicate my own paging for a repeater (I hate having everything locked inside tables with the other auto-paging controls) have created a series of LinkButtons as my pagers. What I do is create a PagedDataSource for the actual data and then another for the page indices and display values. The code then appropriately displays the correct number of pages above my code. However, whenever I click any callback or posting capable control, it duplicates the row of link buttons I have created below it. I can change pages and the bottom row does not get updated, but the top one does. So I have a top row that pages correctly and a bottom row that does not. Just to be clear, that bottom row should not even be there. I have also attempted to try using this with POAC (plain old asp controls--sorry I couldn't resist) and the problem is not reproduced. I really wanted to do this using AJAX so that my pages weren't posting back. :( I have attached the source to this bug report. I apologize if the code is a little crazy. This was a prototype to doing some nice custom paging. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-16 14:39 Message: Logged In: NO Very nice. I didn't think to check the markup. I always thought that the Repeater returned literal content, not enclosing it in a <div>, but that did the trick. I also, per your suggestion changed the anthem tags to asp tags inside the repeater after I saw that moving the markup to the Header and Footer tags worked. Thanks! ---------------------------------------------------------------------- Comment By: Andy Miller (afm_44) Date: 2008-01-16 07:12 Message: Logged In: YES user_id=1245761 Originator: NO One thing I notice is that you have embedded the Anthem Repeater inside of HTML as a table. The resulting HTML probably looks like this: <table> <tr> <div> <td> </div> </tr> </table> Which is not valid HTML. I suspect your browser is confused by the <div> stuck in between the <tr> and the <td>. Try putting the <table><tr> in the Repeater <HeaderTemplate> and close the table in the Repeater <FooterTemplate>. The next thing I notice is that you are embedding Anthem controls (LinkButton, Label) inside of the Anthem Repeater. As far as I can tell that is unnecessary and probably inefficient (each LinkButton and Label is updated twice: once by the Repeater and once by the itself). The Anthem Repeater implements Anthem.IContainerControl which means it will "anthemize" any base controls it finds inside. Try changing the control inside the Repeater to <asp:LinkButton> and <asp:Label>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=782464&aid=1872498&group_id=151897 |