I have run into an issue and was wondering if anyone could help. I am doing an ajax call , returning html and updating an Element. The html is basic "Test <hr /> Test". But for some reason IE7 comes up with an unknown runtime exception. It will render it correctly if i have "Test <br /> test". Has anyone had this problem? I have even taken out the Ajax call and just have a javascript function to call new Element.update() .. passing the id of the element and the text. Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
I have figured out my own problem after so many hours... ugh! But it seems to work if the element is type <div> but has issues if the type of element is a <p>. Hmm will still have to do some research. I might just be missing something. Thanks everyone ;) On May 21, 4:05 pm, Tomelo <tomeloalac...-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:> I have run into an issue and was wondering if anyone could help. I am > doing an ajax call , returning html and updating an Element. The html > is basic "Test <hr /> Test". But for some reason IE7 comes up with an > unknown runtime exception. It will render it correctly if i have "Test > <br /> test". Has anyone had this problem? I have even taken out the > Ajax call and just have a javascript function to call new > Element.update() .. passing the id of the element and the text. > > Thanks--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
IE has a lot of quirks when updating certain types of elements (like table bodies, select lists, and -- perhaps -- paragraphs). That''s why updating divs and spans are usually the way to go since IE seems to treat them similar to the way that other browsers handle updates. - Dash - Tomelo wrote:> I have figured out my own problem after so many hours... ugh! But it > seems to work if the element is type <div> but has issues if the type > of element is a <p>. Hmm will still have to do some research. I might > just be missing something. Thanks everyone ;) > > On May 21, 4:05 pm, Tomelo <tomeloalac...-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote: > >> I have run into an issue and was wondering if anyone could help. I am >> doing an ajax call , returning html and updating an Element. The html >> is basic "Test <hr /> Test". But for some reason IE7 comes up with an >> unknown runtime exception. It will render it correctly if i have "Test >> <br /> test". Has anyone had this problem? I have even taken out the >> Ajax call and just have a javascript function to call new >> Element.update() .. passing the id of the element and the text. >> >> Thanks >> > > > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---