Re: [web2py] Re: Problems with forms and firefox

[Bruno Rocha]

It happens even if I remove the ckeditor widget.

and happens also on the edit article form.

Denes found the problem but I cant understand why the problem is only with
firefox.

http://zerp.ly/rochacbruno
Em 28/11/2011 13:02, "DenesL"  escreveu:

> Seems to be a problem with the encoding/decoding of multi-part form
> data.
> The POST source shows:
>
> Content-Type: multipart/form-data;
> boundary=---265001916915724
> Content-Length: 464
> -265001916915724
> Content-Disposition: form-data; name="comment_text"
>   test by Denes using Firefox 8.0.1 on Win XP
> -265001916915724
> Content-Disposition: form-data; name="_formkey"
> 51d0905f-1ba0-4f3d-96c2-5dc38178dd36
> -265001916915724
> Content-Disposition: form-data; name="_formname"
> article_comments/create
> -265001916915724--
>
> but Firebug only lists two parts:
>
> Parts multipart/form-data
>
> _formkey51d0905f-1ba0-4f3d-96c2-5dc38178dd36
> _formname   article_comments/create
>

Re: [web2py] Re: Problems with forms and firefox

[Bruno Rocha]

I am trying to think it is a problem with web2py session vars in
current.session.

Re: [web2py] Re: Problems with forms and firefox

[Bruno Rocha]

I am sure it is not ckeditor because I tested without it.

may be it is a problem in current or in custom_importer.

note that my form is built in a module.

I will try to build the form in controller for test.

thanks again.

http://zerp.ly/rochacbruno
Em 29/11/2011 12:02, "DenesL"  escreveu:

>
> Note that in my previous test the P tags were not encoded:
>
> Content-Disposition: form-data; name="comment_text"
>   test by Denes using Firefox 8.0.1 on Win XP
>
> If you type for example:
> TEST
>
> the comment will be encoded as:
>  TEST
>
> Again note that the P tags are not encoded.
>
> If no Content-Transfer-Encoding is specified in a Multipart Media Type
> then the content is assumed to be in US-ASCII as described in RFC2045
> and RFC822, but in there the greater-than ">" and less-than "<"
> characters are special and "must be in quoted-string, to use within a
> word".
>
> So I believe the encoding is being messed up, finding where is yet
> another problem.
>
> Denes.
>
>

Re: [web2py] Re: Problems with forms and firefox

[Bruno Rocha]

I found that the problem is somewhere in the new welcome layout. some lib
there is changing the form encoding.

If I try with .load

http://labs.blouweb.com/movuca/article/show.load/2/vegetarian-cheese

The comments works ok with any browser.

Now I have to find what lib or html tag is doing that,

Re: [web2py] Re: Problems with forms and firefox

[Bruno Rocha]

Finally the problem is solved, and it has not to be with web2py.

I am using jqm (Jquery Modal Plugin)

The sample code has

  
  {{=T("Close")}}
  
  
  

where the src attr for img is filled dynamically by the plugin modal.
Firefox was raising validation error because of that.

I used the w3c validator to solve this problem!

Thank you all

Re: [web2py] Re: Problems with forms and firefox

[Bruno Rocha]

This was the issue:

http://www.nczonline.net/blog/2009/11/30/empty-image-src-can-destroy-your-site/

and

http://www.nczonline.net/blog/2010/03/16/empty-string-urls-in-html-a-followup/