[Proto-Scripty] Re: Ajax.Updater request in IE changes header attribute Accept

2009-09-22 Thread david

Hi John,
it sound like a modified option in IE or register ?
but you'll have more chance on a microsoft support forum.

--
david

On 18 sep, 21:55, John Shen jshen2...@gmail.com wrote:
 I struggling with this one for more than a day now.  Need help!

 I am working on a rails project, in which I submit the following in a
 form using onsubmit trigger:

 new Ajax.Updater('xxx', 'the_url_path', {asynchronous:true,
 evalScripts:true, parameters:Form.serialize(document.the_form)});
 return false;

 It works perfectly in Firefox, Safari, Opera and Chrome, failed on IE
 (versions 6, 7, and 8). After some investigation, I found that for
 some reason, the ajax request is sent to server and IE somehow changed
 accept attribute in the header accepting everything (including word
 file, images, excel files etc) but javascript.  When the response
 comes back with content type of text/javascript, IE refuses to run
 because it is not expecting any scripts.  It pops up a file download
 window and a security warning window say it does not recognize the
 content of the file.

 Anybody had this problem before?  your help is much appreciated!

 John
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype  script.aculo.us group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to 
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~--~~~~--~~--~--~---



[Proto-Scripty] Re: Events not working as expected in opera, ie or any other browser except firefox

2009-09-22 Thread Juan Diego

Ok so i find out the source of the problem, not a solution yet, but i
know what is the problem.  The flash module in my joomla page has this
mootools.js library that for some reasons in IE8 conflicts or creates
that problem, i am going to try some work around.

Juan Diego

On Sep 21, 7:04 am, T.J. Crowder t...@crowdersoftware.com wrote:
 Hi Juan,

 I've only skimmed this, so apologies if this comment is completely off-
 base, but you mentioned tables in there somewhere although I don't see
 any tables in the HTML snippets.  Do all of your tables have the
 appropriate TBODY elements in them?  I can see that being a difference
 between browsers, particularly depending on what your DOCTYPE is.
 It's a surprisingly well-kept secret that TR cannot appear directly
 within TABLE, you must have a TBODY (or THEAD or TFOOT) in between:

     table
       tr
         tdThis/td
       /tr
       tr
         tdis/td
       /tr
       tr
         tdWRONG/td
       /tr
     /table

     table
       tbody
         tr
           tdThis/td
         /tr
         tr
           tdis/td
         /tr
         tr
           tdright/td
         /tr
       /tbody
     /table

 Firefox will silently insert one for you; I don't know what IE's
 behavior is (whether it inserts one or just doesn't worry about it).

 Again, apologies if this is completely off-base.

 Oh, and separately:  If you find yourself writing:

     someElement.up().up()

 you can use

     someElement.up(1)

 ...instead. (Yes, really 1, not 2 -- up() equals up(0), so up().up()
 equals up(1). *Terrible* API choice, but there we are.  Details in the
 old API docs[1].)

 [1]http://prototypejs.org/api/element/up

 Good luck,
 --
 T.J. Crowder
 tj / crowder software / comwww.crowdersoftware.com

 On Sep 21, 11:08 am, Juan Diego juandieg...@gmail.com wrote:

  Damn IE. Ok thanks.  I am going to take away elements from the page
  where is the conflict.  Thanks for your time.

  Juan Diego

  On Sep 21, 4:49 am, Kevin Porter k...@9ballpool.co.uk wrote:

   Sorry, I didn't try your page, I was just using the test page I built to
   test your code.

   You're right, IE8 gives an error on your page.

   It's complaining about this line:

   var e2 = element.up().up().up().next();

   You'll just have to debug - please find out exaclty what you get for
   element.up(), element.up().up() etc. At some point
   it's behaviour is differing from Firefox - when you find out what that
   is we'll try and figure why the behaviour is different.

   One thing I would suggest trying (from previous IE LI difficulties) is
   to remove all whitespace from the UL/LI markup. However, the docs for
   next() and up() say that whitespace nodes are totally ignored by these
   functions, so that may not be the problem but it's probably worth a
   minute to try.

   Alternatively, you could try using a css rule in up()
   (http://www.prototypejs.org/api/element/up) , eg:

   var e2 = element.up('div.lista_izq').next();

   Let me know how you get on. If those alternative suggestions don't work,
   we really need you to debug to find out at exactly which point the IE8
   behaviour is differing from that of normal browsers.

   regards,

   - Kev

   Juan Diego wrote:
It is still not working. I am going to try in another machine.  I get
this error because the browser is in spanish.  El objeto no acepta
esta propiedad o metodo. Which means the object does not accept this
property or method in the lines 15 and 28.

On Sep 21, 4:23 am, Kevin Porter k...@9ballpool.co.uk wrote:

It works for me in IE8!

Kill IE8, re-open it and try again.

If it still doesn't work, what error are you getting?

regards,

- Kev

Juan Diego wrote:

I cleaned up a little my code it still doesnt work in IE8

this is the code
function reemplazarX(){
   var element = this;
   //var e2 =element.getOffsetParent();
   var e2 =element.up().up().up().next();
   //alert(e2);
   e2.setStyle({
           backgroundColor: '#020506',
           opacity: 1.0,
           borderLeft:'1px #FFF solid'
   });
   e2.innerHTML= element.next().innerHTML;

}
function borrar(){
   var element = this;
   //var e2 =element.getOffsetParent();
   var e2 =element.up().up().up().next();
   e2.innerHTML= ;
   e2.setStyle({
           backgroundColor: '#000',
           opacity: 0.0
   });
}

On Sep 21, 3:59 am, Juan Diego juandieg...@gmail.com wrote:

I dont want the LI elements.  Here is how it is setup,

div class=lista_izq
ul
    lidiv class=texttext1/div
          div class=hidden_texthidden1/div
    /li
   lidiv class=texttext2/div
          div class=hidden_texthidden2/div
    /li
/ul
/div
div class=lista_dernbsp/div
I want display my message in lista_der.  So that is why i use all
those up(), i guess I can use 4 up and one next.

On Sep 21,